[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: trunk r116285: * lisp/emacs-lisp/lisp.el (lisp-completion-at-point):

From: Dmitry Gutov
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
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Michael Heerdegen <address@hidden> 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.


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

> Maybe consider making the behavior customizable, so everybody can get
> what he wants.

Maybe. But see the beginning of this message.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]