From: Kaushal Modi <kaushal.modi@gmail.com>
To: "Bruce D'Arcus" <bdarcus@gmail.com>
Cc: William Denton <wtd@pobox.com>, org-mode-email <emacs-orgmode@gnu.org>
Subject: Re: Comments break up a paragraph when writing one-setence-per-line
Date: Fri, 16 Jul 2021 14:10:15 -0400 [thread overview]
Message-ID: <CAFyQvY0j7fSxSnuTL6exgthEGk+EOAo=vEgTdbzEK0XMr2QECg@mail.gmail.com> (raw)
In-Reply-To: <CAF-FPGMOa_2jtmPAt-3J0Nu3jZ0RzyvYw5ctroqEkFGXgipgyg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 934 bytes --]
Hello,
On Fri, Jul 16, 2021 at 12:35 PM Bruce D'Arcus <bdarcus@gmail.com> wrote:
> On Fri, Jul 16, 2021 at 12:07 PM William Denton <wtd@pobox.com> wrote:
>
> > However, I was a bit surprised when I found that a commented line starts
> a new
> > paragraph.
>
> I hadn't yet discovered that, but I think it should be considered a
> bug.
Comments causing paragraph breaks has been a long known behavior. I learned
about it few years back, probably from one of the threads here or by
reading the code.
> The output of your example should remove the commented line
> entirely, and so be:
>
> In this paragraph I introduce an idea.
> But I am sure about this. And here is my conclusion.
>
> Perhaps it can be easily fixed?
>
I don't think it would be a very easy fix as the behavior stems from an
intentional low level implementation in org-element.el. Changing this
behavior will cause a regression in all Org exporters out there.
[-- Attachment #2: Type: text/html, Size: 1683 bytes --]
next prev parent reply other threads:[~2021-07-16 18:11 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 [this message]
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
2021-10-03 11:34 ` Max Nikulin
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='CAFyQvY0j7fSxSnuTL6exgthEGk+EOAo=vEgTdbzEK0XMr2QECg@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=bdarcus@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=wtd@pobox.com \
/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).