From: Richard Stallman <rms@gnu.org>
To: Cecilio Pardo <cpardo@imayhem.com>
Cc: arne_bab@web.de, emacs-devel@gnu.org
Subject: Re: Re: Colorizing source code in Info manuals
Date: Wed, 25 Dec 2024 23:30:50 -0500 [thread overview]
Message-ID: <E1tQfWM-0000w6-Ix@fencepost.gnu.org> (raw)
In-Reply-To: <31551117-3bda-4051-b345-1b1e3d597161@imayhem.com> (message from Cecilio Pardo on Wed, 25 Dec 2024 00:08:53 +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. ]]]
The feature is good, but some of those colors are too light in color
to be easy to see. For instance, the color used for comments
and the color used for `defun' are too light, so that text in the PDF is hard
to read on the screen.
I suggest playing with different default colors for use in the Texinfo
PDFs.
--
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-26 4:30 UTC|newest]
Thread overview: 20+ 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
2024-12-26 4:30 ` Richard Stallman [this message]
2024-12-26 8:56 ` 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=E1tQfWM-0000w6-Ix@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).