From: Nicolas Goaziou <firstname.lastname@example.org> To: Ihor Radchenko <email@example.com> Cc: firstname.lastname@example.org Subject: Re: [feature request] A new cookie type [!] showing the last note taken Date: Wed, 09 Sep 2020 16:00:14 +0200 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <871rjgahyj.fsf@localhost> (Ihor Radchenko's message of "Sat, 05 Sep 2020 13:52:20 +0800") Hello, Ihor Radchenko <firstname.lastname@example.org> writes: > You are right. I missed that \\ is also a newline for LaTeX export. It is a line break in any export back-end. > Another possibility is re-purposing counter definition from ordered > lists. Currently the "\\[@[0-9]+\\]" is used to force item number in > ordered lists: > > 1. item > 5. [@5] another item > 6. next item > > However, it is unused it unordered lists. We might define a note as a > unnumbered list item with [@note]: > > - [@note] This is note That's a reasonable syntax extension, maybe too English-centered. Maybe a more abstract [@!] would be better. > In addition, all the list items in :LOGBOOK: drawer may be considered > notes (to avoid a need to change the current format of the > automatically added notes). Notes are not necessary stuffed into a LOGBOOK drawer, or even into a drawer at all. Besides, LOGBOOK is a common word, and it is not unreasonable to think some user could have used it for other purposes. Old notes are going to be incompatible (as in ignored by any tool processing notes, not invalid markup) with the new ones. I don't think there's a way to eschew it. It doesn't seem to be a big deal, however, as you don't lose anything by keeping notes in old syntax around. Regards, -- Nicolas Goaziou
next prev parent reply other threads:[~2020-09-09 14:01 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-08-29 6:40 Ihor Radchenko 2020-08-30 8:50 ` Nicolas Goaziou 2020-08-30 10:40 ` Ihor Radchenko 2020-08-30 11:03 ` Nicolas Goaziou 2020-08-30 12:18 ` Ihor Radchenko 2020-08-30 12:57 ` Nicolas Goaziou 2020-08-30 14:58 ` Eric Abrahamsen 2020-08-31 2:26 ` Ihor Radchenko 2020-08-31 8:42 ` Julius Müller 2020-08-31 11:55 ` Ihor Radchenko 2020-08-31 14:58 ` Nicolas Goaziou 2020-09-02 2:02 ` Ihor Radchenko 2020-09-03 9:16 ` Nicolas Goaziou 2020-09-05 5:52 ` Ihor Radchenko 2020-09-09 14:00 ` Nicolas Goaziou [this message] 2020-09-10 9:24 ` Ihor Radchenko 2020-09-13 13:09 ` Nicolas Goaziou 2020-09-14 19:49 ` Eric Abrahamsen 2020-09-05 22:14 ` Allen Li 2020-09-06 1:23 ` Ihor Radchenko 2020-09-06 18:16 ` Eric Abrahamsen 2021-01-17 15:38 ` Christopher Miles 2021-01-18 2:07 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [feature request] A new cookie type ['\!'] showing the last note taken' \ /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
Code repositories for project(s) associated with this 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).