From: Tim Cross <theophilusx@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Re: [BUG] Adding note to heading without newline at the end
Date: Tue, 21 Jun 2022 21:13:56 +1000 [thread overview]
Message-ID: <87pmj2p8n5.fsf@gmail.com> (raw)
In-Reply-To: <m21qvi8er5.fsf@ntnu.no>
Tor Kringeland <tor.kringeland@ntnu.no> writes:
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> Aha. Not saving is an important piece of information.
>> (said the person with compulsive saving syndrome)
>
> Thanks! This fixes the bug (which was present in both Org 9.5 and 9.6)
> for me. However, my original bug, which is only present in Org 9.6, is
> still there. Do the same thing but set org-log-into-drawer to t. Then
>
> #+begin_example
> * test<POINT>
> #+end_example
>
>
> becomes
>
> #+begin_example
> * tes
> :LOGBOOK:
> - Note taken on [2022-06-21 Tue 12:55]
> :END:
> t<POINT>
> #+end_example
>
> This bug also only happens if there is no trailing newline in the
> buffer.
Not sure if this makes any difference wrt your bug, but wanted to point
out that your test example block is non-conforming. If you have a line
starting with an '*', you have ot proceed it with a comma to escape the
meaning of the start. If you use org-edit-special to edit the block
contents, the escaping is done for you automatically. Running org-lint
is also useful when you think you might have a bug as it will ensure you
have a relatively clean and correct input file.
next prev parent reply other threads:[~2022-06-21 11:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 0:27 [BUG] Adding note to heading without newline at the end Tor Kringeland
2022-06-20 13:41 ` Ihor Radchenko
2022-06-20 15:11 ` Tor Kringeland
2022-06-21 2:24 ` [PATCH] " Ihor Radchenko
2022-06-21 10:58 ` Tor Kringeland
2022-06-21 11:13 ` Tim Cross [this message]
2022-06-21 11:38 ` Ihor Radchenko
2022-06-22 14:28 ` Tor Kringeland
2022-06-23 15:59 ` Samuel Banya
2022-06-26 23:32 ` Samuel Banya
2022-06-26 23:45 ` Ihor Radchenko
2022-06-27 2:42 ` Samuel Banya
2022-06-27 10:18 ` Ihor Radchenko
2022-06-28 2:47 ` Samuel Banya
2022-06-28 2:57 ` Ihor Radchenko
2022-09-13 14:13 ` Ihor Radchenko
2022-06-21 1:56 ` Samuel Banya
2022-06-21 2:21 ` Tor Kringeland
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=87pmj2p8n5.fsf@gmail.com \
--to=theophilusx@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).