From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Trailing whitespace after export snippets without a transcoder
Date: Thu, 25 Apr 2024 17:54:17 +0700 [thread overview]
Message-ID: <v0dcoq$h8v$1@ciao.gmane.io> (raw)
In-Reply-To: <87wmoprzm4.fsf@localhost>
On 23/04/2024 02:01, Ihor Radchenko wrote:
> For example, consider an HTML exporter that aligns tags nicely and
> keeps blank lines between markup blocks for readability. If we
> remove such blank lines unconditionally, it will be problematic.
I consider that just newlines are enough to make HTML markup human
readable. I believe blank lines appear in HTML due to conditional
constructs interpreted by various template engines and almost nobody
cares concerning actual formatting in such cases.
However I proposed to make this feature an option that is turned on by
default.
> I guess that I can change the condition to not include trailing space
> from (rx whitespace eol) to (rx (any " \t|) eol).
One more time I forgot that neither \n nor non-breakable space are
included into post-blank.
I think, more permissive regexp may be used. At least it should accept
newlines and any space after it
(rx (any " \t" eol) (zero-or-more whitespace) eos)
Moreover, post-blank of the pruned object may be ignored when the
following element starts with spaces other than purely zero width ones.
In my opinion, keeping extra spaces (e.g. post-blank ones from pruned
objects) makes less harm than aggressively stripping them. Anyway some
backends must normalize spaces (while for others they do not matter).
While newline characters are not affected, this part of change does not
affect accidental split of paragraphs.
My feeling is that extensive test suite is required. It would be easier
to review what cases are not handled yet.
next prev parent reply other threads:[~2024-04-25 10:55 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-22 0:04 Inline comments ypuntot
2023-06-22 1:50 ` Max Nikulin
2023-06-28 15:51 ` [PATCH] org-faq.org: " Max Nikulin
2023-06-29 10:47 ` Ihor Radchenko
2023-06-30 10:34 ` Max Nikulin
2023-07-01 10:48 ` Ihor Radchenko
2023-08-06 18:34 ` Bastien Guerry
2023-07-01 15:24 ` Ihor Radchenko
2023-07-02 5:46 ` Org FAQ design (Re: [PATCH] org-faq.org: Inline comments) Max Nikulin
2023-07-08 5:48 ` [PATCH v2] org-faq.org: Inline comments Max Nikulin
2023-07-08 9:31 ` Ihor Radchenko
2023-07-10 16:09 ` Max Nikulin
2023-09-01 11:28 ` Ihor Radchenko
2024-04-15 12:17 ` Ihor Radchenko
2024-04-17 14:44 ` Max Nikulin
2024-04-20 11:14 ` Trailing whitespace after export snippets without a transcoder (was: [PATCH v2] org-faq.org: Inline comments) Ihor Radchenko
2024-04-20 15:02 ` Trailing whitespace after export snippets without a transcoder Max Nikulin
2024-04-21 13:00 ` Ihor Radchenko
2024-04-22 10:45 ` Max Nikulin
2024-04-22 19:01 ` Ihor Radchenko
2024-04-25 10:54 ` Max Nikulin [this message]
2024-04-28 11:19 ` 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='v0dcoq$h8v$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@gnu.org \
/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).