From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Igor Perepelytsya <igorquail@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Using org-capture with a template adds an unnecessary newline regardless of flags set [9.0.5 (9.0.5-elpa @ /home/igor/.emacs.d/elpa/org-20170210/)]
Date: Tue, 23 May 2017 18:17:33 +0200 [thread overview]
Message-ID: <87efvfeeea.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAHyu4JcdiN3idd5w1vYLsmaFKVBi5aRzg9c8MFbD0diOisNjGA@mail.gmail.com> (Igor Perepelytsya's message of "Sat, 15 Apr 2017 05:57:01 -0400")
Hello,
Igor Perepelytsya <igorquail@gmail.com> writes:
> Using a template with org-capture to create a new org entry will add an
> unwanted newline after it. This occurs regardless of the contents of the
> template file, whether or not the 'empty-lines 1' / 'empty-lines-after
> 1' checkboxes are ticked in org-customize, or `empty-lines` /
> `empty-lines-after` keys are set to 0 manually. I expected that there
> would be no newline added by default after a template is inserted into
> an org-capture buffer.
>
> This appears to happen because
> `org-capture-place-(entry/plain-text/etc)` defuns in org-capture.el have
> `(org-capture-empty-lines-after 1)` in them by default. Changing this to
> `(org-capture-empty-lines-after)` and byte-compiling the file fixes the
> issue. I am not aware of any reason for 1 to be the default forced value
> here.
>
> Emacs : GNU Emacs 25.1.1 (x86_64-unknown-linux-gnu, GTK+ Version 2.24.30)
> of 2016-09-24
> Package: Org mode version 9.0.5 (9.0.5-elpa @
> /home/igor/.emacs.d/elpa/org-20170210/)
I think I fixed it. Could you confirm it?
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2017-05-23 16:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-15 9:57 Bug: Using org-capture with a template adds an unnecessary newline regardless of flags set [9.0.5 (9.0.5-elpa @ /home/igor/.emacs.d/elpa/org-20170210/)] Igor Perepelytsya
2017-04-17 9:31 ` Nicolas Goaziou
2017-05-23 16:17 ` 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=87efvfeeea.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=igorquail@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).