From: Jean Louis <bugs@gnu.support>
To: "Sébastien Miquel" <sebastien.miquel@posteo.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Org-mode blocks multiline fontification performance
Date: Thu, 24 Jun 2021 09:38:58 +0300 [thread overview]
Message-ID: <YNQogrIkIlFgYvij@protected.localdomain> (raw)
In-Reply-To: <a4b6a4d0-b40d-e787-0a2a-2a083559a30c@posteo.eu>
* Sébastien Miquel <sebastien.miquel@posteo.eu> [2021-06-24 09:27]:
> Jean Louis writes:
> > Use the chunked approach, make 2 files one including the other.
> A workaround, certainly. But a reasonable document might contains some 20
> such
> blocks of moderate size, say 10-30 lines each.
>
> Really what I'm wondering is if there's a different way to achieve such
> fontification with font-lock.
Somebody else may help on that.
Personally I have switched from Org to meta-level database backed
editing of any objects with any kind of modes. I am similarly using
programming blocks (often PostgreSQL reports) and they are opened as a
single object in PostgreSQL or SQL mode. I can describe them but their
description is in a different place and separate. If I wish to include
them in a main Org (or other type) file, it is matter of a second, and
their report is included. Though I don't use files the same approach
can work well with files and Org files to include programming blocks
from other files.
Then I would make a non-exporting link in Org file that brings me to
other file to be edited, and in that other (included) file I would
make a link back to the master Org file. This way switching back and
forth is easy.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2021-06-24 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 18:41 Org-mode blocks multiline fontification performance Sébastien Miquel
2021-06-24 6:12 ` Jean Louis
2021-06-24 6:26 ` Sébastien Miquel
2021-06-24 6:38 ` Jean Louis [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YNQogrIkIlFgYvij@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=sebastien.miquel@posteo.eu \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.