From: Richard Lawrence <wyley.r@gmail.com>
To: Samuel Wales <samologist@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: newline or no newline at end of capture: expected behavior
Date: Sun, 27 Sep 2020 09:16:33 +0200 [thread overview]
Message-ID: <878scvbsfi.fsf@aquinas> (raw)
In-Reply-To: <CAJcAo8spnYTZ25kn15Z+A3RarcVAGH75n8TBYjKxih8on=a1FQ@mail.gmail.com>
Hi Samuel,
> On 9/23/20, Samuel Wales <samologist@gmail.com> wrote:
>> i have the same question for headline-only capture
>> buffers. i.e. what is the expected result with and without trailing
>> newline.
Just to clarify: are you aware of the :empty-lines, :empty-lines-before
and :empty-lines-after keys that you can set in org-capture-templates?
Are your questions about the default values of these keys?
I just tried a simple setup in emacs -Q with Org 9.4, namely:
(setq org-capture-templates
'(("s" "simple" entry (file+headline "~/org/notes.org" "Foo")
"* %?" :empty-lines 1)))
and Org seems to correctly respect the value of these keys when they are
specified explicitly. That is, with :empty-lines 0, no newlines are
added; with :empty-lines 1, a blank line appears on each side of the
captured entry; with :empty-lines-after 1, a blank line appears after,
but not before, the new entry; and so on.
Can you use these keys to get the behavior you are looking for? Or is
your question about something else?
--
Best,
Richard
next prev parent reply other threads:[~2020-09-27 7:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-20 5:29 newline or no newline at end of capture: expected behavior Samuel Wales
2020-09-20 5:36 ` Samuel Wales
2020-09-23 7:24 ` Bastien
2020-09-23 21:29 ` Samuel Wales
2020-09-23 21:30 ` Samuel Wales
2020-09-27 4:13 ` Samuel Wales
2020-09-27 7:16 ` Richard Lawrence [this message]
2020-09-27 7:42 ` Samuel Wales
2020-09-27 10:39 ` Nicolas Goaziou
2020-09-27 21:07 ` Samuel Wales
2020-09-27 21:08 ` Samuel Wales
2020-09-28 2:31 ` Samuel Wales
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=878scvbsfi.fsf@aquinas \
--to=wyley.r@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=samologist@gmail.com \
/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).