[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lisp-complete-symbol is too loquacious in minibuffer
From: |
Stefan Monnier |
Subject: |
Re: lisp-complete-symbol is too loquacious in minibuffer |
Date: |
Thu, 22 Dec 2005 16:54:49 -0500 |
User-agent: |
Gnus/5.11 (Gnus v5.11) Emacs/22.0.50 (gnu/linux) |
>>> Stefan, there's a bug in your latest changes to this function: when a
>>> completion has been found, the *Completions* buffer is buried but its
>>> window remains visible. In previous versions, the window was deleted
>>> as well.
>>
>> If you do it the other way around you also have a bug in that it may
>> remove a window that was there before.
> It seems the only good way to handle all cases is preserving the
> window configuration before first M-TAB, and restoring it afterwards.
The *Completions* buffer may be displayed in a different frame.
Stefan
- lisp-complete-symbol is too loquacious in minibuffer, Katsumi Yamaoka, 2005/12/21
- Re: lisp-complete-symbol is too loquacious in minibuffer, Richard M. Stallman, 2005/12/22
- Re: lisp-complete-symbol is too loquacious in minibuffer, Katsumi Yamaoka, 2005/12/22
- Re: lisp-complete-symbol is too loquacious in minibuffer, Romain Francoise, 2005/12/22
- Re: lisp-complete-symbol is too loquacious in minibuffer, Katsumi Yamaoka, 2005/12/22
- Re: lisp-complete-symbol is too loquacious in minibuffer, Stefan Monnier, 2005/12/22
- Re: lisp-complete-symbol is too loquacious in minibuffer, Juri Linkov, 2005/12/22
- Re: lisp-complete-symbol is too loquacious in minibuffer,
Stefan Monnier <=
- Re: lisp-complete-symbol is too loquacious in minibuffer, Luc Teirlinck, 2005/12/22