David Kastrup <[EMAIL PROTECTED]> writes:
>> That's actually what I have at the moment.
>>
>> (if (fboundp 'completing-read-multiple)
>> (defalias 'TeX-completing-read-multiple 'completing-read-multiple)
>> (defun TeX-completing-read-multiple
>> (prompt table &optional predicate require-match initial-input
>> hist def inherit-input-method)
>> "Poor mans implementation of Emacs' `completing-read-multiple' for
>> XEmacs."
>> (require 'multi-prompt)
>> (multi-prompt "," nil prompt table predicate require-match initial-input
>> hist)))
>
> Not quite the same. Don't use "require" in functions. It is a
> permanent performance hog when compared to calling an autoload, and it
> does not make the byte compiler happy.
Thanks. I didn't know that.
It is not necessary anyway since multi-prompt is in auto-loads.el.
>> I just dicovered a difference in `multi-prompt' and `crm'. If the
>> second argument of `multi-prompt' is non-nil the values you are
>> completing on are supposed to be unique and there is no way to
>> specify that in `completing-read-multiple' so we cannot replace the
>> two occurences of `multi-prompt' in latex.el with
>> `completing-read-multiple' without loosing that.
>
> What is the user-visible difference in behavior?
If one possible completion is "foo" you cannot complete on it more
than once (i.e. "foo,Co<TAB>") if `multi-prompt' is called with unique
set to non-nil. It still possible to enter it
though. `completing-read-multiple' cannot restrict the completion in
that way. Both calls of `multi-prompt' in latex.el uses unique.
Kind regards,
/arne
--
Arne Jørgensen <http://arnested.dk/>
_______________________________________________
auctex-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/auctex-devel
