emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: John Hendy <jw.hendy@gmail.com>
To: Erik Iverson <erikriverson@gmail.com>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: possible org-insert-heading bug?
Date: Tue, 2 Jul 2013 17:11:01 -0500	[thread overview]
Message-ID: <CA+M2ft_CmhTTY12s_2FRe3=aGm76ow77qSZaTaO7fVR-LZz_cw@mail.gmail.com> (raw)
In-Reply-To: <CAKzGw13JcY_vWue2d6jHLjBzkU3JEK8=JmUXQfBKpRKx-VH4hQ@mail.gmail.com>

Hi Erik,


Glad to see you around :)

These all may be quite related. I haven't seen activity on those
threads suggesting whether a) the documentation is, in fact, right or
wrong or b) whether anyone has taken action to fix or adjust the
behavior of M-RET or C-RET based on the complaints/counter-intuitive
observations.

Let me know if those are similar to your issue. Perhaps Bastien can
comment on the state of these thread, now at least four in number...

- http://www.mail-archive.com/emacs-orgmode@gnu.org/msg70718.html
- http://osdir.com/ml/emacs-orgmode-gnu/2013-05/msg00846.html
- http://permalink.gmane.org/gmane.emacs.orgmode/72399

I've taken to using C-RET in the meantime, as it seems to do what I
often expect when reflexively pressing M-RET. Also, someone once
corrected me on the documentation that "at the end of the line" might
mean before the ellipsis, not after?


Hope that helps!
John


On Tue, Jul 2, 2013 at 1:53 PM, Erik Iverson <erikriverson@gmail.com> wrote:
> Hello,
>
> I am using a current git pull (Org-mode version 8.0.3,
> release_8.0.3-345-g239aa7) and noticed behavior that's easiest to show
> with a small example. If you save and visit the following org file,
>
> https://dl.dropboxusercontent.com/u/7514404/test.org
>
> you will see the behavior described and documented (assuming it's
> reproducible under your version of emacs and orgmode).
>
> Briefly M-<RET> at the end of a *folded* headline that contains plain
> list items will insert a new plain list item at the end of the
> subtree, instead of a new top-level headline. I believe this conflicts
> with the documentation for M-<RET>, which currently reads:
>
> ... If the command is used at the end of a folded subtree (i.e.,
> behind the ellipses at the end of a headline), then a headline like
> the current one will be inserted after the end of the subtree...
>
> Best,
> --Erik
>

  reply	other threads:[~2013-07-02 22:11 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-02 18:53 possible org-insert-heading bug? Erik Iverson
2013-07-02 22:11 ` John Hendy [this message]
2013-07-03  3:52   ` Carsten Dominik
2013-07-03 15:01     ` Robert Horn
2013-07-03 15:06       ` Erik Iverson
2013-07-03 15:39         ` Robert Horn
2013-07-31 19:15     ` Simon Thum
2013-08-02 14:34       ` Bastien
2013-08-08  7:28       ` Carsten Dominik
2013-08-08 20:17         ` Simon Thum

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='CA+M2ft_CmhTTY12s_2FRe3=aGm76ow77qSZaTaO7fVR-LZz_cw@mail.gmail.com' \
    --to=jw.hendy@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=erikriverson@gmail.com \
    /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).