From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Monnier Subject: Re: Completing with anything Date: Tue, 24 May 2011 09:47:06 -0300 Message-ID: References: <87r5bhysp6.fsf@keller.adm.naquadah.org> <87vd0romky.fsf@keller.adm.naquadah.org> <87mxm2na63.fsf@member.fsf.org> <87vd0qfhu3.fsf@member.fsf.org> <87y63jpii5.fsf@keller.adm.naquadah.org> <871v0ecwe4.fsf@keller.adm.naquadah.org> <87aaecihl2.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: In-Reply-To: <87aaecihl2.fsf@gmail.com> (Antoine Levitt's message of "Tue, 24 May 2011 11:16:41 +0200") List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org To: Antoine Levitt Cc: emacs-orgmode@gnu.org, emacs-devel@gnu.org List-Id: emacs-orgmode.gnu.org > So, could you add 'failed, which means that no function was able to > complete? That way I could do something like > (setq completion-extra-properties '(:exit-function my-exit-function)) > (defun my-exit-function (string finished) > (when (eq finished 'failed) > (dabbrev-expand))) > and always get a dabbrev-expand as fallback to completion-at-point? Hmm... interesting way to attack that problem. I don't think that will work quite like this: if the completion provides its own :exit-function (e.g. to add a terminator string), then yours won't be run. Stefan