From: Richard Stallman <rms@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: arne_bab@web.de, emacs-devel@gnu.org
Subject: Re: Colorizing source code in Info manuals
Date: Tue, 10 Dec 2024 23:33:18 -0500 [thread overview]
Message-ID: <E1tLEPW-0000nK-A8@fencepost.gnu.org> (raw)
In-Reply-To: <c1af5ac0-e4f6-4424-9113-68c14c4c3678@imayhem.com> (message from Cecilio Pardo on Sun, 8 Dec 2024 19:08:04 +0100)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> I think some 'cheap' changes in info, such as the presentation of source
> code and emacs key sequences, in my unqualified opinion, are worth the
> effort at this point.
Would you please say specifically what extensions you're suggesting?
How would one use them? What jobs would they do?
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-12-11 4:33 UTC|newest]
Thread overview: 17+ 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 [this message]
2024-12-11 11:01 ` Cecilio Pardo
2024-12-11 17:14 ` [External] : " Drew Adams
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=E1tLEPW-0000nK-A8@fencepost.gnu.org \
--to=rms@gnu.org \
--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).