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: Fri, 08 Dec 2023 18:27:42 -0800 [thread overview]
Message-ID: <LV8P223MB0920DBA505A2D4080311CB4AA289A@LV8P223MB0920.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <8734we47i4.fsf@localhost> (Ihor Radchenko's message of "Thu, 07 Dec 2023 10:44:19 +0000")
Ihor Radchenko <yantar92@posteo.net> writes:
> David Masterson <dsmasterson@gmail.com> writes:
>
>> 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.
>
> We do document the line breaks in
> https://orgmode.org/manual/Paragraphs.html
The only thing I see with respect to '\\' is:
Paragraphs are separated by at least one empty line. If you need to
enforce a line break within a paragraph, use ‘\\’ at the end of a line.
Which doesn't answer the question of why org-add-note (etc) added it the
end of the first line of a Note which lead to my confusion. It's easy to
assume, if Org is adding '\\' to the first line of the Note and the Note
is a unit, then this is there to prevent folding/wrapping in the Note
when Org does "something" (but what?).
--
David Masterson
next prev parent reply other threads:[~2023-12-09 2:33 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
2023-12-07 10:44 ` Ihor Radchenko
2023-12-09 2:27 ` David Masterson [this message]
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=LV8P223MB0920DBA505A2D4080311CB4AA289A@LV8P223MB0920.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).