GNU bug report logs -
#18265
24.3.92; lisp-completion-at-point should return nil in comments, unless after `
Previous Next
Reported by: Dmitry <dgutov <at> yandex.ru>
Date: Thu, 14 Aug 2014 12:27:01 UTC
Severity: minor
Found in version 24.3.92
Fixed in version 25.1
Done: Dmitry Gutov <dgutov <at> yandex.ru>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
[Message part 1 (text/plain, inline)]
Your message dated Fri, 19 Sep 2014 07:56:12 +0400
with message-id <541BA95C.30400 <at> yandex.ru>
and subject line Re: bug#18265: 24.3.92; lisp-completion-at-point should return nil in comments, unless after `
has caused the debbugs.gnu.org bug report #18265,
regarding 24.3.92; lisp-completion-at-point should return nil in comments, unless after `
to be marked as done.
(If you believe you have received this mail in error, please contact
help-debbugs <at> gnu.org.)
--
18265: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=18265
GNU Bug Tracking System
Contact help-debbugs <at> gnu.org with problems
[Message part 2 (message/rfc822, inline)]
https://github.com/company-mode/company-mode/issues/167
`company-elisp' does that, by the way.
In GNU Emacs 24.3.92.4 (x86_64-unknown-linux-gnu, GTK+ Version 3.10.8)
of 2014-08-06 on axl
Repository revision: 117425 eliz <at> gnu.org-20140805133406-w7477hyd1gl9h1d7
Windowing system distributor `The X.Org Foundation', version 11.0.11501000
System Description: Ubuntu 14.04.1 LTS
[Message part 3 (message/rfc822, inline)]
Version: 24.5
On 08/16/2014 10:00 PM, Stefan Monnier wrote:
> While it's "counter to the c-a-p-f interface", the need to combine
> several backends is sufficiently common that we need to support it somehow.
>
> I hope a "merge" solution can use a less hackish solution than the
> current ":exclusive no".
I'm not convinced with this approach. At least, AFAICS, different users
prefer to merge different backends together. For instance, some
https://github.com/iquiw/company-ghc users like to merge its results
with the plain company-dabbrev-code. Some, I believe, don't.
If the completion function gets to decide that, it would be harder for
users to customize.
>> And anyway, it doesn't seem to help with the distinction between manual and
>> idle completion,
>
> Indeed, it's a largely orthogonal issue.
I've installed the in-string-or-comment piece of logic that's been
missing compared to company-elisp, so this bug should be settled.
The distinction between manual and idle completion doesn't seem to be
very useful here, so let's leave that until there's a definite demand
for it.
This bug report was last modified 10 years and 229 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.