Aha! Finally figured out how to get this installed over the MELPA version.
Yes, this is fixed in the development branch. I am so happy about this. I hope
this is released in a stable version soon, because right now org-capture is
really destructive otherwise.
Thanks!
Nicolas Goaziou writes:
> Hello,
>
> Calvin Beck <hob...@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,
--
