From mboxrd@z Thu Jan  1 00:00:00 1970
From: Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: org-capture and blank lines
Date: Fri, 3 Sep 2010 08:00:43 +0200
Message-ID: <8DEE7E6B-DD11-41A0-9FE5-2CFD73EB33E3@gmail.com>
References: <AANLkTik3_0JW3XOJabw2mUWsUJmOBX_0FQ1apzkY22PK@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v936)
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from [140.186.70.92] (port=58550 helo=eggs.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1OrPKQ-0007aN-HI
	for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 02:00:47 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69)
	(envelope-from <carsten.dominik@gmail.com>) id 1OrPKP-0006gm-IE
	for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 02:00:46 -0400
Received: from imap.science.uva.nl ([146.50.4.51]:48827)
	by eggs.gnu.org with esmtp (Exim 4.69)
	(envelope-from <carsten.dominik@gmail.com>) id 1OrPKP-0006gX-5w
	for emacs-orgmode@gnu.org; Fri, 03 Sep 2010 02:00:45 -0400
In-Reply-To: <AANLkTik3_0JW3XOJabw2mUWsUJmOBX_0FQ1apzkY22PK@mail.gmail.com>
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <http://lists.gnu.org/mailman/listinfo/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: <http://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
To: Samuel Wales <samologist@gmail.com>
Cc: emacs-orgmode@gnu.org


On Sep 3, 2010, at 5:48 AM, Samuel Wales wrote:

> Hi Carsten,
>
> Thanks for org-capture.  It is superb.
>
> I think I have only been able to find one suggestion for it.
> Currently, cancelling leaves a blank line.  Maybe there is a way to
> fix that?  Do I need to provide details?


Hi Samuel,

this is not easy to fix.  I need to insert one empty line to
make sure that the user does not by accident remove the final newline
and in this way deactivate the following headline.

Then, at kill time, when I am cleaning up, it is hard to tell if there
was an empty line originally....

So the current procedure is safer and I will keep it like this.

>
> It is also tempting to make (kill-buffer nil) ask you if you want to
> cancel the capture.

How do you call (kill-buffer nil) ?

If you have a special key for this, you can bind it in
org-capture-mode-map to org-capture-kill.  If you are using the  
interactive
version of `kill-buffer', I don't think it is a good idea to change  
this because
users will expect the buffer name prompt at that point.

- Carsten