[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: gnus-carpal-mode and mouse-autoselect-window
From: |
Klaus Zeitler |
Subject: |
Re: gnus-carpal-mode and mouse-autoselect-window |
Date: |
Wed, 30 Mar 2005 13:01:23 +0200 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (usg-unix-v) |
>>>>> "Reiner" == Reiner Steib <address@hidden> writes:
Reiner>
Reiner> Or did you mean to add (goto-char (point-min)) _after_ the `if'
Reiner> clause?
>>
>> I've added it right at the end of the save-excursion, i.e. the function
>> ends like this:
>> --- snip ---
>> (set-window-point (get-buffer-window (current-buffer))
>> (point-min)))
>> (goto-char (point-min))
>> ))))
>> --- snip ---
Reiner>
Reiner> Thus it is only done if the `set-window-point' statement is also
Reiner> executed. I would guess that the `set-window-point' statement
Reiner> should already do this, but maybe I'm missing something.
I finally found some time to debug this and would like to clarify one thing
before I set this problem aside.
It seems to me as if set-window-point and goto-char don't do the same thing.
set-window-point basically executes the following statements:
--- snip ---
if (w == XWINDOW (selected_window)
&& XBUFFER (w->buffer) == current_buffer)
Fgoto_char (pos);
else
set_marker_restricted (w->pointm, pos, w->buffer);
--- snip ---
when called from gnus-carpal-setup-buffer, XWINDOW(selected_window) is true,
but (XBUFFER (w->buffer) == current_buffer) is false. Thus
set_marker_restricted is called and not goto_char.
It's not clear to me what the function set_marker_restricted does and if
that does what is expected to be done when called in gnus-carpal-setup-buffer.
Klaus
--
------------------------------------------
| Klaus Zeitler Lucent Technologies |
| Email: address@hidden |
------------------------------------------
---
For perfect happiness, remember two things:
(1) Be content with what you've got.
(2) Be sure you've got plenty.