[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: appointment display during isearch replaces buffer contents with his
From: |
Johan Bockgård |
Subject: |
Re: appointment display during isearch replaces buffer contents with history-element |
Date: |
Tue, 26 Feb 2008 12:53:02 +0100 |
User-agent: |
Gnus/5.110007 (No Gnus v0.7) Emacs/23.0.60 (gnu/linux) |
bojohan+news@dd.chalmers.se (Johan Bockgård) writes:
> Chong Yidong <cyd@stupidchicken.com> writes:
>
>> an alike. Make read_key_sequence aware of that. */
>> if (timers_run != old_timers_run
> [...]
>
> There are two occurrences of this in wait_reading_process_output. Should
> the other be changed too?
Anyone? I'm talking about this change:
2008-01-10 Chong Yidong <cyd@stupidchicken.com>
* process.c (wait_reading_process_output): Check for window
changes caused by timers.
wait_reading_process_output contains two conditionals that may run
record_asynch_buffer_change. The check for window changes was only
added to the latter one:
process.c:4368
/* If a timer has run, this might have changed buffers
an alike. Make read_key_sequence aware of that. */
if (timers_run != old_timers_run
&& old_buffer != current_buffer
&& waiting_for_user_input_p == -1)
record_asynch_buffer_change ();
process.c:4692
/* If a timer has run, this might have changed buffers
an alike. Make read_key_sequence aware of that. */
if (timers_run != old_timers_run
&& waiting_for_user_input_p == -1
&& (old_buffer != current_buffer
|| !EQ (old_window, selected_window)))
record_asynch_buffer_change ();
Is this intentional?
--
Johan Bockgård
- Re: appointment display during isearch replaces buffer contents with history-element,
Johan Bockgård <=