From: "Arsen Arsenović" <arsen@aarsen.me>
To: "Dr. Arne Babenhauserheide" <arne_bab@web.de>
Cc: Cecilio Pardo <cpardo@imayhem.com>, emacs-devel <emacs-devel@gnu.org>
Subject: Re: Colorizing source code in Info manuals
Date: Fri, 06 Dec 2024 01:31:48 +0100 [thread overview]
Message-ID: <86plm5tzwr.fsf@aarsen.me> (raw)
In-Reply-To: <87ttbh4v5l.fsf@web.de> (Arne Babenhauserheide's message of "Thu, 05 Dec 2024 23:33:42 +0100")
[-- Attachment #1: Type: text/plain, Size: 1139 bytes --]
"Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
> Cecilio Pardo <cpardo@imayhem.com> writes:
>
>> As texinfo is not going to add features like color to the Info format,
>
> This could also be added in HTML Exports via Javascript-Libraries.
And without: (texinfo) Syntax Highlighting
>> I think maybe emacs could add some itself.
>>
>> For example, the Emacs Lisp Intro uses @smallexample blocks for
>> presenting lisp code. I modified makeinfo more or less successfully to
>> generate a file with the line numbers where these blocks start. With
>> this kind of information, emacs could fontify the source code.
>>
>> Does this sound good?
>
> That definitely sounds interesting!
>
> Could it also detect source blocks in *info* on the fly and then
> highlight the block like orgmode does it?
Instead of guesswork, the info format should be extended to contain the
language ID @example can take as an argument.
Really, the entire info format can be significantly better. It is
currently a marked-up catfile.
IMO, it should be replaced with something that has a proper DOM.
--
Arsen Arsenović
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 381 bytes --]
next prev parent reply other threads:[~2024-12-06 0:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 22:06 Colorizing source code in Info manuals Cecilio Pardo
2024-12-05 22:33 ` Dr. Arne Babenhauserheide
2024-12-06 0:31 ` Arsen Arsenović [this message]
2024-12-06 8:39 ` Cecilio Pardo
2024-12-08 5:17 ` Richard Stallman
2024-12-08 18:08 ` Cecilio Pardo
2024-12-08 19:58 ` Björn Bidar
2024-12-11 4:33 ` Richard Stallman
2024-12-11 10:41 ` Cecilio Pardo
2024-12-11 4:33 ` Richard Stallman
2024-12-11 11:01 ` Cecilio Pardo
2024-12-06 7:38 ` Eli Zaretskii
2024-12-06 8:52 ` Cecilio Pardo
2024-12-06 11:42 ` Eli Zaretskii
2024-12-09 4:56 ` Richard Stallman
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86plm5tzwr.fsf@aarsen.me \
--to=arsen@aarsen.me \
--cc=arne_bab@web.de \
--cc=cpardo@imayhem.com \
--cc=emacs-devel@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.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).