GNU bug report logs -
#102
keymap property ignored for mouse click on overlay
Previous Next
Reported by: "Drew Adams" <drew.adams <at> oracle.com>
Date: Sun, 30 Mar 2008 22:15:08 UTC
Severity: normal
Merged with 71
Done: Chong Yidong <cyd <at> stupidchicken.com>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 102 in the body.
You can then email your comments to 102 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#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.com>
:
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):
emacs -Q
(setq foo-map (make-sparse-keymap))
(define-key foo-map [mouse-2] 'bar)
(defun foo (beg end)
(interactive "r")
(let ((overlay (make-overlay beg end)))
(overlay-put
overlay 'display
(propertize "xxxxxxxxx" 'face 'font-lock-constant-face))
(overlay-put overlay 'keymap foo-map)))
(defun bar (event) (interactive "e") (message "BAR"))
Here's some text: aaaaaaaaaaaaaaaaaaaaaaa
Select one or more of the a's and do M-x foo, to apply the overlay to just
those a's.
Put point somewhere outside the displayed "xxxxxxxxx" overlay.
Click mouse-2 anywhere on the displayed "xxxxxxxxx". What happens, it seems,
is that, since point is not on the a's that have the overlay, keymap foo-map
doesn't apply. Clicking mouse-2 therefore just calls the default mouse-2
binding, e.g. mouse-yank-at-click. That sets point so that it is at the
beginning of the overlaid text, so that a second mouse-2 click on the
displayed "xxxxxxxxx" does call bar.
If that's what's happening, how can foo be defined so that a first click on
the displayed "xxxxxxxxx" calls bar?
I'm guessing that the mouse click on the overlay is noted not as being
a click on a buffer position that has the overlay but on a buffer
position that is under the displayed "xxxxxxxxx" but is actually
outside the text that has the overlay.
What I'm looking for is for the click to be perceived by Emacs as happening
on the overlay, and for the overlay's keymap to apply over the full extent
of the overlay, not just at its beginning, causing the overlay's keymap
binding to take effect.
Note that this is specifically about overlays, not text properties.
In GNU Emacs 22.1.90.1 (i386-mingw-nt5.1.2600)
of 2008-01-30 on PRETEST
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Ic:/gnuwin32/include'
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #10 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> (setq foo-map (make-sparse-keymap))
> (define-key foo-map [mouse-2] 'bar)
>
> (defun foo (beg end)
> (interactive "r")
> (let ((overlay (make-overlay beg end)))
> (overlay-put
> overlay 'display
> (propertize "xxxxxxxxx" 'face 'font-lock-constant-face))
> (overlay-put overlay 'keymap foo-map)))
>
> (defun bar (event) (interactive "e") (message "BAR"))
> ...
> I'm guessing that the mouse click on the overlay is noted not as being
> a click on a buffer position that has the overlay but on a buffer
> position that is under the displayed "xxxxxxxxx" but is actually
> outside the text that has the overlay.
First off, could you confirm that this bug, #102, is the same as #71 in
the bug tracker, at
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=71
? Thanks.
The following patch implements the behavior you are looking for: mouse
clicks on before/after strings and display strings will use the `keymap'
overlay or text property associated with the text position---unless the
string itself defines a `keymap' text property, in which case that
keymap is used instead.
Could you test it out? Please test as many combinations of
keymaps/overlays/textprops as possible. Test the output of C-h k also.
*** trunk/src/keyboard.c~ 2008-04-15 19:34:26.000000000 -0400
--- trunk/src/keyboard.c 2008-04-15 19:21:34.000000000 -0400
***************
*** 9695,9701 ****
localized_local_map = 1;
start = EVENT_START (key);
! if (CONSP (start) && POSN_INBUFFER_P (start))
{
pos = POSN_BUFFER_POSN (start);
if (INTEGERP (pos)
--- 9695,9701 ----
localized_local_map = 1;
start = EVENT_START (key);
! if (CONSP (start))
{
pos = POSN_BUFFER_POSN (start);
if (INTEGERP (pos)
*** trunk/src/keymap.c.~1.372.~ 2008-04-08 21:55:36.000000000 -0400
--- trunk/src/keymap.c 2008-04-15 14:32:22.000000000 -0400
***************
*** 1682,1705 ****
if (CONSP (position))
{
Lisp_Object string;
/* For a mouse click, get the local text-property keymap
of the place clicked on, rather than point. */
!
! if (POSN_INBUFFER_P (position))
{
! Lisp_Object pos;
! pos = POSN_BUFFER_POSN (position);
! if (INTEGERP (pos)
! && XINT (pos) >= BEG && XINT (pos) <= Z)
! {
! local_map = get_local_map (XINT (pos),
! current_buffer, Qlocal_map);
!
! keymap = get_local_map (XINT (pos),
! current_buffer, Qkeymap);
! }
}
/* If on a mode line string with a local keymap,
--- 1682,1699 ----
if (CONSP (position))
{
Lisp_Object string;
+ Lisp_Object pos = POSN_BUFFER_POSN (position);
/* For a mouse click, get the local text-property keymap
of the place clicked on, rather than point. */
! if (INTEGERP (pos)
! && XINT (pos) >= BEG && XINT (pos) <= Z)
{
! local_map = get_local_map (XINT (pos),
! current_buffer, Qlocal_map);
! keymap = get_local_map (XINT (pos),
! current_buffer, Qkeymap);
}
/* If on a mode line string with a local keymap,
***************
*** 1862,1885 ****
if (CONSP (position))
{
Lisp_Object string;
/* For a mouse click, get the local text-property keymap
of the place clicked on, rather than point. */
!
! if (POSN_INBUFFER_P (position))
{
! Lisp_Object pos;
! pos = POSN_BUFFER_POSN (position);
! if (INTEGERP (pos)
! && XINT (pos) >= BEG && XINT (pos) <= Z)
! {
! local_map = get_local_map (XINT (pos),
! current_buffer, Qlocal_map);
!
! keymap = get_local_map (XINT (pos),
! current_buffer, Qkeymap);
! }
}
/* If on a mode line string with a local keymap,
--- 1856,1873 ----
if (CONSP (position))
{
Lisp_Object string;
+ Lisp_Object pos = POSN_BUFFER_POSN (position);
/* For a mouse click, get the local text-property keymap
of the place clicked on, rather than point. */
! if (INTEGERP (pos)
! && XINT (pos) >= BEG && XINT (pos) <= Z)
{
! local_map = get_local_map (XINT (pos),
! current_buffer, Qlocal_map);
! keymap = get_local_map (XINT (pos),
! current_buffer, Qkeymap);
}
/* If on a mode line string with a local keymap,
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #15 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> First off, could you confirm that this bug, #102, is the same
> as #71 in the bug tracker, at
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=71
Yes, it is the same. Sorry for the duplicate.
> The following patch implements the behavior you are looking for: mouse
> clicks on before/after strings and display strings will use
> the `keymap'
> overlay or text property associated with the text
> position---unless the
> string itself defines a `keymap' text property, in which case that
> keymap is used instead.
>
> Could you test it out? Please test as many combinations of
> keymaps/overlays/textprops as possible. Test the output of
> C-h k also.
I can't build Emacs, sorry. If it were Lisp only, I would test it.
Thanks for fixing this.
- Drew
Merged 71 102.
Request was from
Chong Yidong <cyd <at> stupidchicken.com>
to
control <at> emacsbugs.donarmstrong.com
.
(Wed, 16 Apr 2008 13:25:06 GMT)
Full text and
rfc822 format available.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #22 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
>> The following patch implements the behavior you are looking for:
>> mouse clicks on before/after strings and display strings will use the
>> `keymap' overlay or text property associated with the text
>> position---unless the string itself defines a `keymap' text property,
>> in which case that keymap is used instead.
>>
>> Could you test it out? Please test as many combinations of
>> keymaps/overlays/textprops as possible. Test the output of
>> C-h k also.
>
> I can't build Emacs, sorry. If it were Lisp only, I would test it.
After studying this some more, I've decided to leave the current
behavior alone.
It turns out that the patch I posted earlier doesn't work for
after-strings, because the buffer position associated with an
after-string is the end of the overlay (1 + the postition of the last
character). As a result, there's no efficient way for read_key_sequence
to detect the existence of an overlay with a keymap for an after-string.
The fact that the buffer position of an after-string is the overlay end
isn't easily changed, because the redisplay engine relies on this for
efficiency (it means that the redisplay iterator can process all the
strings at a given charpos, before processing the buffer text).
Since the benefit of this feature is rather marginal in the first place,
I think it's better to simply document that display strings don't
inherit keymaps. The way to DTRT is to give the display string a
'keymap text property, which has always worked.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #27 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> After studying this some more, I've decided to leave the current
> behavior alone.
>
> It turns out that the patch I posted earlier doesn't work for
> after-strings, because the buffer position associated with an
> after-string is the end of the overlay (1 + the postition of the last
> character). As a result, there's no efficient way for
> read_key_sequence
> to detect the existence of an overlay with a keymap for an
> after-string.
>
> The fact that the buffer position of an after-string is the
> overlay end
> isn't easily changed, because the redisplay engine relies on this for
> efficiency (it means that the redisplay iterator can process all the
> strings at a given charpos, before processing the buffer text).
>
> Since the benefit of this feature is rather marginal in the
> first place,
> I think it's better to simply document that display strings don't
> inherit keymaps. The way to DTRT is to give the display string a
> 'keymap text property, which has always worked.
Could you state how that would change in the test case I sent? I added both a
`display' property and a `keymap' property to the overlay. What would the new
test-case code look like?
I'm OK with documenting a limitation if there is an easy alternative way to do
what I need.
Thx.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #32 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
>> Since the benefit of this feature is rather marginal in the first
>> place, I think it's better to simply document that display strings
>> don't inherit keymaps. The way to DTRT is to give the display string
>> a 'keymap text property, which has always worked.
>
> Could you state how that would change in the test case I sent? I added
> both a `display' property and a `keymap' property to the overlay. What
> would the new test-case code look like?
>
> I'm OK with documenting a limitation if there is an easy alternative
> way to do what I need.
It's simple:
(defun foo (beg end)
(interactive "r")
(let ((overlay (make-overlay beg end)))
(overlay-put
overlay 'display
(propertize "xxxxxxxxx" 'face 'font-lock-constant-face
'keymap foo-map))
(overlay-put overlay 'keymap foo-map)))
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
martin rudalics <rudalics <at> gmx.at>
:
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 #37 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> It's simple:
>
> (defun foo (beg end)
> (interactive "r")
> (let ((overlay (make-overlay beg end)))
> (overlay-put
> overlay 'display
> (propertize "xxxxxxxxx" 'face 'font-lock-constant-face
> 'keymap foo-map))
> (overlay-put overlay 'keymap foo-map)))
It's all in the original thread, compare:
http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg01923.html
I have at least one Emacs 22 build where this fails. Please
recheck whether it works for Emacs 22.2.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #42 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
martin rudalics <rudalics <at> gmx.at> writes:
>> (defun foo (beg end)
>> (interactive "r")
>> (let ((overlay (make-overlay beg end)))
>> (overlay-put
>> overlay 'display
>> (propertize "xxxxxxxxx" 'face 'font-lock-constant-face
>> 'keymap foo-map))
>> (overlay-put overlay 'keymap foo-map)))
>
> It's all in the original thread, compare:
>
> http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg01923.html
>
> I have at least one Emacs 22 build where this fails. Please
> recheck whether it works for Emacs 22.2.
Works for me on 22.2.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #47 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> > (defun foo (beg end)
> > (interactive "r")
> > (let ((overlay (make-overlay beg end)))
> > (overlay-put
> > overlay 'display
> > (propertize "xxxxxxxxx" 'face 'font-lock-constant-face
> > 'keymap foo-map))
> > (overlay-put overlay 'keymap foo-map)))
>
> It's all in the original thread, compare:
> http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg01923.html
Which is this:
(defun foo (beg end)
(interactive "r")
(let ((overlay (make-overlay beg end)))
(overlay-put
overlay 'display
(propertize "xxxxxxxxx" 'face 'font-lock-constant-face 'keymap foo-map))))
Yidong's suggestion still has the (overlay-put overlay 'keymap foo-map); yours
does not. Is that part needed? (Trying to understand what is needed, not just
what works on this example.)
> I have at least one Emacs 22 build where this fails. Please
> recheck whether it works for Emacs 22.2.
What is "it"? Your suggestion or Yidong's (or both)?
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
martin rudalics <rudalics <at> gmx.at>
:
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 #52 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> What is "it"? Your suggestion or Yidong's (or both)?
My suggestion works here with Emacs 23 and did not work in an Emacs 22
build from May 2007. I don't know what Chong checked and what changed
since that. Does his suggestion work for you?
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #57 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> Yidong's suggestion still has the (overlay-put overlay 'keymap
> foo-map); yours does not. Is that part needed? (Trying to understand
> what is needed, not just what works on this example.)
No. The only local keymap considered is the one on the display string.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #62 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
martin rudalics <rudalics <at> gmx.at> writes:
>> What is "it"? Your suggestion or Yidong's (or both)?
>
> My suggestion works here with Emacs 23 and did not work in an Emacs 22
> build from May 2007. I don't know what Chong checked and what changed
> since that. Does his suggestion work for you?
Have you tried 22.2?
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #67 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> My suggestion works here with Emacs 23 and did not work in an Emacs 22
> build from May 2007. I don't know what Chong checked and what changed
> since that. Does his suggestion work for you?
Your suggestion works for me in Emacs 22.2.1.
Yidong's suggestion does not work for me in Emacs 22.2.1.
Thanks for the workaround. I'm OK with having this limitation documented. That
is, the workaround should be suggested to users, IMO.
In GNU Emacs 22.2.1 (i386-mingw-nt5.1.2600)
of 2008-03-26 on RELEASE
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #72 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> Your suggestion works for me in Emacs 22.2.1.
> Yidong's suggestion does not work for me in Emacs 22.2.1.
>
> Thanks for the workaround. I'm OK with having this limitation
> documented. That is, the workaround should be suggested to users, IMO.
I should have added that both suggestions work in Emacs 23:
In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
of 2008-04-04 on LENNART-69DE564
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --no-opt --cflags -Ic:/g/include
-fno-crossjumping'
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #77 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> > My suggestion works here with Emacs 23 and did not work in
> > an Emacs 22 build from May 2007. I don't know what Chong
> > checked and what changed
> > since that. Does his suggestion work for you?
>
> Your suggestion works for me in Emacs 22.2.1.
> Yidong's suggestion does not work for me in Emacs 22.2.1.
>
> Thanks for the workaround. I'm OK with having this limitation
> documented. That is, the workaround should be suggested to users, IMO.
>
> In GNU Emacs 22.2.1 (i386-mingw-nt5.1.2600)
> of 2008-03-26 on RELEASE
> Windowing system distributor `Microsoft Corp.', version 5.1.2600
> configured using `configure --with-gcc (3.4)'
I just got an email from a user of my code who said that it does not work for
him in Emacs 22.2.1. Perhaps it is platform related? I haven't heard back from
him yet about his platform.
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; 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 #82 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
"Drew Adams" <drew.adams <at> oracle.com> writes:
> I just got an email from a user of my code who said that it does not
> work for him in Emacs 22.2.1. Perhaps it is platform related? I
> haven't heard back from him yet about his platform.
Possibly. On GNU/Linux, I've not managed to get this to fail at all.
Martin, are you running on GNU/Linux?
Information forwarded to
bug-submit-list <at> lists.donarmstrong.com, Emacs Bugs <bug-gnu-emacs <at> gnu.org>
:
bug#102
; Package
emacs
.
Full text and
rfc822 format available.
Acknowledgement sent to
"Drew Adams" <drew.adams <at> oracle.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 #87 received at 102 <at> emacsbugs.donarmstrong.com (full text, mbox):
> > > My suggestion works here with Emacs 23 and did not work in
> > > an Emacs 22 build from May 2007. I don't know what Chong
> > > checked and what changed
> > > since that. Does his suggestion work for you?
> >
> > Your suggestion works for me in Emacs 22.2.1.
> > Yidong's suggestion does not work for me in Emacs 22.2.1.
> >
> > Thanks for the workaround. I'm OK with having this limitation
> > documented. That is, the workaround should be suggested to
> users, IMO.
> >
> > In GNU Emacs 22.2.1 (i386-mingw-nt5.1.2600)
> > of 2008-03-26 on RELEASE
> > Windowing system distributor `Microsoft Corp.', version 5.1.2600
> > configured using `configure --with-gcc (3.4)'
>
> I just got an email from a user of my code who said that it
> does not work for him in Emacs 22.2.1. Perhaps it is platform
> related? I haven't heard back from him yet about his platform.
I was mistaken about this. The user is using Windows, like me, and he too
confirms that it _does_ work with Emacs 22.2.1. Sorry for the confusion.
bug closed, send any further explanations to "Drew Adams" <drew.adams <at> oracle.com>
Request was from
Chong Yidong <cyd <at> stupidchicken.com>
to
control <at> emacsbugs.donarmstrong.com
.
(Sun, 20 Apr 2008 13:45:04 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <don <at> donarmstrong.com>
to
internal_control <at> emacsbugs.donarmstrong.com
.
(Sun, 18 May 2008 14:24:02 GMT)
Full text and
rfc822 format available.
This bug report was last modified 17 years and 35 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.