From: Chong Yidong <cyd@stupidchicken.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 1458@emacsbugs.donarmstrong.com
Subject: bug#1458: 23.0.60; mouse-posn-property: Args out of range
Date: Tue, 02 Dec 2008 11:39:11 -0500 [thread overview]
Message-ID: <87skp6jzv4.fsf@cyd.mit.edu> (raw)
In-Reply-To: <jwvd4gazkdy.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Tue, 02 Dec 2008 10:11:39 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> You patch to timer_check doesn't seem right: it may cause the
> current-buffer to be changed even if the timer doesn't do anything, just
> because the current-buffer before running the timer wasn't the
> selected-window's buffer. It causes no end of trouble in Gnus
> (e.g. when connecting to an IMAP server, it calls read-passwd during
> which calls to read-event can run timers, so we start read-passwd in
> the IMAP process's buffer and we finish it in the *Group* buffer or
> which ever buffer is currently displayed, after which
> send-process-string fails because it can't find the process).
I see. The change is reverted.
Now I'm not certain how to deal with the problem described in bug#1458.
Perhaps we should make the selected window's buffer current only if the
selected window's buffer was current before running the timer. WDYT?
next prev parent reply other threads:[~2008-12-02 16:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87k5alru8r.fsf@cyd.mit.edu>
2008-11-29 20:31 ` bug#1458: 23.0.60; mouse-posn-property: Args out of range Stephen Berman
2008-11-30 17:45 ` bug#1458: marked as done (23.0.60; mouse-posn-property: Args out of range) Emacs bug Tracking System
2008-12-02 15:11 ` bug#1458: 23.0.60; mouse-posn-property: Args out of range Stefan Monnier
2008-12-02 16:39 ` Chong Yidong [this message]
2008-12-02 22:49 ` Stefan Monnier
2008-12-02 23:20 ` bug#1458: marked as done (23.0.60; mouse-posn-property: Args out of range) Emacs bug Tracking System
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skp6jzv4.fsf@cyd.mit.edu \
--to=cyd@stupidchicken.com \
--cc=1458@emacsbugs.donarmstrong.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.