GNU bug report logs -
#1458
23.0.60; mouse-posn-property: Args out of range
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 1458 in the body.
You can then email your comments to 1458 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1458
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Stephen Berman <stephen.berman <at> gmx.net>
:
New bug report received and forwarded. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #5 received at submit <at> emacsbugs.donarmstrong.com (full text, mbox):
1. emacs -Q
2. Eval this:
(defun testme ()
(save-selected-window
(switch-to-buffer "testme")))
If `testme' is not a fresh buffer, see observation (a) below.
3. Eval (run-at-time 3 nil 'testme) and wait 3 seconds.
4. When the `testme' buffer appears, move the mouse cursor over the mode line;
as soon as it hits a position that has a help-echo property containing the
string "mouse-2", the following error is raised:
mouse-posn-property: Args out of range: 719
The out of range number is (point) in step 3.
Backtrace:
Debugger entered--Lisp error: (args-out-of-range 719)
get-char-property(719 follow-link #<window 220 on testme>)
mouse-posn-property((#<window 220 on testme> mode-line (467 . 644) 0 (#("-%-" 0 3 ...) . 2) 719 (58 . 46) nil (2 . 4) (8 . 16)) follow-link)
(or (mouse-posn-property pos (quote follow-link)) (key-binding [follow-link] nil t pos))
(and (or (not ...) mouse-1-click-in-non-selected-windows (eq ... ...)) (or (mouse-posn-property pos ...) (key-binding [follow-link] nil t pos)))
(let ((action ...)) (cond (... ...) (... ...) (t action)))
mouse-on-link-p((#<window 220 on testme> mode-line (467 . 644) 0 (#("-%-" 0 3 ...) . 2) 719 (58 . 46) nil (2 . 4) (8 . 16)))
mouse-fixup-help-message("mouse-1: Select (drag to resize)\nmouse-2: Make current window occupy the whole frame\nmouse-3: Remove current window from display")
Observations:
a. The error only occurs when (point) of the the buffer that is current when
step 3 is carried out, is greater than (point-max) of the buffer `testme'.
b. The error only occurs when testme is called from a timer.
c. The error only occurs when the function called from the timer
contains a call to save-selected-window.
d. The error only occurs with propertized text satisfying mouse-on-link-p in
either the mode line or the header line, i.e., suitably propertized
text inserted into the editing area of the buffer does not induce the
error.
In GNU Emacs 23.0.60.17 (i686-pc-linux-gnu, GTK+ Version 2.12.9)
of 2008-11-29 on escher
Windowing system distributor `The X.Org Foundation', version 11.0.10400090
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: en_US.UTF-8
value of $XMODIFIERS: @im=local
locale-coding-system: utf-8-unix
default-enable-multibyte-characters: t
Reply sent to
Chong Yidong <cyd <at> stupidchicken.com>
:
You have taken responsibility.
Full text and
rfc822 format available.
Notification sent to
Stephen Berman <stephen.berman <at> gmx.net>
:
bug acknowledged by developer.
Full text and
rfc822 format available.
Message #10 received at 1458-done <at> emacsbugs.donarmstrong.com (full text, mbox):
> 1. emacs -Q
>
> 2. Eval this:
>
> (defun testme ()
> (save-selected-window
> (switch-to-buffer "testme")))
>
> 3. Eval (run-at-time 3 nil 'testme) and wait 3 seconds.
>
> 4. When the `testme' buffer appears, move the mouse cursor over the
> mode line; as soon as it hits a position that has a help-echo property
> containing the string "mouse-2", the following error is raised:
>
> mouse-posn-property: Args out of range: 719
I've checked in a fix. Thanks.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1458
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Stefan Monnier <monnier <at> iro.umontreal.ca>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #15 received at 1458 <at> emacsbugs.donarmstrong.com (full text, mbox):
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).
Stefan
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1458
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Chong Yidong <cyd <at> stupidchicken.com>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #20 received at 1458 <at> emacsbugs.donarmstrong.com (full text, mbox):
Stefan Monnier <monnier <at> 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?
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#1458
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
Stefan Monnier <monnier <at> IRO.UMontreal.CA>
:
Extra info received and forwarded to list. Copy sent to
Emacs Bugs <bug-gnu-emacs <at> gnu.org>
.
Full text and
rfc822 format available.
Message #25 received at 1458 <at> emacsbugs.donarmstrong.com (full text, mbox):
>> 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?
I don't think so. I think we need to track this bug further down.
Maybe the problem is that some code uses current_buffer (maybe to build
the mouse events?) rather than selected_window->buffer.
Stefan
bug reopened, originator not changed.
Request was from
Stefan Monnier <monnier <at> IRO.UMontreal.CA>
to
control <at> emacsbugs.donarmstrong.com
.
(Tue, 02 Dec 2008 22:55:05 GMT)
Full text and
rfc822 format available.
Reply sent to
Chong Yidong <cyd <at> stupidchicken.com>
:
You have taken responsibility.
Full text and
rfc822 format available.
Notification sent to
Stephen Berman <stephen.berman <at> gmx.net>
:
bug acknowledged by developer.
Full text and
rfc822 format available.
Message #32 received at 1458-done <at> emacsbugs.donarmstrong.com (full text, mbox):
Stefan Monnier <monnier <at> IRO.UMontreal.CA> writes:
> I think we need to track this bug further down. Maybe the problem is
> that some code uses current_buffer (maybe to build the mouse events?)
> rather than selected_window->buffer.
I've made a change to make_lispy_position that should solve this.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> emacsbugs.donarmstrong.com
.
(Wed, 31 Dec 2008 15:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 16 years and 169 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.