From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: [patch] extend org-meta-return to keywords Date: Sun, 23 Nov 2014 22:54:20 +0100 Message-ID: <87a93h60s3.fsf@gmx.us> References: <87egszw8ui.fsf@gmx.us> <87wq6o3u57.fsf@gmx.us> <87fvdb4l6c.fsf@nicolasgoaziou.fr> <87sihb4ede.fsf@pank.eu> <87lhn36nq1.fsf@gmx.us> <87bnny4ybq.fsf@nicolasgoaziou.fr> <5471C038.4080102@free.fr> <873899503j.fsf@nicolasgoaziou.fr> <8738997sa2.fsf@gmx.us> <87ppcd3iqj.fsf@nicolasgoaziou.fr> <87vbm56b2q.fsf@gmx.us> <878uj139k1.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57503) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xsf72-0002Kn-4p for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 16:54:38 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xsf6w-00067k-2o for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 16:54:32 -0500 Received: from mout.gmx.net ([212.227.17.20]:60397) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xsf6v-00067W-PG for emacs-orgmode@gnu.org; Sun, 23 Nov 2014 16:54:26 -0500 Received: from W530 ([37.135.96.168]) by mail.gmx.com (mrgmx103) with ESMTPSA (Nemesis) id 0M1FAK-1YCXPK0M1o-00t9DV for ; Sun, 23 Nov 2014 22:54:22 +0100 In-Reply-To: <878uj139k1.fsf@nicolasgoaziou.fr> (Nicolas Goaziou's message of "Sun, 23 Nov 2014 22:13:02 +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: emacs-orgmode@gnu.org Hi, Nicolas Goaziou writes: >> Still, I think overload M-RET is more intuitive, > > "Intuitiveness" is in the eye of the beholder... Clearly. > Maybe some users will not find intuitive that M-RET usually inserts a > headline... unless it is in a plain list, in which case it inserts an > item... oh wait, if it is at a keyword it can duplicate it... but, > wait, it doesn't happen for every keyword... ah! and in source blocks > it... Not to forget tables. . . >> but I fear our opinions will fail to converge. > > If you want to convince me, show me that this binding makes Org simpler > to use, or, at least, equally simple. Until then, I stand on my ground. This is a Sisyphean task. Even if a number of participants of this ML would chime in, we would still not know whether it would confuse or benefit new users. >From my point of view, we can make every function tied to M-RET beyond `org-insert-headline' configurable and turned off by default. This may, however, also add confusion ("why did M-RET work in X's Org but not in mine..."). At this point, I doubt I can add novel, useful inputs to the discussion. Cheers, Rasmus -- And I faced endless streams of vendor-approved Ikea furniture. . .