From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [bug] YASnippet (bound to SPC) and Org in `master' Date: Tue, 25 Nov 2014 16:09:38 +0100 Message-ID: <87wq6jmi4t.fsf@selenimh.mobile.lan> References: <8661e57xom.fsf@example.com> <87r3wroevf.fsf@selenimh.mobile.lan> <86egsre568.fsf@example.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45540) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtHk0-0007wh-8l for emacs-orgmode@gnu.org; Tue, 25 Nov 2014 10:09:28 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1XtHjq-0006aG-6W for emacs-orgmode@gnu.org; Tue, 25 Nov 2014 10:09:20 -0500 Received: from plane.gmane.org ([80.91.229.3]:39678) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1XtHjp-0006a9-WB for emacs-orgmode@gnu.org; Tue, 25 Nov 2014 10:09:10 -0500 Received: from public by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1XtHjo-0003sQ-1t for emacs-orgmode@gnu.org; Tue, 25 Nov 2014 16:09:08 +0100 In-Reply-To: <86egsre568.fsf@example.com> (Sebastien Vauban's message of "Tue, 25 Nov 2014 15:16:47 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Sebastien Vauban Cc: public-emacs-orgmode-mXXj517/zsQ@plane.gmane.org, Carsten Dominik Sebastien Vauban writes: >> I don't understand why yas-expand (or yas/expand) appears in >> `org-self-insert-command'. This feature was introduced for the first >> time in 94c4f801a2a8f0e0e14b48719c22e06dd9a1e599: >> >> Tables: Fix auto-blanking of fields is yasnippet is active. >> >> When yasnippet is active, it is the official binding of TAB. That >> means, the org-mode self-insert command must know that it may >> blank table fields if the last command was yas/expand. >> >> The "must know" part is not clear to me. I tend to think we should >> remove it. > > Will you do that? I'd rather understand the issue first. I CC Carsten if he wants to chime in. The fallback plan is to do the removal and see what happens. Regards,