From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Heerdegen Subject: Re: Emacs bug 37890; killing capture buffer Date: Fri, 20 Dec 2019 01:17:32 +0100 Message-ID: <87zhfn3l5v.fsf@web.de> References: <87r217lwwz.fsf@web.de> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:46678) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ii5z5-0004Y8-Ui for emacs-orgmode@gnu.org; Thu, 19 Dec 2019 19:17:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ii5z4-0005El-Og for emacs-orgmode@gnu.org; Thu, 19 Dec 2019 19:17:35 -0500 Received: from mout.web.de ([212.227.15.4]:41171) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ii5z4-00056Y-AP for emacs-orgmode@gnu.org; Thu, 19 Dec 2019 19:17:34 -0500 In-Reply-To: (Samuel Wales's message of "Tue, 17 Dec 2019 17:07:35 -0700") 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: Samuel Wales Cc: emacs-orgmode@gnu.org Samuel Wales writes: > the indirect buffer capture mechanism was to be an improvement on > remember.el, and replaced it. you might still be able to find > remember.el if you prefer the separate file idea. I find it acceptable once it's been made more secure (e.g. by using hooks like I mentioned). But I wonder now why you said there are still problems with final newlines (and you already got a confirmation), while I and other developers say it has been fixed. Do you use the org mode version built in Emacs, and you don't use Emacs master? Thanks, Michael.