emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jay Dresser <jay@jaydresser.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: superflous blank line in capture
Date: Tue, 23 May 2017 18:18:02 +0200	[thread overview]
Message-ID: <87a863eedh.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <87lgq3ykwh.fsf@jaydresser.us> (Jay Dresser's message of "Wed, 10 May 2017 23:20:30 -0700")

Hello,

Jay Dresser <jay@jaydresser.us> writes:

> A little bug in capture I think.
>
> I am using this template:
>
> ("a" "Add Nag" entry (file+headline "~/Org/jay.org" "Nags") "* %?\nSCHEDULED: %T\nDEADLINE: %T\n:PROPERTIES:\n:CATEGORY: Urgent\n:APPT_WARNTIME: 10m\n:END:" :prepend t)
>
> This behaves correctly. If I am near the destination before I invoke, I
> can see that it inserts as shown but with a blank line after the ":END:"
> line. After I finish with C-c C-c, that blank line goes away.
>
> However when I use this template:
>
> ("a" "Add Nag" entry (file+headline "~/Org/jay.org" "Nags") "* %?\nSCHEDULED: %T\nDEADLINE: %T\n:PROPERTIES:\n:CATEGORY: Urgent\n:APPT_WARNTIME: 10m\n:END:" :prepend t :unnarrowed t)
>
> It also inserts the blank line, but when I finish with C-c C-c the blank
> line remains. I assume that the behavior should not be different in this
> way just because of the narrowing.

It should be fixed in maint branch. Could you confirm it?

Regards,

-- 
Nicolas Goaziou

      reply	other threads:[~2017-05-23 16:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-09 14:46 org-capture datetree below heading? Benedikt Steindorf
2017-05-10  6:39 ` Carsten Dominik
2017-05-11  6:20 ` superflous blank line in capture Jay Dresser
2017-05-23 16:18   ` Nicolas Goaziou [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87a863eedh.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=emacs-orgmode@gnu.org \
    --cc=jay@jaydresser.us \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).