emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: Nicolas Goaziou <mail@nicolasgoaziou.fr>
Cc: emacs-orgmode@gnu.org
Subject: Re: [feature request] A new cookie type [!] showing the last note taken
Date: Sat, 05 Sep 2020 13:52:20 +0800	[thread overview]
Message-ID: <871rjgahyj.fsf@localhost> (raw)
In-Reply-To: <87sgbzw77n.fsf@nicolasgoaziou.fr>

> However, writing an item
> with a line break at the end of its first line is not necessarily
> a note.

You are right. I missed that \\ is also a newline for LaTeX export.

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

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).

What do you think?

Best,
Ihor

Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:

> Hello,
>
> Ihor Radchenko <yantar92@gmail.com> writes:
>
>> I may miss something, but it does not look [for me] any more specific
>> in comparison with headline format:
>>
>> - headline :: "^\*+ .+$"
>> - first line of note :: "^[ \t]*-.+\\\\$"
>
> I do see a big difference, tho. Starting a line with an asterisk
> followed by a space _always_ create a headline. However, writing an item
> with a line break at the end of its first line is not necessarily
> a note.
>
>   - Question.\\
>     Why would this be a note?
>
>   - Answer.\\
>     It isn't.
>
> So, suggested syntax is too ambiguous.
>
> Regards,
> -- 
> Nicolas Goaziou


  reply	other threads:[~2020-09-05  5:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-29  6:40 [feature request] A new cookie type [!] showing the last note taken 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 [this message]
2020-09-09 14:00                     ` Nicolas Goaziou
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 \
    --in-reply-to=871rjgahyj.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \
    /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).