From: Richard Walker <walkerrichardj@gmail.com>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: org-datetree-insert-line and org-blank-before-new-entry
Date: Wed, 1 Sep 2021 10:35:17 +1000 [thread overview]
Message-ID: <CAFyNgSE4mAt+b0Ks8L9bg2LbHcXnayOh+bYyONTQ4jN+zx3C1w@mail.gmail.com> (raw)
A follow-up to the changes made to org-datetree-insert-line
in September 2020.
The definition now begins:
(defun org-datetree-insert-line (year &optional month day text)
(delete-region (save-excursion (skip-chars-backward " \t\n") (point)) (point))
(when (assq 'heading org-blank-before-new-entry)
(insert "\n"))
...
I'm getting blank lines inserted before new entries, and
I found a couple of sources of advice for setting org-blank-before-new-entry
( https://emacs.stackexchange.com/questions/51117/org-mode-control-whether-m-ret-inserts-a-newline-or-not-for-plain-lists
and
https://stackoverflow.com/questions/28351465/emacs-orgmode-do-not-insert-line-between-headers
)
that say to do this:
(setf org-blank-before-new-entry '((heading . nil) (plain-list-item . nil)))
Such a setting seems to be consistent with the help text of
org-blank-before-new-entry, and what org--blank-before-heading-p
expects to find. But, having made this setting,
(when (assq 'heading org-blank-before-new-entry)
(insert "\n"))
still does the insertion, since (assq 'heading org-blank-before-new-entry)
is non-nil.
Change (assq 'heading org-blank-before-new-entry)
to (org--blank-before-heading-p) here?
next reply other threads:[~2021-09-01 0:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 0:35 Richard Walker [this message]
2022-10-26 7:29 ` org-datetree-insert-line and org-blank-before-new-entry Ihor Radchenko
2022-10-26 22:50 ` Richard Walker
2022-10-27 4:02 ` [PATCH] org-manual: Suggest to wait for one month and followup when reporting bugs (was: org-datetree-insert-line and org-blank-before-new-entry) Ihor Radchenko
2022-10-27 8:31 ` [PATCH] org-manual: Suggest to wait for one month and followup when reporting bugs Bastien Guerry
2022-10-29 9:41 ` Ihor Radchenko
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=CAFyNgSE4mAt+b0Ks8L9bg2LbHcXnayOh+bYyONTQ4jN+zx3C1w@mail.gmail.com \
--to=walkerrichardj@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).