bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#1080: marked as done (23.0.60; completing-read-multiple is wrong wi


From: Emacs bug Tracking System
Subject: bug#1080: marked as done (23.0.60; completing-read-multiple is wrong with mouse-2 in *Completions*)
Date: Mon, 16 Mar 2009 00:55:08 +0000

Your message dated Sun, 15 Mar 2009 20:48:59 -0400
with message-id <address@hidden>
and subject line Re: 23.0.60; completing-read-multiple is wrong with mouse-2 in 
*Completions*
has caused the Emacs bug report #1080,
regarding 23.0.60; completing-read-multiple is wrong with mouse-2 in 
*Completions*
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
1080: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=1080
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 23.0.60; completing-read-multiple is wrong with mouse-2 in *Completions* Date: Sat, 4 Oct 2008 09:12:07 -0700
emacs -Q
 
Evaluate this:
(completing-read-multiple "Choose: " '("Lllll" Dddddd "Rrrrrr"))
 
Type: `Lll TAB , Ddd TAB ,'
and then choose `Rrrrrr' with `mouse-2' in *Completions*.
 
The result returned is ("Rrrrrr"), not ("Lllll" Dddddd "Rrrrrr") as it
presumably should be.

It seems like `completing-read-multiple' should use a special
keymap for *Completions*, just like it does with
`crm-local-completion-map' and `crm-local-must-match-map'
for the minibuffer, and in that new keymap, `mouse-2' should
DTRT. IOW, treat `mouse-2' similarly to how TAB is treated.
 

In GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600)
 of 2008-10-03 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'
 




--- End Message ---
--- Begin Message --- Subject: Re: 23.0.60; completing-read-multiple is wrong with mouse-2 in *Completions* Date: Sun, 15 Mar 2009 20:48:59 -0400
> (completing-read-multiple "Choose: " '("Lllll" Dddddd "Rrrrrr"))
> 
> Type: `Lll TAB , Ddd TAB ,'
> and then choose `Rrrrrr' with `mouse-2' in *Completions*.
> 
> The result returned is ("Rrrrrr"), not ("Lllll" Dddddd "Rrrrrr") as it
> presumably should be.
>
> It seems like `completing-read-multiple' should use a special
> keymap for *Completions*, just like it does with
> `crm-local-completion-map' and `crm-local-must-match-map'
> for the minibuffer, and in that new keymap, `mouse-2' should
> DTRT. IOW, treat `mouse-2' similarly to how TAB is treated.

Fixed, thanks for the report.

Note that the new crm--choose-completion-string function does not exit
the minibuffer, unlike the usual completion string chooser.  Instead, it
just completes into the minibuffer.  This behavior seems more suitable
for completing-read-multiple.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]