From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
To: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re:Re: [DISCUSSION] Refactoring fontification system
Date: Thu, 9 Jun 2022 07:37:46 +0200 [thread overview]
Message-ID: <CAO48Bk9PqxV0O0jKm63dA__e5Y=12q+4QOKNEtZxgofoPfcXtw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1226 bytes --]
Max Niulin writes:
>> On 03/06/2022 16:45, Ihor Radchenko wrote:
>>
>> From my point of view exporters may reuse code block formatters for
>> examples. It would allow to pass options to e.g. LaTeX verbatim
environment:
>> Pedro Andres Aranda Gutierrez. Re: A question/bug report(?) Wed, 30 Mar
>> 2022 07:14:54 +0200
>>
https://list.orgmode.org/orgmode/CAO48Bk_dJs1=5zgpcZwODaTsRqyRsKq1ALj6WpaXCc4bDjW3FQ@mail.gmail.com/
>
> Among other goals, the new fontification is aiming to avoid such bad
> surprises.
OK, just to add to the discussion. The original intent of my message was to
give _me_ control over what I want to colour, not delegating that to the
fontifying engine in Emacs.
I need limited and controlled colouring for text-books and lab manuals
where colouring elements of a listing goes against the publishing
standards. I only need custom colouring to "emulate" terminal output, not
for the code as such. And I could do that with the #+ATTR: if supported.
Best, /PA
--
Fragen sind nicht da um beantwortet zu werden,
Fragen sind da um gestellt zu werden
Georg Kreisler
Juju and real life:
unit-basic-16: 09:17:36 WARNING juju.worker.uniter.operation we should run
a leader-deposed hook here, but we can't yet
[-- Attachment #2: Type: text/html, Size: 1816 bytes --]
reply other threads:[~2022-06-09 5:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAO48Bk9PqxV0O0jKm63dA__e5Y=12q+4QOKNEtZxgofoPfcXtw@mail.gmail.com' \
--to=paaguti@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).