From mboxrd@z Thu Jan 1 00:00:00 1970 From: Julien Danjou Subject: Re: Re: Completing with anything Date: Wed, 04 May 2011 17:34:27 +0200 Message-ID: <871v0ecwe4.fsf@keller.adm.naquadah.org> References: <87r5bhysp6.fsf@keller.adm.naquadah.org> <878vxovsym.fsf@keller.adm.naquadah.org> <87k4h7ua23.fsf@member.fsf.org> <87vd0romky.fsf@keller.adm.naquadah.org> <87mxm2na63.fsf@member.fsf.org> <87vd0qfhu3.fsf@member.fsf.org> <87y63jpii5.fsf@keller.adm.naquadah.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha1; protocol="application/pgp-signature" Return-path: In-Reply-To: (Stefan Monnier's message of "Wed, 04 May 2011 12:07:23 -0300") 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: Stefan Monnier Cc: Tassilo Horn , emacs-orgmode@gnu.org, emacs-devel@gnu.org List-Id: emacs-orgmode.gnu.org --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable On Wed, May 04 2011, Stefan Monnier wrote: > 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. > Could you give me an idea of what kind of abbrevs the code should try > to accommodate? IIUC, your nic/nicolas example perfectly fits in. This is what I tried to achieve in message-mode (using org-contacts as the database). Maybe what's needed is a different completion type, which would be a built on top of both completion and abbrev. It would try to complete based on an abbrev list until there's no possible doubt about the alias the users wants, and finally would do the expand-abbrev operation. At least, that sounds like a completion mode we would need in message-mode case. =2D-=20 Julien Danjou =E2=9D=B1 http://julien.danjou.info --=-=-= Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQIcBAEBAgAGBQJNwXIDAAoJEGEbqVCLeKXCp4YP/RBB2VUQtt0SZ6aqoigl6ofb SM+a8VyCWVLNkklSm2cMso17wHDQFOZOWpD6CHN1FF+XlUTBOnxEmgKKewM2s4Bn M6/r8/gpByzQvetOevHqoAP+2QwKwUQ/NZtrwqln/VjE6H/HLbV4jjPqF6+RalsZ sRnVmb67EWxZIfsspbHTPJiwe5wnrPbiYpUYAzdXZIVNPo9biyRcCSyXRZgzAuef NbLCFlSBg5dbZPxHMxtYqm0IXOK34JPc8Ca5hwALEzSN8ISZQmoRfqqurfwet6CD hdGmKqG1xziWkpfrGIjbyvoOvah9RQnXzG3uWFj7/ui1a0Mpn7E/GfBl1vv6SKKS 1yykFZF2JTVJJVLOY13LRC+PlKSoMLXnaHDEjSMzOiceWygKryWJ4MzWUu7tjIBu xmc2cmRTR4Z+mYqVgzRr2ff5ZrhsyJr+eb3XPlyuSOW0ptlRX79DxHA79vPIqZZk 8XLqK1ukSSnLjZgJzv5iju8HyXwvG1201yWLs9fZhNxg5u61yoj/OtHL6YaI6yzq o6q1HLIfg/sQLGt0wrwa1prmRr+C8+/pjJ+vQcXvV/8CagSX4Vq67qkVM1Z1itWi x3oHORNUxIRl8V2AQSO+EAvLTa7wGXsIrqr5vsoTbANL3VbSO64YasGprL17FQ9z dDGnAD/pdrd6ClHDoyXY =GJMY -----END PGP SIGNATURE----- --=-=-=--