From: Bastien <bzg@gnu.org>
To: James Harkins <jamshark70@gmail.com>
Cc: jamshark70@dewdrop-world.net, Emacs-orgmode@gnu.org
Subject: Re: Bug: org-insert-heading-respect-content inserts at the wrong level if target heading is invisible [7.9.2 (release_7.9.2-883-g6fb36e.dirty @ /home/dlm/share/org-mode.git/lisp/)]
Date: Thu, 11 Apr 2013 01:06:27 +0200 [thread overview]
Message-ID: <87fvyy0yvg.fsf@bzg.ath.cx> (raw)
In-Reply-To: <CAFniQ7U4hpsMj9KfOaH86p-9aVGWApcOEjqJpRR=zWHsb2cGTQ@mail.gmail.com> (James Harkins's message of "Wed, 13 Mar 2013 17:03:26 +0800")
Hi James,
James Harkins <jamshark70@gmail.com> writes:
> On Tue, Mar 5, 2013 at 1:41 AM, Bastien <bzg@gnu.org> wrote:
>> There is some obscure issues here... I fixed various things in
>> `org-insert-heading' in master, but inserting in invisible parts of
>> the subtree is still unstable. So I went and used the workaround you
>> suggested (i.e. org-show-subtree) in the maint branch, so that it will
>> be in 7.9.4.
>
> Apologies -- this seems to be the issue that wouldn't die -- but I
> have to report another failure with this.
Thanks for the detailed report -- I pushed a fix.
I used (org-insert-heading-respect-content '(16) t) so that new
headings are added at the end of the parent subtree.
Can you confirm it works fine for you?
Thanks,
--
Bastien
prev parent reply other threads:[~2013-04-10 23:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 4:46 Bug: org-insert-heading-respect-content inserts at the wrong level if target heading is invisible [7.9.2 (release_7.9.2-883-g6fb36e.dirty @ /home/dlm/share/org-mode.git/lisp/)] James Harkins
2013-02-11 17:30 ` Bastien
2013-02-12 3:50 ` James Harkins
2013-02-12 10:34 ` Bastien
2013-02-14 9:09 ` Bastien
[not found] ` <CAFniQ7XpJnqOW8DqdGLJ1RbtPtrnKQz=zXBH-O0M1ZFPBa5ucw@mail.gmail.com>
[not found] ` <87mwujdp87.fsf@bzg.ath.cx>
2013-03-13 9:03 ` James Harkins
2013-04-10 23:06 ` Bastien [this message]
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=87fvyy0yvg.fsf@bzg.ath.cx \
--to=bzg@gnu.org \
--cc=Emacs-orgmode@gnu.org \
--cc=jamshark70@dewdrop-world.net \
--cc=jamshark70@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).