From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Large source block causes org-mode to be unusable
Date: Wed, 23 Jun 2021 23:40:31 +0700 [thread overview]
Message-ID: <savo60$7bj$1@ciao.gmane.io> (raw)
In-Reply-To: <CAFhsWEg7WSVorQNEmAnxqcqyu5YcqhxshTyeE0svmNGrmDrJUg@mail.gmail.com>
On 22/06/2021 19:32, Léo Ackermann wrote:
>
> I suggest that special block in LateX export
> (https://orgmode.org/manual/Special-blocks-in-LaTeX-export.html) may be
> treated differently.
Generally I agree with you that #+begin_proof should be a thin wrapper
unlike a source code block. However I am not familiar with
fontification, so I can not reason if it is feasible. Maybe the code is
watching if something like #+end_proof appeared, so block finished.
On the other hand my impression was that \begin{proof} environment is
intended to emphasize a paragraph or two to separate it from regular
text on the same page. My expectation is that 4-page long proof should
be formatted as ordinary sections and subsections.
If proof environment is still required, maybe it is possible to
customize export backend to have proofs as a headings with some property
in the source document. E.g. beamer backend converts headings to frames.
I have never tried such tricks, so I am unaware how much work is
required for such approach.
next prev parent reply other threads:[~2021-06-23 16:41 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 18:27 Large source block causes org-mode to be unusable Léo Ackermann
2021-06-21 18:43 ` John Hendy
2021-06-21 18:57 ` Sébastien Miquel
2021-06-21 19:22 ` John Kitchin
2021-06-21 19:36 ` John Hendy
2021-06-21 20:41 ` Tom Gillespie
2021-06-22 4:48 ` Tim Cross
2021-06-22 7:54 ` Eric S Fraga
2021-06-22 11:20 ` Léo Ackermann
2021-06-22 12:13 ` Eric S Fraga
2021-06-22 12:32 ` Léo Ackermann
2021-06-22 13:03 ` Eric S Fraga
2021-06-22 13:32 ` Léo Ackermann
2021-06-23 16:40 ` Maxim Nikulin [this message]
2021-06-23 19:42 ` Gennady Uraltsev
2021-06-24 7:54 ` Eric S Fraga
2021-06-26 14:10 ` Léo Ackermann
2021-06-28 8:28 ` Sébastien Miquel
2021-06-28 10:42 ` Eric S Fraga
2021-06-28 10:40 ` Eric S Fraga
2021-06-22 6:10 ` Timothy
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='savo60$7bj$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).