[Top][All Lists]

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

Re: Completion with (:exclusive 'no) is called twice, and doesn't pass o

From: Vitalie Spinu
Subject: Re: Completion with (:exclusive 'no) is called twice, and doesn't pass over on sole completion.
Date: Sun, 18 Mar 2012 10:35:02 +0100
User-agent: Gnus/5.130004 (Ma Gnus v0.4) Emacs/24.0.94 (gnu/linux)

>>>> Stefan Monnier <address@hidden>
>>>> on Sat, 17 Mar 2012 22:03:44 -0400 wrote:

  >> A related issue. Position after 'aaaa, try to complete. You will get a
  >> "Sole completion" message.  Press "space" or "M-b", or whatever, you will
  >> get a message "aaaa:" which means that completion is repeated after any
  >> other command.  This is really bad, as my completion is calling an
  >> external process and stalls emacs for a second, badly interfering with
  >> the editing.

  > Again, you're confused: the completion-at-point-functions do not perform
  > completion, they just return the data about what completion table to use
  > at point.

Ok, I see it more clearly now, with your auto-complete point latter,
thanks. Will rewrite and see if it gets better.


  >> I've written auto-complete support and emacs-24 completion at point
  >> for R.  And it turned out that these two are really distinct features.
  >> One is fast, cache based and sloppy, as it should not interfere with
  >> the editing.  Another one is exact and might be very slow, because it
  >> contacts the associated process.  The TAB completions can afford to be
  >> slow, as there is no editing.

  > Interesting.

  > So the completion candidates displayed in R-mode for auto-complete are
  > different than the ones used for TAB?

Yes, and no. What I meant is that the underlying mechanisms are very
different.  99.99% of the time the completion candidates are the same,
but there are objects which are not meaningful to cache, like arguments
of the user functions, or components of the recursive structures (lists,
environments, data.frames etc.). In this cases AC also calls the
process, and it's usually fast. But in some extreme corner cases, like
if user changed a function in an attached package, AC will still use the
cached version.'

  > Hmm... more consistency in the naming might be good here, indeed.
  > It's important to keep the "<package>-" prefix since I don't want to
  > consider all of this as part of Emacs's "core", but maybe we could
  > settle on "<something>-completion-at-point-function" or maybe something
  > shorter than that.

I am a fan of the -completion postfix convention. It's easy to match in
apropos, anything or IDO regexp: comint-filename-completion,
tags-completion, imenu-completion, imenu-in-same-mode-completion,
words-in-same-buffer-commpletion etc. It can get pretty long by itself,
so a short postfix is better.


reply via email to

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