emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carlos Pita <carlosjosepita@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Newlines in capture templates
Date: Wed, 03 Sep 2014 16:24:41 -0300	[thread overview]
Message-ID: <87vbp4wlqe.fsf@gmail.com> (raw)
In-Reply-To: <871trs660d.fsf@gmail.com> (Carlos Pita's message of "Wed, 03 Sep 2014 13:08:50 -0300")

Well, I've figured it out myself, it wasn't that hard. Here it is in
case someone else comes here looking for an answer in the future:

C-h v org-capture-templates:

[...]

 :empty-lines        Set this to the number of lines the should be inserted
                     before and after the new item.  Default 0, only common
                     other value is 1.

 :empty-lines-before Set this to the number of lines the should be inserted
                     before the new item.  Overrides :empty-lines for the
                     number lines inserted before.

 :empty-lines-after  Set this to the number of lines the should be inserted
                     after the new item.  Overrides :empty-lines for the
                     number of lines inserted after.


Cheers
--
Carlos

Carlos Pita <carlosjosepita@gmail.com> writes:

> Hi all,
>
> I would like to separate the items in my capture files by a number of
> newlines, as in:
>
> 	** item 1
>
>     content 1
>
>     ** item 2
>
>     content 2
>
> 	** item 3
> 	
> 	content 3
> 	
> instead of:
>
> 	** item 1
> 	
> 	content 1
> 	** item 2
> 	
> 	content 2
> 	** item 3
> 	
> 	content 3
> 	
> But org is removing the heading and trailing \n from my templates. Is
> there any way to avoid this, or to command org to automatically include
> newlines between captures?
>
> Thank you in advance
> --
> Carlos

      reply	other threads:[~2014-09-03 19:25 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-03 16:08 Newlines in capture templates Carlos Pita
2014-09-03 19:24 ` Carlos Pita [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=87vbp4wlqe.fsf@gmail.com \
    --to=carlosjosepita@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).