From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Yates Newsgroups: gmane.emacs.devel Subject: Re: Emacs completion matches selection UI Date: Sat, 28 Dec 2013 11:43:36 -0500 Message-ID: References: <87fvqtg02v.fsf@flea.lifelogs.com> <874n67n450.fsf@flea.lifelogs.com> <87eh5bkxca.fsf@flea.lifelogs.com> <87d2kuzzqj.fsf@uwakimon.sk.tsukuba.ac.jp> <87a9fylusq.fsf@flea.lifelogs.com> <878uvizrwz.fsf@uwakimon.sk.tsukuba.ac.jp> <8761qmkyn1.fsf@flea.lifelogs.com> <87zjnyxdpb.fsf@uwakimon.sk.tsukuba.ac.jp> <87k3f2j7xv.fsf@flea.lifelogs.com> <2518D79A-B9E4-45DF-A403-8330145DFD17@gmail.com> <87eh58j0x3.fsf@flea.lifelogs.com> <87mwjvfrfy.fsf@flea.lifelogs.com> <877gawbhp0.fsf@flea.lifelogs.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=047d7b86e4ca85d7ab04ee9ae91c X-Trace: ger.gmane.org 1388249016 3512 80.91.229.3 (28 Dec 2013 16:43:36 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sat, 28 Dec 2013 16:43:36 +0000 (UTC) Cc: Emacs developers To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 28 17:43:43 2013 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VwwzH-0002Sc-Ed for ged-emacs-devel@m.gmane.org; Sat, 28 Dec 2013 17:43:43 +0100 Original-Received: from localhost ([::1]:52646 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VwwzG-0002GG-Un for ged-emacs-devel@m.gmane.org; Sat, 28 Dec 2013 11:43:42 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:38196) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VwwzD-0002G9-Oh for emacs-devel@gnu.org; Sat, 28 Dec 2013 11:43:40 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VwwzC-0000kB-MI for emacs-devel@gnu.org; Sat, 28 Dec 2013 11:43:39 -0500 Original-Received: from mail-wg0-x22c.google.com ([2a00:1450:400c:c00::22c]:45286) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VwwzC-0000k5-Fc for emacs-devel@gnu.org; Sat, 28 Dec 2013 11:43:38 -0500 Original-Received: by mail-wg0-f44.google.com with SMTP id a1so8875950wgh.23 for ; Sat, 28 Dec 2013 08:43:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=M6Gj6IC8yOZC6ozAFusgwSjEfDrKdw1qpjtP0IBRSe0=; b=Ubz1V99/HhU8Mqz0GuGOD+A+9XAufKa8BPAbkbfa/JShFsZ2KFqcbOt+56GHOZZJEM jEbDs5hjGxc4mGNB7zZc2YSaPkOgmLC/vNVoflosFARhlwg7FieRFVAS0+6Olz5papEg nUNUxtSQoWViiP5SQRsvNKpazX6ATYjCAMisiVt9N5k2OA8J7oBmAOU+A2tn8hQUnARd ojSQWXCT4f3XWkLX6qFlyeZj/7TODvQ2k5X2sLb/Li6EzAwv06p5RmPiz7ssGpcdR59I 9K2bJgM0VAP7JEc5C7Wz7HHodz1GBURawl5mJ05ZvXezteFAau4IBQPBzIh0LM8PRkRn 8yyw== X-Received: by 10.194.62.70 with SMTP id w6mr13788889wjr.55.1388249017077; Sat, 28 Dec 2013 08:43:37 -0800 (PST) Original-Received: by 10.194.88.165 with HTTP; Sat, 28 Dec 2013 08:43:36 -0800 (PST) In-Reply-To: X-Google-Sender-Auth: LyKp6A87ntUbkz1gASdoqcz8D_0 X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a00:1450:400c:c00::22c X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:166953 Archived-At: --047d7b86e4ca85d7ab04ee9ae91c Content-Type: text/plain; charset=ISO-8859-1 On Sat, Dec 28, 2013 at 9:02 AM, Stefan Monnier wrote: > Ah, right, the conflict is in the meaning of the TAB key. > There are two issues there: > 1- the fact that there's no standard way to *extend* the meaning of > TAB, so autocomplete and yasnippet may both *redefine* the key instead. > 2- even if the two manage to redefine TAB "at the same time", the > resulting behavior may prove too DWIMish. > This seems to be an instance of a general pattern, namely a succession of completion mechanisms desiring to be attempted based on a particular triggering event. Does it not then follow that part of creating a more uniform completion experience ought to include direct Emacs support for that pattern? The alternative is today's hodgepodge of per-package idiosyncratic redefinition mechanisms. /john --047d7b86e4ca85d7ab04ee9ae91c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On S= at, Dec 28, 2013 at 9:02 AM, Stefan Monnier <monnier@iro.umontrea= l.ca> wrote:
Ah, right, the conflict is in the meaning of the TAB key.<= br> There are two issues there:
1- the fact that there's no standard way to *extend* the meaning of
=A0 =A0TAB, so autocomplete and yasnippet may both *redefine* the key inste= ad.
2- even if the two manage to redefine TAB "at the same time", the=
=A0 =A0resulting behavior may prove too DWIMish.

<= /div>
This seems to be an instance of a general pattern, namely a succe= ssion of completion mechanisms desiring to be attempted based on a particul= ar triggering event.
=A0Does it not then follow that part of creating a more uniform comple= tion experience ought to include direct Emacs support for that pattern? =A0= The alternative is today's hodgepodge of per-package idiosyncratic rede= finition mechanisms.

/john
--047d7b86e4ca85d7ab04ee9ae91c--