From: storm@cua.dk (Kim F. Storm)
Cc: miles@gnu.org, monnier@iro.umontreal.ca, rms@gnu.org,
emacs-devel@gnu.org
Subject: Re: Bugs in newly added completion capabilities.
Date: Fri, 01 Jul 2005 10:14:08 +0200 [thread overview]
Message-ID: <m3u0jf6izz.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <200506301828.j5UISL305879@raven.dms.auburn.edu> (Luc Teirlinck's message of "Thu, 30 Jun 2005 13:28:21 -0500 (CDT)")
Luc Teirlinck <teirllm@dms.auburn.edu> writes:
> since the following change made relatively recently (I thought we were
> in a feature freeze, but anyway):
>
> 2005-02-22 Kim F. Storm <storm@cua.dk>
>
> * minibuf.c (Ftry_completion, Fall_completions): Allow
> both string and symbol keys in alists and hash tables.
>
> Again I am not arguing for or against the desirability of this change,
> I am trying to deal with its consequences.
I changed them to support the following change:
2005-02-22 Kim F. Storm <storm@cua.dk>
* progmodes/hideif.el (hide-ifdef-use-define-alist):
Use completing-read. Suggested by Juan-Leon Lahoz Garcia.
> There are two problems: the _nearly_ everywhere is very inconsistent
> and the exceptions at first seem totally arbitrary, so it should be
> clearly documented what the exceptions are and what the motivation for
> the exceptions is.
I don't think there were any explicit motivation (rather oversight on
my part) -- better fix the code to DTRT. Please do.
> I don't like the idea of adding "" at the beginning of a completion table.
> Here I have a good reason, which is that it changes the behavior:
>
> (try-completion "" '("aaa" "aab" "aac")) => "aa"
> (try-completion "" '("" "aaa" "aab" "aac")) => ""
>
> Of course, the person consing "" to the front of the completion table
> will have to write his code to expect the second answer.
Perhaps a check to see if first elt is lambda and second elt is a list
would be a reasonable way to recognize a lambda form.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2005-07-01 8:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-28 2:27 Bugs in newly added completion capabilities Luc Teirlinck
2005-06-28 18:47 ` Richard M. Stallman
2005-06-29 3:50 ` Luc Teirlinck
2005-06-29 20:43 ` Richard M. Stallman
2005-06-30 2:29 ` Luc Teirlinck
2005-06-30 7:48 ` Kim F. Storm
2005-06-30 7:50 ` Miles Bader
2005-06-30 12:51 ` Kim F. Storm
2005-06-30 17:19 ` Luc Teirlinck
2005-06-30 17:42 ` Stefan Monnier
2005-06-30 18:28 ` Luc Teirlinck
2005-06-30 19:42 ` Stefan Monnier
2005-07-01 8:14 ` Kim F. Storm [this message]
2005-07-01 14:59 ` Stefan Monnier
2005-07-02 12:32 ` Richard M. Stallman
2005-06-30 18:32 ` Luc Teirlinck
2005-06-30 19:43 ` Stefan Monnier
2005-07-01 4:03 ` Richard M. Stallman
2005-07-01 4:36 ` Miles Bader
2005-07-01 7:33 ` David Kastrup
2005-07-01 7:55 ` Miles Bader
2005-07-01 8:34 ` Kim F. Storm
2005-07-01 22:45 ` Richard M. Stallman
2005-07-01 8:30 ` Kim F. Storm
2005-06-30 21:29 ` Richard M. Stallman
2005-06-29 3:56 ` Luc Teirlinck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3u0jf6izz.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=miles@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.