emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Miguel Morin <blind.pew@cantab.net>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: refiling gobbles a newline and absorbs the next heading [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Thu, 09 Jan 2020 07:54:01 +0000	[thread overview]
Message-ID: <m2imll6p5y.fsf@cantab.net> (raw)
In-Reply-To: <87sgkxwk7i.fsf@nicolasgoaziou.fr>


I put "refiling" in the title as that is the moment when things go awry, so I noticed it when I refiled items.

I updated Org to 9.3.1 and confirm that the bug is still present. Because I got some compatibility problems, I tested it with `emacs -q`, in which I didn't have email, and then drafted the email after reverting to the built-in 9.1.9.

Below is the relevant part to reproduce the bug. What do you mean by ECM? Error Correction Mode? Engineering Change Management?



Start a file at `~/test.org` with:

* heading 1

* heading 2
* heading 3

Set this capture template:

(setq org-capture-templates
      '(("t" "Todo" entry (file+headline "~/test.org" "heading 1")
	 "* TODO %?\n")))

add a capture item, delete newlines from the end of the org-capture buffer, and refile to "heading 3". The heading next to the refiled item is gobbled and both the org-capture item and the gobbled "heading 2" move to "heading 3".

[![Empty lines method, step 1 - create an org-capture item][1]][1]

[![Empty lines method, step 2 - delete lines from end of org-capture buffer][2]][2]

[![Empty lines method, step 3 - refile][3]][3]

  [1]: https://i.stack.imgur.com/6cUlo.png
  [2]: https://i.stack.imgur.com/GPwg8.png
  [3]: https://i.stack.imgur.com/tzAJI.png

On Thu, 02 Jan 2020 at 22:46 WET, Nicolas Goaziou wrote:

> Hello,
> Miguel Morin <blind.pew@cantab.net> writes:
>> TL;DR: starting a capture item and deleting the new lines at the end
>> of the capture buffer gobbles the next heading, and refiling moves the
>> gobbled heading along with the new capture item.
> I'm confused. Your bug title is about refiling, yet, all your message is
> about setting up capture in various ways.
> Could you update Org (Org 9.3.1 has been released last week) and try
> again? Also, could you provide an ECM demonstrating how to reproduce the
> issue in a simple way, not necessarily how you tried to work around
> it ? :)
> Thank you.
> Regards,

  reply	other threads:[~2020-01-09  7:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-01 23:12 Bug: refiling gobbles a newline and absorbs the next heading [9.1.9 (release_9.1.9-65-g5e4542 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Miguel Morin
2020-01-02 22:46 ` Nicolas Goaziou
2020-01-09  7:54   ` Miguel Morin [this message]
2020-01-09 16:40     ` Nicolas Goaziou
2020-01-09 22:11       ` Miguel Morin
2020-01-11 15:58         ` Nicolas Goaziou
2020-01-11 20:13           ` Samuel Wales
2020-01-12  7:55           ` Miguel Morin
2020-02-11 11:38     ` Bastien
2020-02-14 22:22       ` Miguel Morin
2020-02-16 10:32         ` Bastien
2020-02-05  6:30 ` Bastien
2020-02-11 15:34   ` Miguel Morin
2020-02-11 16:44     ` Bastien

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:

  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=m2imll6p5y.fsf@cantab.net \
    --to=blind.pew@cantab.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \


* 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


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).