all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Calvin Beck <hobbes@seas.upenn.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Capture problems with newlines [9.1.14 (9.1.14-9-g131531-elpa @ /home/calvin/.emacs.d/elpa/org-20181105/)]
Date: Tue, 06 Nov 2018 18:02:24 +0100	[thread overview]
Message-ID: <877ehqt9zz.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <871s7zmdws.fsf@seas.upenn.edu> (Calvin Beck's message of "Mon, 05 Nov 2018 16:07:31 -0500")

Hello,

Calvin Beck <hobbes@seas.upenn.edu> writes:

> I have this problem where I have a capture template like this:
>
>> ("t" "Todo" entry (file+headline "~/org/todo.org" "Tasks")
>>    "* TODO %?\n   SCHEDULED: %t\n   %a\n")
>
> And then if I have another heading under Tasks...
>
>> * Tasks
>> * HEADING2
>
> Then when capturing a todo entry, if I delete the last line I get something like...
>
>> * Tasks
>> ** TODO
>>    SCHEDULED: <2018-11-05 Mon>
>>    link* HEADING2
>
> And similarly, if I edit the last line in the capture template I get...
>
>> * Tasks
>> ** TODO
>>    SCHEDULED: <2018-11-05 Mon>
>>    link
>> the stuff that I added at the end of my capture template* HEADING2
>
> This is counter intuitive, as you expect the capture to be isolated from
> the other headings. Additionally, it's not obvious that you are messing
> up other headings when you are using org-capture, so you can end up
> losing tasks and headings, which seems like a very bad behaviour!

Could you test again with development version? I think it was fixed
recently.

Regards,

-- 
Nicolas Goaziou

  reply	other threads:[~2018-11-06 17:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-05 21:07 Bug: Capture problems with newlines [9.1.14 (9.1.14-9-g131531-elpa @ /home/calvin/.emacs.d/elpa/org-20181105/)] Calvin Beck
2018-11-06 17:02 ` Nicolas Goaziou [this message]
2018-11-14 14:56   ` hobbes

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877ehqt9zz.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=hobbes@seas.upenn.edu \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.