From: Dmitry Gutov <dgutov@yandex.ru>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: emacs-devel@gnu.org
Subject: Re: trunk r116285: * lisp/emacs-lisp/lisp.el (lisp-completion-at-point): Symbols don't start
Date: Tue, 11 Feb 2014 16:47:24 +0200 [thread overview]
Message-ID: <87ioslaepv.fsf@yandex.ru> (raw)
In-Reply-To: <871tz995bl.fsf@web.de> (Michael Heerdegen's message of "Tue, 11 Feb 2014 13:55:42 +0100")
Michael Heerdegen <michael_heerdegen@web.de> writes:
> Whether a macro evaluates arguments isn't a question of obfuscation.
> Depending on circumstances, it's a necessity.
When a macro doesn't evaluate an argument, most of the time it's to
introduce a new local var, or define one or several globals.
IOW, please provide an example of a popular macro that isn't `defadvice'
where this will be a problem.
> I really don't think this is a good idea. This would break completion
> inside macros.
Only in some, ill-behaving ones.
> In any case, there are symbols I want to complete that
> are not boundp, like keywords, tags, faces etc, also when they appear in
> quoted structures.
Have you tried the patch? When you're inside a quoted structure, any
kinds of meaningful symbols should be offered as completions.
> `lisp--form-quoted-p' does only work inside balanced
> parentheses.
Example?
I don't see any problems if some parens are missing after point.
> IMHO, having some false positives is less problematic than
> breaking completion in some cases.
"Some"? Emacs has about as much functions as variables, not to mention
faces, features, etc.
On average, in non-quoted forms more than half of completions are false
positives.
> Maybe consider making the behavior customizable, so everybody can get
> what he wants.
Maybe. But see the beginning of this message.
next prev parent reply other threads:[~2014-02-11 14:47 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1WBHeS-0000wr-6k@vcs.savannah.gnu.org>
2014-02-06 13:41 ` trunk r116285: * lisp/emacs-lisp/lisp.el (lisp-completion-at-point): Symbols don't start Dmitry Gutov
2014-02-06 22:00 ` Stefan Monnier
2014-02-07 3:16 ` Michael Heerdegen
2014-02-07 13:22 ` Stefan Monnier
2014-02-11 3:43 ` Dmitry Gutov
2014-02-11 12:55 ` Michael Heerdegen
2014-02-11 14:47 ` Dmitry Gutov [this message]
2014-02-12 11:14 ` Michael Heerdegen
2014-02-13 5:13 ` Dmitry Gutov
2014-02-13 7:36 ` Michael Heerdegen
2014-02-13 13:33 ` Stefan Monnier
2014-02-14 3:48 ` Dmitry Gutov
2014-02-12 1:42 ` Stefan Monnier
2014-02-13 5:21 ` Dmitry Gutov
2014-02-13 12:56 ` Michael Heerdegen
2014-02-13 14:32 ` Dmitry Gutov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ioslaepv.fsf@yandex.ru \
--to=dgutov@yandex.ru \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).