From: Ramesh Nedunchezian <email@example.com>
To: "firstname.lastname@example.org" <email@example.com>
Subject: Re: Bug (HTML/TexInfo etc): Commented code block gets through to exporter when it shouldn't [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
Date: Fri, 30 Apr 2021 10:42:52 +0530 [thread overview]
Message-ID: <TY2PR0101MB3693D51EE9CC9D8342F06101DA5E9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com> (raw)
This is not an exporter bug, but a fontifier bug.
There is no space after the leading '#' in the "problematic" lines.
Yet, the fontifier seems to think that lines which shouldn't be
commented-out lines are actually commented-out lines.
I think I should have trusted my own screenshots rather than the org's
default fontifier :-(
I really don't know how I got that snippet in that state. When I
comment out a source snippet afresh, Org untabifies the snippet.
On 30/04/21 10:30 am, Ramesh Nedunchezian wrote:
> Bug (HTML/TexInfo etc):
> Commented code block gets through to exporter when it shouldn't
> [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)]
> See the attached files. The `.txt' file is actually a `.org' file.
> The surprising behaviour--surprising at least to me--is because of the
> presence of tabs in the source block, that is commented out.
> Screenshots show where the tabs are in org file, and how the HTML
> output is rendered.
> When I untabify the file, everything looks fine.
> I have created this report with `emacs -Q' (i.e., with a capital Q),
> and whatever Org that ships with it.
> Emacs : GNU Emacs 28.0.50 (build 6, x86_64-pc-linux-gnu, GTK+ Version 3.24.24, cairo version 1.16.0)
> of 2021-04-28
> Package: Org mode version 9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)
next parent reply other threads:[~2021-04-30 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <firstname.lastname@example.org>
2021-04-30 5:12 ` Ramesh Nedunchezian [this message]
2021-04-30 5:00 Bug (HTML/TexInfo etc): Commented code block gets through to exporter when it shouldn't [9.4.4 (release_9.4.4 @ /usr/local/share/emacs/28.0.50/lisp/org/)] Ramesh Nedunchezian
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).