unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org, sdl.web@gmail.com,
	storm@cua.dk
Subject: Re: gnus makes emacs lose response
Date: Sat, 23 Sep 2006 11:02:46 -0400	[thread overview]
Message-ID: <jwvr6y2pqyy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <E1GQyHY-0005Pv-Vr@fencepost.gnu.org> (Richard Stallman's message of "Fri\, 22 Sep 2006 23\:34\:24 -0400")

>     Oh I see, it's because I haven't updated the code in response to the
>     following change:

>     2004-08-19  Kim F. Storm  <storm@cua.dk>

> 	    * process.c (wait_reading_process_input): Clean up.
> 	    Add wait_for_cell, wait_proc, and just_wait_proc args
> 	    to avoid overloading `read_kbd' and `do_display' args.
> 	    Change read_kbd arg to int.  All callers changed.

>     So I should probably check wait_proc instead.

> Would you please make whatever change is needed?

We're talking about a local change which I have no intention to install in
Emacs-CVS, or at least not for Emacs-22.  Although maybe it could be
added but controlled by a compilation flag such as ENABLE_CHECKING
or DEBUG.


        Stefan

  reply	other threads:[~2006-09-23 15:02 UTC|newest]

Thread overview: 58+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-09 22:33 gnus makes emacs lose response Kim F. Storm
2006-09-10  4:10 ` Stefan Monnier
2006-09-16 20:22   ` Chong Yidong
2006-09-18 14:40   ` Chong Yidong
2006-09-18 14:53     ` Chong Yidong
2006-09-19 10:45       ` Stefan Monnier
2006-09-19 15:02         ` Chong Yidong
2006-09-22 19:12           ` Stefan Monnier
2006-09-23 18:01             ` Richard Stallman
2006-09-23  3:34         ` Richard Stallman
2006-09-23 15:02           ` Stefan Monnier [this message]
2006-09-18 14:55     ` Stefan Monnier
  -- strict thread matches above, loose matches on Subject: below --
2006-09-23 18:18 Chong Yidong
2006-09-23 23:42 ` Luc Teirlinck
2006-09-26 17:26 ` Leo
2006-09-26 18:08   ` Chong Yidong
2006-09-26 19:20     ` Leo
2006-09-04  8:41 Kim F. Storm
2006-09-05 21:18 ` Chong Yidong
2006-09-05 21:21   ` Stefan Monnier
2006-09-07 20:43     ` Chong Yidong
2006-09-08 11:56       ` Richard Stallman
2006-09-06 19:06   ` Richard Stallman
2006-09-07 14:37 ` Chong Yidong
2006-09-22 20:04 ` Chong Yidong
2006-09-25  0:39   ` Stefan Monnier
2006-09-25 15:22     ` Chong Yidong
     [not found] <m2lkuuynpf.fsf@sl392.st-edmunds.cam.ac.uk>
     [not found] ` <m24q18rize.fsf@sl392.st-edmunds.cam.ac.uk>
2006-04-05  8:47   ` Kim F. Storm
2006-04-05 17:55     ` Leon
2006-04-06  9:08       ` Kim F. Storm
2006-04-06 21:15         ` Leon
2006-04-07  8:13           ` Kim F. Storm
2006-04-07 13:25             ` Leon
2006-04-07 20:58         ` Ralf Angeli
2006-04-09  1:17           ` Leon
2006-04-17 20:35           ` Ralf Angeli
2006-04-18  1:46             ` Leon
2006-04-19 20:18               ` Ralf Angeli
2006-04-20  1:19                 ` Leon
2006-04-19 20:18             ` Ralf Angeli
2006-04-19 20:51               ` Stefan Monnier
2006-04-19 21:13                 ` Ralf Angeli
2006-04-20 18:05               ` Gregory Novak
2006-04-24  0:41                 ` Kim F. Storm
2006-08-22 11:44               ` Kim F. Storm
2006-08-23 14:45                 ` Richard Stallman
2006-08-23 15:00                   ` Kim F. Storm
2006-08-25  7:43                     ` Richard Stallman
2006-08-25  8:15                       ` Kim F. Storm
2006-08-26 10:08                         ` Richard Stallman
2006-08-26 21:32                           ` Kim F. Storm
2006-08-25  8:56                       ` Jason Rumney
2006-08-23 20:51                   ` Stefan Monnier
2006-08-24  3:17                   ` Bob Rogers
2006-08-24  7:51                     ` Kim F. Storm
2006-08-25  1:01                       ` Bob Rogers
2006-08-25 20:23                       ` Richard Stallman
2006-08-25  7:44                     ` Richard Stallman

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=jwvr6y2pqyy.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    --cc=sdl.web@gmail.com \
    --cc=storm@cua.dk \
    /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).