unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Seltenreich <seltenreich@gmx.de>
Cc: emacs-devel@gnu.org
Subject: Re: Did something change with respect to Emacs idle loop:
Date: Tue, 26 Sep 2006 19:49:35 +0200	[thread overview]
Message-ID: <87venafrgw.fsf@gate450.dyndns.org> (raw)
In-Reply-To: <17682.1266.569204.546622@gargle.gargle.HOWL> (T. V. Raman's message of "Wed\, 20 Sep 2006 20\:20\:18 -0700")

"T. V. Raman" <raman@users.sf.net> writes:

> Another situation where I've noticed changed behavior is with
> emms (2.1) --- if you launch a playlist  then playback stops
> after each track, and you again need to touch the keyboard  for
> it to move to the next track.

Could this be related to the recently-fixed fontification loop
problem?  When investigating with gdb, I noticed that Emacs didn't
leave the following loop in wait_reading_process_output() since
timers_run was repeatedly increased during redisplay, and execution
didn't ever reach the select().

--8<---------------cut here---------------start------------->8---
	  do
	    {
	      int old_timers_run = timers_run;
	      struct buffer *old_buffer = current_buffer;

	      timer_delay = timer_check (1);

	      /* 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 ();

	      if (timers_run != old_timers_run && do_display)
		/* We must retry, since a timer may have requeued itself
		   and that could alter the time_delay.  */
		redisplay_preserve_echo_area (9);
	      else
		break;
	    }
--8<---------------cut here---------------end--------------->8---

HTH
Andreas

  parent reply	other threads:[~2006-09-26 17:49 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-21  3:20 Did something change with respect to Emacs idle loop: T. V. Raman
2006-09-21  3:47 ` T. V. Raman
2006-09-21 13:58   ` Romain Francoise
2006-09-22  1:11     ` T. V. Raman
2006-09-22 18:08       ` Romain Francoise
2006-09-22  4:11 ` Richard Stallman
2006-09-22 19:21   ` Chong Yidong
2006-09-23 17:55     ` T. V. Raman
2006-09-24  2:10       ` Richard Stallman
2006-09-24 15:49         ` joakim
2006-09-24 18:00           ` T. V. Raman
2006-09-25  3:17           ` Richard Stallman
2006-09-24 17:58         ` T. V. Raman
2006-09-25 20:48           ` Richard Stallman
2006-09-27 13:08             ` T. V. Raman
2006-09-28  2:14               ` Richard Stallman
2006-09-23 18:01     ` Richard Stallman
2006-09-26 17:49 ` Andreas Seltenreich [this message]
2006-09-27 13:09   ` T. V. Raman
2006-09-27 17:53     ` Andreas Seltenreich
2006-09-28  3:46       ` T. V. Raman

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87venafrgw.fsf@gate450.dyndns.org \
    --to=seltenreich@gmx.de \
    --cc=emacs-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).