From: "E.L.K." <email@example.com>
Subject: Re: [patch] When inserting entry template, don't include last newline in narrowed zone
Date: Sun, 28 Jun 2020 14:17:16 +0300 [thread overview]
Message-ID: <CAF+cOoP9D6zkTi+RrssSeO5bx1YC5wUeBYiYYrL1vSH2-Au0Hw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 789 bytes --]
Just found an issue with this patch: if I try to schedule the item,
SCHEDULED and timestamp get inserted into invisible area.
On Sun, Jun 28, 2020 at 1:14 PM E.L.K. <firstname.lastname@example.org> wrote:
> Org 9.3.6: when inserting the entry by capture mechanics, it narrows
> buffer in a way that cursor can be moved to the last line, which is the
> beginning of next (non-capture template) line in the original unnarowed
> So this allows to: start capture, move point to the very last char of the
> narrowed buffer, insert something. If this line in unnarowed buffer was
> start of heading, it breaks structure of document.
> This is patch in attempt to fix it. I followed same approach as in
> org-capture-place-item function.
[-- Attachment #2: Type: text/html, Size: 1259 bytes --]
next prev parent reply other threads:[~2020-06-28 11:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-28 10:14 [patch] When inserting entry template, don't include last newline in narrowed zone E.L.K.
2020-06-28 11:17 ` E.L.K. [this message]
2020-06-28 16:28 ` Kyle Meyer
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).