From: Tim Cross <theophilusx@gmail.com>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: Ihor Radchenko <yantar92@posteo.net>, emacs-orgmode@gnu.org
Subject: Re: [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language)
Date: Sun, 18 Dec 2022 12:33:23 +1100 [thread overview]
Message-ID: <86r0wxtrx8.fsf@gmail.com> (raw)
In-Reply-To: <CA+G3_PMwiLb-tX_w5je+pp9YX95muC3WOzeDo24iqhfTLoxvHA@mail.gmail.com>
Tom Gillespie <tgbugs@gmail.com> writes:
> Treating src blocks missing a lang as paragraphs is
> incorrect because according to the syntax spec they
> are syntactically still blocks (greater or lesser depending
> on your inclinations).
>
> I think the general principle we want to follow here is
> that a block (or any entity in general) should not lose
> its type because some part of its syntax is malformed
> (I have made similar arguments about property drawers).
>
I think you might be right here.
The big characteristic of source blocks and example blocks which make
them different from paragraphs is the line breaks and indentation. If
they are treated as paragraphs, won't this information be lost?
next prev parent reply other threads:[~2022-12-18 1:36 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 21:40 [BUG] ox-html does not export captions of source blocks without language Johan Bolmsjö
2022-12-14 21:51 ` Kaushal Modi
2022-12-14 22:05 ` Johan Bolmsjö
2022-12-15 9:31 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Ihor Radchenko
2022-12-15 10:32 ` Kaushal Modi
2022-12-15 11:32 ` Max Nikulin
2022-12-15 14:29 ` Tim Cross
2022-12-15 15:07 ` Ihor Radchenko
2022-12-17 5:17 ` Tom Gillespie
2022-12-18 1:33 ` Tim Cross [this message]
2022-12-17 14:47 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? Max Nikulin
2022-12-18 13:35 ` [BUG] org-latex-src-block-backend is directly used as variable instead of querying export option (was: [Syntax discussion] Should we treat src blocks without LANG as paragraphs?) Ihor Radchenko
2022-12-18 13:40 ` Timothy
2022-12-21 12:14 ` Ihor Radchenko
2022-12-27 14:18 ` [FR] Present list of errors in separate buffer when running org-export, similar to what org-lint does " Ihor Radchenko
2022-12-27 18:39 ` Tim Cross
2022-12-17 9:56 ` [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Ihor Radchenko
2022-12-15 13:32 ` Timothy
2022-12-27 14:08 ` [BUG] ox-html does not export captions of source blocks without language Ihor Radchenko
2023-01-16 10:09 ` Ihor Radchenko
2023-01-16 10:31 ` [ANN] orgtbl-fit tbanelwebmin
2023-01-24 19:55 ` Ihor Radchenko
2023-01-25 15:02 ` tbanelwebmin
2023-01-26 10:35 ` Ihor Radchenko
2023-01-26 19:13 ` tbanelwebmin
2023-02-20 10:50 ` Ihor Radchenko
2023-03-01 11:48 ` tbanelwebmin
2023-03-03 15:13 ` Ihor Radchenko
2023-03-05 18:46 ` tbanelwebmin
2023-01-23 13:32 ` [BUG] ox-html does not export captions of source blocks without language Ihor Radchenko
-- strict thread matches above, loose matches on Subject: below --
2022-12-16 6:15 [Syntax discussion] Should we treat src blocks without LANG as paragraphs? (was: [BUG] ox-html does not export captions of source blocks without language) Pedro Andres Aranda Gutierrez
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=86r0wxtrx8.fsf@gmail.com \
--to=theophilusx@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=tgbugs@gmail.com \
--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).