From: Leo <sdl.web@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 4664@emacsbugs.donarmstrong.com,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#4664: 23.1.50; local variables completions
Date: Mon, 12 Oct 2009 16:49:37 +0100 [thread overview]
Message-ID: <xbaihbu44nou.fsf@cam.ac.uk> (raw)
In-Reply-To: <87my3xo59s.fsf@mail.jurta.org> (Juri Linkov's message of "Mon, 12 Oct 2009 02:54:55 +0300")
On 2009-10-12 00:54 +0100, Juri Linkov wrote:
>>> This is a wrong fix. It again removes valid local variables like
>>> `generated-autoload-file' from completion. The right fix would be
>>> just to avoid trying to provide their current value as the default
>>> value:
>>
>> Agreed. Actually even if a symbol is not known to be safe and not
>> completable, it should be possible for the user to use it, since it may
>> simply not be loaded yet.
>
> Yes, this is already the case: the user is free to enter any variable.
> It is only completion with require-match=nil that provides a list
> of known variable names.
The completion of 'mode' does not include modes like outline-minor-mode.
Is this an oversight?
Leo
next prev parent reply other threads:[~2009-10-12 15:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xbaipr8yncbp.fsf@cam.ac.uk>
2009-10-07 11:15 ` bug#4664: 23.1.50; local variables completions Leo
2009-10-07 14:34 ` Stefan Monnier
[not found] ` <87pr8yanj1.fsf@mail.jurta.org>
2009-10-08 1:10 ` Stefan Monnier
2009-10-08 6:54 ` Leo
2009-10-08 9:22 ` Juri Linkov
2009-10-08 11:58 ` Leo
2009-10-09 19:26 ` Stefan Monnier
2009-10-11 23:54 ` Juri Linkov
2009-10-12 15:49 ` Leo [this message]
2009-10-12 20:31 ` Juri Linkov
2009-10-13 11:17 ` Leo
2009-10-13 19:52 ` Stefan Monnier
2009-10-13 22:35 ` Juri Linkov
2009-10-14 1:16 ` Leo
2009-10-07 21:15 ` bug#4664: marked as done (23.1.50; local variables completions) Emacs bug Tracking System
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=xbaihbu44nou.fsf@cam.ac.uk \
--to=sdl.web@gmail.com \
--cc=4664@emacsbugs.donarmstrong.com \
--cc=juri@jurta.org \
--cc=monnier@IRO.UMontreal.CA \
/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.