From: Jorge <jorge13515@gmail.com>
To: org mode <emacs-orgmode@gnu.org>
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: Sun, 2 Oct 2016 16:40:16 -0300 [thread overview]
Message-ID: <CAJR3QneT1XYmVjEbmFyAt0nm6w3zwb4b8Pv9rXDt3em9KfHd2g@mail.gmail.com> (raw)
In-Reply-To: <87bmz3wvbi.fsf@nicolasgoaziou.fr>
On 1 October 2016 at 19:36, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> In this case, both "parent" and "grandparent" are confusing terms.
> I made a change to M-RET docstring, hopefully eschewing the confusion.
> Please let me know if there is still something wrong there.
It is good now, but I still have some questions and observations:
First, there is some undocumented behavior if M-RET is called in the headline
after column 0 but before the headline text (e.g. if point is on the priority
cookie). It then splits the heading just before the PROPERTIES drawer. But I
don’t know if this is worthy of documentation.
Now something which I do consider worthy of description:
This forces the insertion of a heading after the current subtree,
independently on the location of point.
At least in Org version 8.3.6 (8.3.6-4-g4835be-elpaplus @
/home/jorge/.emacs.d/elpa/org-plus-contrib-20160926/), the new subtree is
positioned /before/ the current one if M-RET (even C-u M-RET) is invoked at
column 0 in the headline. You could change the text to
This forces the insertion of a heading after the current subtree,
for any position of point except at column 0 in the headline.
Or you could change the code to remove this non-uniform behavior at column 0 of
the headline.
Now a very small detail:
With double \\[universal-argument] \\[universal-argument] prefix
A “double \\[universal-argument] \\[universal-argument]” could be interpreted
as C-u C-u C-u C-u. I think it would be better to say just
With a \\[universal-argument] \\[universal-argument] prefix
--
• I am Brazilian. I hope my English is correct and I welcome corrections.
• Please adopt free formats like PDF, ODF, Org, LaTeX, Opus, WebM and 7z.
• Free (as in free speech) software for Android: https://f-droid.org/
next prev parent reply other threads:[~2016-10-02 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-29 18:36 Bug: Several small documentation problems [8.3.6 (8.3.6-4-g4835be-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20160926/)] Jorge
2016-09-29 20:36 ` Nicolas Goaziou
2016-09-30 13:36 ` Jorge
2016-10-01 22:36 ` Nicolas Goaziou
2016-10-02 19:40 ` Jorge [this message]
2016-10-04 10:03 ` Nicolas Goaziou
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJR3QneT1XYmVjEbmFyAt0nm6w3zwb4b8Pv9rXDt3em9KfHd2g@mail.gmail.com \
--to=jorge13515@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).