From mboxrd@z Thu Jan  1 00:00:00 1970
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
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
Message-ID: <877ehqt9zz.fsf@nicolasgoaziou.fr>
References: <871s7zmdws.fsf@seas.upenn.edu>
Mime-Version: 1.0
Content-Type: text/plain
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:38351)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1gK4lp-00075I-Ef
	for emacs-orgmode@gnu.org; Tue, 06 Nov 2018 12:04:09 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <mail@nicolasgoaziou.fr>) id 1gK4le-00041D-LQ
	for emacs-orgmode@gnu.org; Tue, 06 Nov 2018 12:04:02 -0500
Received: from relay12.mail.gandi.net ([217.70.178.232]:59193)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32)
	(Exim 4.71) (envelope-from <mail@nicolasgoaziou.fr>)
	id 1gK4lb-0000k4-18
	for emacs-orgmode@gnu.org; Tue, 06 Nov 2018 12:03:54 -0500
In-Reply-To: <871s7zmdws.fsf@seas.upenn.edu> (Calvin Beck's message of "Mon,
	05 Nov 2018 16:07:31 -0500")
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Calvin Beck <hobbes@seas.upenn.edu>
Cc: emacs-orgmode@gnu.org

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