From: David Masterson <dsmasterson@gmail.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: oeg-add-note and double backslash ?
Date: Wed, 06 Dec 2023 23:52:16 -0800 [thread overview]
Message-ID: <SA1P223MB0924FD6ED6F98B6B2829ED24A28BA@SA1P223MB0924.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <87il5cvjvw.fsf@localhost> (Ihor Radchenko's message of "Tue, 05 Dec 2023 13:50:11 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>>> To prevent fill-region from concatenating the auto-generated text in the
>>> first line and the user input in the following lines.
>>
>> Ah. Is that mentioned somewhere in the Org manual? I don't mean the
>> details of fill-region, but a little something to answer "why is that
>> there?" by new users.
>
> No, AFAIK, the exact format of notes is not described in the manual.
> We do not describe every single detail in the manual.
> I believe that the exact wording of the notes is not something we have
> to describe.
Hmm. glancing through the manual, there is a bit of assumption implicit
about the use of '\\'. We had the problem with Unix Shell scripts that
we would need a backslash at the end of a line to prevent the EOL as
being interpreted as end-of-input. Depending on the layers of scripting
we were using, we added backslashes after the backslash because each
layer would peel off a backslash. This is what I first thought of in
reading the manual.
Seeing '\\' at the end of the note line, I thought something would get
messed up if the EOLs (except last) in the Note were treated as
end-of-input, so I added them to all but the last line. This is what I
think needs clarification.
--
David Masterson
next prev parent reply other threads:[~2023-12-07 7:58 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-03 22:37 oeg-add-note and double backslash ? David Masterson
2023-12-04 15:10 ` Ihor Radchenko
2023-12-04 22:03 ` David Masterson
2023-12-05 1:31 ` Samuel Wales
2023-12-05 6:36 ` David Masterson
2023-12-05 13:50 ` Ihor Radchenko
2023-12-07 7:52 ` David Masterson [this message]
2023-12-07 10:44 ` Ihor Radchenko
2023-12-09 2:27 ` David Masterson
2023-12-09 11:03 ` Ihor Radchenko
2023-12-10 0:23 ` David Masterson
2023-12-10 14:57 ` Ihor Radchenko
2023-12-10 21:00 ` David Masterson
2023-12-11 13:48 ` Ihor Radchenko
2023-12-12 18:29 ` David Masterson
2023-12-13 10:34 ` Ihor Radchenko
2023-12-14 5:53 ` David Masterson
2023-12-14 13:05 ` 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=SA1P223MB0924FD6ED6F98B6B2829ED24A28BA@SA1P223MB0924.NAMP223.PROD.OUTLOOK.COM \
--to=dsmasterson@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).