From mboxrd@z Thu Jan 1 00:00:00 1970 From: "" Subject: Re: Bug: Capture problems with newlines [9.1.14 (9.1.14-9-g131531-elpa @ /home/calvin/.emacs.d/elpa/org-20181105/)] Date: Wed, 14 Nov 2018 09:56:58 -0500 Message-ID: <87k1lfg11h.fsf@seas.upenn.edu> References: <871s7zmdws.fsf@seas.upenn.edu> <877ehqt9zz.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45309) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMwbI-00008S-T9 for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 09:57:05 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMwbI-00064c-4F for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 09:57:04 -0500 Received: from mail-qk1-x733.google.com ([2607:f8b0:4864:20::733]:36016) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gMwbH-00061n-Ug for emacs-orgmode@gnu.org; Wed, 14 Nov 2018 09:57:04 -0500 Received: by mail-qk1-x733.google.com with SMTP id o125so26196568qkf.3 for ; Wed, 14 Nov 2018 06:57:02 -0800 (PST) In-reply-to: <877ehqt9zz.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Nicolas Goaziou Cc: emacs-orgmode@gnu.org 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 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, --