From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: Completing with anything
Date: Tue, 24 May 2011 00:14:52 -0300
Message-ID: <jwvlixwhk5j.fsf-monnier+@gnu.org>
References: <87r5bhysp6.fsf@keller.adm.naquadah.org>
	<m1wrl8c5ix.fsf@94.197.191.21.threembb.co.uk>
	<878vxovsym.fsf@keller.adm.naquadah.org>
	<87k4h7ua23.fsf@member.fsf.org>
	<87vd0romky.fsf@keller.adm.naquadah.org>
	<jwv4o8bvjn1.fsf-monnier+emacs@gnu.org>
	<87mxm2na63.fsf@member.fsf.org>
	<jwv8vxmr5vp.fsf-monnier+emacs@gnu.org>
	<87vd0qfhu3.fsf@member.fsf.org>
	<jwvlj1mp41j.fsf-monnier+emacs@gnu.org>
	<sa3ipvg8oe5.fsf_-_@cigue.easter-eggs.fr>
	<jwv62rgguvg.fsf-monnier+emacs@gnu.org>
	<sa362rcg1k2.fsf@cigue.easter-eggs.fr>
	<jwvaago1q4p.fsf-monnier+emacs@gnu.org>
	<sa3y648bh9p.fsf@cigue.easter-eggs.fr>
	<87y63jpii5.fsf@keller.adm.naquadah.org>
	<jwv39lq69dv.fsf-monnier+emacs@gnu.org>
	<sa3aafx2lf9.fsf@cigue.easter-eggs.fr>
	<jwvwrj0ywdc.fsf-monnier+emacs@gnu.org>
	<sa3wrizpzpi.fsf@cigue.easter-eggs.fr>
	<jwv8vumv7bm.fsf-monnier+emacs@gnu.org>
	<871v0ecwe4.fsf@keller.adm.naquadah.org>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
In-Reply-To: <871v0ecwe4.fsf@keller.adm.naquadah.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: </archive/html/emacs-devel>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=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: Julien Danjou <julien@danjou.info>
Cc: Tassilo Horn <tassilo@member.fsf.org>, emacs-orgmode@gnu.org, emacs-devel@gnu.org
List-Id: emacs-orgmode.gnu.org

> > So at least cycling-completion seems fundamentally incompatible with
> > this idea of abbrev-expansion-after-completion, at least if you want to
> > allow arbitrarily complex abbrevs like skeletons.
> Indeed, this is a real problem.

I've now added a :exit-function property that
completion-at-point-functions can return which is a function that gets
called when completion is finished.  It operates outside of the
completion-table, so has access to the buffer text and can do things
like abbrev-expand.

It gets a status argument which tells it whether the completion is
`exact' (basically, it's valid according to the completion-table, but
there may be further completions available), `sole' (it's the only
completion), and `finished' (not only it's the sole completion, but the
user is not expected to want to change it).  `sole' is used by cycling,
so the :exit-function can call abbrev-expand when the status is
`finished' and it won't interfere with cycling (which simply won't
benefit from abbrev-expansion).


        Stefan