From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jorge Subject: Re: Bug: Several small documentation problems [8.3.6 (8.3.6-4-g4835be-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160926/)] Date: Fri, 30 Sep 2016 10:36:37 -0300 Message-ID: References: <87intexx22.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:32919) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpxzV-0003Ww-MY for emacs-orgmode@gnu.org; Fri, 30 Sep 2016 09:36:45 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpxzT-0004ON-GD for emacs-orgmode@gnu.org; Fri, 30 Sep 2016 09:36:40 -0400 Received: from mail-qk0-x22b.google.com ([2607:f8b0:400d:c09::22b]:36824) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpxzT-0004OC-9W for emacs-orgmode@gnu.org; Fri, 30 Sep 2016 09:36:39 -0400 Received: by mail-qk0-x22b.google.com with SMTP id z190so106552686qkc.3 for ; Fri, 30 Sep 2016 06:36:39 -0700 (PDT) In-Reply-To: <87intexx22.fsf@nicolasgoaziou.fr> 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" To: org mode On 29 September 2016 at 17:36, Nicolas Goaziou wro= te: > I think "grandparent" is correct. In the following document > > * H1 > ** H2 > Text<--point > > "H2" is the parent headline of "Text" and as a consequence, "H1" is its > grandparent. What if point is in the headline, which is often the case? Besides the docstring is inconsistent: With two universal prefix arguments, insert the heading at the end of the grandparent subtree. For example, if point is within a 2nd-level heading, then it will insert a 2nd-level heading at the end of the 1st-level parent heading. In the first sentence it says "grandparent subtree", whereas in the second sentence it says "parent heading". And the manual says "parent": Calling this command with `C-u C-u' will unconditionally respect the headline's content and create a new item at the end of the parent subtree. Perhaps uniformity of terminology would help here. > You are right, M-RET and C-RET are confusing, and making C-u M-RET > a duplicate of C-RET is wasting some important keybinding. This was > discussed on this ML already (with Rasmus) but led nowhere so far. > > In any case, it is more future-proof to not insist on the fact that > C-RET is C-u M-RET. I think that, whether we describe both behaviors separately or tell the user that C-RET is equivalent to C-u M-RET, the commitment (to not change the behavio= r) is the same. But if you still think that describing both separately is mor= e future-proof, I won't argue. But I still ask you to look at the other points I made about that manual section: that it doesn't adequately explain the effect of C-u M-RET, and th= at the description of C-RET is actually wrong. > Thank you for this tedious, yet very important work. Thank you very much for working on Org! --=20 =E2=80=A2 I am Brazilian. I hope my English is correct and I welcome corre= ctions. =E2=80=A2 Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM a= nd 7z. =E2=80=A2 Free (as in free speech) software for Android: https://f-droid.or= g/