From: Tom Gillespie <firstname.lastname@example.org>
To: emacs-orgmode <email@example.com>
Subject: Re: Comments break up a paragraph when writing one-setence-per-line
Date: Sat, 2 Oct 2021 10:57:51 -0700 [thread overview]
Message-ID: <CA+G3_POOAg=DcxDWUHw6NOA3eSqUqaPGFSN7HPNLyvVCfWeL1g@mail.gmail.com> (raw)
A general comment (heh) here. This is not a bug and not easily fixed.
Line comments are their own top level element distinct from
paragraphs. If you need something that fits in a paragraph you can use
@@comment:@@ at the start of a line.
I agree that it is annoying, but Org line comment syntax also only
works if it starts the line, so the behavior diverges from traditional
code comments. It may make sense to update the docs to call them "line
comments" instead of just comments.
One area where we could almost certainly do better is in how line
comments break up the flow of text. I'm not sure there will ultimately
be much we can do about it, but it is worth investigating.
next prev parent reply other threads:[~2021-10-02 17:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-16 16:06 Comments break up a paragraph when writing one-setence-per-line William Denton
2021-07-16 16:34 ` Bruce D'Arcus
2021-07-16 18:10 ` Kaushal Modi
2021-07-17 1:50 ` Samuel Wales
2021-07-18 8:21 ` Maxim Nikulin
2021-07-19 14:03 ` Eric S Fraga
2021-07-21 14:48 ` Maxim Nikulin
2021-07-21 15:22 ` Eric S Fraga
2021-07-21 16:13 ` Maxim Nikulin
2021-10-02 17:57 ` Tom Gillespie [this message]
2021-10-03 11:34 ` Max Nikulin
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).