[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: PC-do-completion weird behavior acronym expansion.
From: |
Romain Francoise |
Subject: |
Re: PC-do-completion weird behavior acronym expansion. |
Date: |
Mon, 03 Sep 2007 13:52:00 +0200 |
address@hidden (Michaël Cadilhac) writes:
> The following change :
> 2007-08-07 Sean O'Rourke <address@hidden>
> * complete.el (PC-lisp-complete-symbol): Complete symbol around point.
> (PC-do-completion): Add "acronym completion" for symbols and
> filenames, so e.g. "mvbl" expands to "make-variable-buffer-local".
> seems to introduce a little (but annoying) bug [...]
It introduces another annoying bug: hitting TAB when the list of
possible completions is empty signals an error. For example, if you
do (completing-read "Foo: " nil) and hit TAB, you get:
Debugger entered--Lisp error: (args-out-of-range "" 0 1)
PC-do-completion(nil)
PC-complete()
call-interactively(PC-complete)
completing-read("Foo: " nil)
eval((completing-read "Foo: " nil))
eval-last-sexp-1(nil)
eval-last-sexp(nil)
call-interactively(eval-last-sexp)
- Re: PC-do-completion weird behavior acronym expansion.,
Romain Francoise <=