From: Cecilio Pardo <cpardo@imayhem.com>
To: rms@gnu.org
Cc: arne_bab@web.de, emacs-devel@gnu.org
Subject: Re: Colorizing source code in Info manuals
Date: Wed, 25 Dec 2024 00:08:53 +0100 [thread overview]
Message-ID: <31551117-3bda-4051-b345-1b1e3d597161@imayhem.com> (raw)
In-Reply-To: <E1tLEPW-0000nK-A8@fencepost.gnu.org>
[-- Attachment #1: Type: text/plain, Size: 660 bytes --]
With a modification in Texinfo to add the location of @example commands
to the "Tags Table" of Info files, and some lisp to search that and
propertize text, I'm getting the results in the attached images (with
and without the code colors).
To take advantage of this, Texinfo files need to indicate the language
used on the example so we know how to fontify. Also, uses of
@smallexample should change to @example. The Lisp Intro uses
@smallexample a lot. If no language is specified, we still get the gray
box around the code.
Now I need to take this change (which will take some work) to the
Texinfo developers, if it looks worth the effort.
[-- Attachment #2: emacs_6vCjiX38X6.png --]
[-- Type: image/png, Size: 96433 bytes --]
[-- Attachment #3: emacs_cs4rqmLikg.png --]
[-- Type: image/png, Size: 93438 bytes --]
next prev parent reply other threads:[~2024-12-24 23:08 UTC|newest]
Thread overview: 21+ 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ć
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 21:04 ` chad
2024-12-11 4:33 ` Richard Stallman
2024-12-11 11:01 ` Cecilio Pardo
2024-12-11 17:14 ` [External] : " Drew Adams
2024-12-24 23:08 ` Cecilio Pardo [this message]
2024-12-26 4:30 ` Richard Stallman
2024-12-26 8:56 ` Cecilio Pardo
2024-12-28 4:34 ` Richard Stallman
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=31551117-3bda-4051-b345-1b1e3d597161@imayhem.com \
--to=cpardo@imayhem.com \
--cc=arne_bab@web.de \
--cc=emacs-devel@gnu.org \
--cc=rms@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).