* bug#3662: Possible problem with ido-completing-read
@ 2009-06-23 21:37 Peter Milliken
2009-06-24 7:08 ` Stephen Berman
2010-12-04 11:42 ` Leo
0 siblings, 2 replies; 5+ messages in thread
From: Peter Milliken @ 2009-06-23 21:37 UTC (permalink / raw
To: emacs-pretest-bug
[-- Attachment #1: Type: text/plain, Size: 4490 bytes --]
--text follows this line--
Please write in English if possible, because the Emacs maintainers
usually do not have translators to read other languages for them.
Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing
list.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
This bug is also present in Emacs 22.3. I am attempting to use
ido-completing-read in a defun and the function "hangs" at the prompt
i.e. it does no completion at all, it will not allow me to cancel the
command, or accept a string typed in followed by RET.
I have produced a small test function to attempt to minimise possible
problems on my part:
(defun test ()
(interactive)
(let ((a)(d))
(setq d '("abc" "xyz" "abe" "def"))
(setq a (ido-completing-read "prompt: " d))))
My *understanding* of reading the defun documentation is that I should
be able to type "a<TAB>" (at the prompt) and have a completion list of
"abc" and "abe" offered. But this does not happen, all I get is "a
TAB". If I hit C-g nothing happens, the prompt line remains at the
command line. I compiled the above with debug on and received the
following trace when I hit C-g:
Debugger entered--Lisp error: (quit)
apply(debug error (quit))
edebug(error (quit))
signal(quit nil)
edebug-signal(quit nil)
signal(quit nil)
keyboard-quit()
call-interactively(keyboard-quit nil nil)
completing-read("prompt: " (("dummy" . 1)) nil nil nil nil)
byte-code(" \b \" lj\n \x12\v&\x06 " [item prompt ido-text-init history
completing-read ido-make-prompt (("dummy" . 1)) nil] 7)
ido-read-internal(list "prompt: " nil nil nil nil)
ido-completing-read("prompt: " ("abc" "xyz" "abe" "def"))
(edebug-after (edebug-before 4) 6 (ido-completing-read "prompt: "
(edebug-after 0 5 d)))
(setq a (edebug-after (edebug-before 4) 6 (ido-completing-read "prompt: "
...)))
(edebug-after (edebug-before 3) 7 (setq a (edebug-after ... 6 ...)))
(let ((a) (d)) (edebug-after (edebug-before 1) 2 (setq d ...))
(edebug-after (edebug-before 3) 7 (setq a ...)))
(edebug-after (edebug-before 0) 8 (let (... ...) (edebug-after ... 2 ...)
(edebug-after ... 7 ...)))
(lambda nil (edebug-after (edebug-before 0) 8 (let ... ... ...)))()
edebug-enter(test nil (lambda nil (edebug-after (edebug-before 0) 8 (let
... ... ...))))
edebug-enter(test nil (lambda nil (edebug-after (edebug-before 0) 8 (let
... ... ...))))
test()
call-interactively(test t nil)
execute-extended-command(nil)
call-interactively(execute-extended-command nil nil)
If Emacs crashed, and you have the Emacs process in the gdb debugger,
please include the output from the following gdb commands:
`bt full' and `xbacktrace'.
If you would like to further debug the crash, please read the file
c:/emacs/etc/DEBUG for instructions.
In GNU Emacs 23.0.95.1 (i386-mingw-nt5.1.2600)
of 2009-06-20 on SOFT-MJASON
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4)'
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: ENA
value of $XMODIFIERS: nil
locale-coding-system: cp1252
default-enable-multibyte-characters: t
Major mode: Emacs-Lisp
Minor modes in effect:
show-paren-mode: t
desktop-save-mode: t
recentf-mode: t
tooltip-mode: t
tool-bar-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
global-auto-composition-mode: t
auto-composition-mode: t
auto-encryption-mode: t
auto-compression-mode: t
column-number-mode: t
line-number-mode: t
C-u <escape> C-x <escape> x t e s t <return> g a <tab>
C-g <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <help-echo> <help-echo> <help-echo>
<help-echo> <help-echo> <menu-bar> <help-menu> <se
nd-emacs-bug-report>
Recent messages:
Local value of py-indent-offset set to 2
Using the CPython shell
Fill column set to 80 (was 70) [9 times]
Wrote c:/usr/local/.emacs.desktop.lock
Desktop: 51 buffers restored.
Loading c:/usr/local/.session...done
For information about GNU Emacs and the GNU system, type C-h C-a.
Edebug: test
Go...
Entering debugger...
[-- Attachment #2: Type: text/html, Size: 6273 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#3662: Possible problem with ido-completing-read
2009-06-23 21:37 bug#3662: Possible problem with ido-completing-read Peter Milliken
@ 2009-06-24 7:08 ` Stephen Berman
2009-06-24 19:45 ` Peter Milliken
2010-12-04 11:42 ` Leo
1 sibling, 1 reply; 5+ messages in thread
From: Stephen Berman @ 2009-06-24 7:08 UTC (permalink / raw
To: Peter Milliken; +Cc: emacs-pretest-bug, 3662
On Wed, 24 Jun 2009 07:37:42 +1000 Peter Milliken <peter.milliken@gmail.com> wrote:
> This bug is also present in Emacs 22.3. I am attempting to use
> ido-completing-read in a defun and the function "hangs" at the prompt
> i.e. it does no completion at all, it will not allow me to cancel the
> command, or accept a string typed in followed by RET.
>
> I have produced a small test function to attempt to minimise possible
> problems on my part:
>
> (defun test ()
> (interactive)
> (let ((a)(d))
> (setq d '("abc" "xyz" "abe" "def"))
> (setq a (ido-completing-read "prompt: " d))))
>
> My *understanding* of reading the defun documentation is that I should
> be able to type "a<TAB>" (at the prompt) and have a completion list of
> "abc" and "abe" offered. But this does not happen, all I get is "a
> TAB". If I hit C-g nothing happens, the prompt line remains at the
> command line.
I get this behavior as well (with GNU Emacs 23.1.50.1
(i686-pc-linux-gnu, GTK+ Version 2.14.4) of 2009-06-23 on escher).
However, if I add `(ido-mode 1)' before the first setq, then it works as
I assume it's supposed to: typing `M-x test' shows "prompt: {abc | xyz |
abe | def}" in the minibuffer, and then typing `a' (without subsequent
TAB) shows "prompt: a[b] {abc | abe}", and `C-g' quits the minibuffer.
Steve Berman
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#3662: Possible problem with ido-completing-read
2009-06-24 7:08 ` Stephen Berman
@ 2009-06-24 19:45 ` Peter Milliken
2009-06-24 22:57 ` Lennart Borgman
0 siblings, 1 reply; 5+ messages in thread
From: Peter Milliken @ 2009-06-24 19:45 UTC (permalink / raw
To: Stephen Berman; +Cc: emacs-pretest-bug, 3662
[-- Attachment #1: Type: text/plain, Size: 2038 bytes --]
Thanks Steve - that allows it to work.
Although the description for 'ido-mode is "Toggle ido speed-ups on or
off..."
So maybe if I waited a year or two ("speed-ups" must be off by default) then
I would have eventually received the correct prompt/behaviour? :-)
Obviously invoking ido-mode has some undescribed side-effect that allows the
completing-read to work. Hopefully somebody will either fix this problem or
put in a description in ido-completing-read that you have to turn on
speed-ups first!
Thanks greatly - I can now get my original defun working! :-)
Peter
On Wed, Jun 24, 2009 at 5:08 PM, Stephen Berman <stephen.berman@gmx.net>wrote:
> On Wed, 24 Jun 2009 07:37:42 +1000 Peter Milliken <
> peter.milliken@gmail.com> wrote:
>
> > This bug is also present in Emacs 22.3. I am attempting to use
> > ido-completing-read in a defun and the function "hangs" at the prompt
> > i.e. it does no completion at all, it will not allow me to cancel the
> > command, or accept a string typed in followed by RET.
> >
> > I have produced a small test function to attempt to minimise possible
> > problems on my part:
> >
> > (defun test ()
> > (interactive)
> > (let ((a)(d))
> > (setq d '("abc" "xyz" "abe" "def"))
> > (setq a (ido-completing-read "prompt: " d))))
> >
> > My *understanding* of reading the defun documentation is that I should
> > be able to type "a<TAB>" (at the prompt) and have a completion list of
> > "abc" and "abe" offered. But this does not happen, all I get is "a
> > TAB". If I hit C-g nothing happens, the prompt line remains at the
> > command line.
>
> I get this behavior as well (with GNU Emacs 23.1.50.1
> (i686-pc-linux-gnu, GTK+ Version 2.14.4) of 2009-06-23 on escher).
> However, if I add `(ido-mode 1)' before the first setq, then it works as
> I assume it's supposed to: typing `M-x test' shows "prompt: {abc | xyz |
> abe | def}" in the minibuffer, and then typing `a' (without subsequent
> TAB) shows "prompt: a[b] {abc | abe}", and `C-g' quits the minibuffer.
>
> Steve Berman
>
[-- Attachment #2: Type: text/html, Size: 2774 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#3662: Possible problem with ido-completing-read
2009-06-24 19:45 ` Peter Milliken
@ 2009-06-24 22:57 ` Lennart Borgman
0 siblings, 0 replies; 5+ messages in thread
From: Lennart Borgman @ 2009-06-24 22:57 UTC (permalink / raw
To: Peter Milliken, 3662; +Cc: emacs-pretest-bug, Stephen Berman
On Wed, Jun 24, 2009 at 9:45 PM, Peter Milliken<peter.milliken@gmail.com> wrote:
> Thanks Steve - that allows it to work.
> Although the description for 'ido-mode is "Toggle ido speed-ups on or
> off..."
> So maybe if I waited a year or two ("speed-ups" must be off by default) then
> I would have eventually received the correct prompt/behaviour? :-)
> Obviously invoking ido-mode has some undescribed side-effect that allows the
> completing-read to work. Hopefully somebody will either fix this problem or
> put in a description in ido-completing-read that you have to turn on
> speed-ups first!
> Thanks greatly - I can now get my original defun working! :-)
> Peter
As things are managed now it might be best to report this as a bug.
Some bugs will have "wish-list" status, but that is ok, then they can
be remembered at least.
^ permalink raw reply [flat|nested] 5+ messages in thread
* bug#3662: Possible problem with ido-completing-read
2009-06-23 21:37 bug#3662: Possible problem with ido-completing-read Peter Milliken
2009-06-24 7:08 ` Stephen Berman
@ 2010-12-04 11:42 ` Leo
1 sibling, 0 replies; 5+ messages in thread
From: Leo @ 2010-12-04 11:42 UTC (permalink / raw
To: 3662; +Cc: Peter Milliken
Hello Peter,
This looks like a duplicate of bug#3274:
http://debbugs.gnu.org/cgi/bugreport.cgi?bug=3274.
Could you confirm it has been fixed in the emacs-23 branch in commit
http://repo.or.cz/w/emacs.git/commit/df923d23a29b20448c3382710d74ba963b065326.
Cheers,
Leo
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2010-12-04 11:42 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2009-06-23 21:37 bug#3662: Possible problem with ido-completing-read Peter Milliken
2009-06-24 7:08 ` Stephen Berman
2009-06-24 19:45 ` Peter Milliken
2009-06-24 22:57 ` Lennart Borgman
2010-12-04 11:42 ` Leo
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.