From: Ihor Radchenko <yantar92@posteo.net>
To: John Wiegley <johnw@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Archiving always adds a newline before entries
Date: Sun, 22 Sep 2024 16:03:17 +0000 [thread overview]
Message-ID: <877cb3r7zu.fsf@localhost> (raw)
In-Reply-To: <m2r0aakbdl.fsf@gnu.org>
"John Wiegley" <johnw@gnu.org> writes:
> I like to avoid blank lines between Org-mode entries, but have found that when
> archiving (and not use datetrees), that this is not supported by Org-mode
> out-of-the-box. Mainly it’s due to these lines:
> ...
> ;; Subtree narrowing can let the buffer end on
> ;; a headline. `org-paste-subtree' then deletes it.
> ;; To prevent this, make sure visible part of buffer
> ;; always terminates on a new line, while limiting
> ;; number of blank lines in a date tree.
> ---> (unless (and datetree-date (bolp)) (insert "\n"))))
> ;; Paste
> (org-paste-subtree (org-get-valid-level level (and heading 1)))
>
> The line indicated above always appends a newline at the end of the buffer,
> so that the pasted tree appears after this newline. It would be nice if this
> followed the configuration of ‘org-blank-before-new-entry’, for example.
+1
Ideally, we should use something more Elisp-friendly compared to
interactive context-dependent `org-paste-subtree'.
In the current state, things are way too fragile to touch them without
risking unexpected breakage in various corner cases.
It would be nice to factor out context-sensitive handling in
`org-paste-subtree' into some kind of API function. Then, we can use
that function more safely in other places like org-archive.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
prev parent reply other threads:[~2024-09-22 16:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 1:22 Archiving always adds a newline before entries John Wiegley
2024-09-22 16:03 ` Ihor Radchenko [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=877cb3r7zu.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=johnw@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).