From: Jean Louis <bugs@gnu.support>
To: Yilkal Argaw <yilkalargawworkneh@gmail.com>
Cc: 60064@debbugs.gnu.org
Subject: bug#60064: adding ansi-color faces for themes that do not have them
Date: Fri, 16 Dec 2022 09:24:31 +0300 [thread overview]
Message-ID: <Y5wPHwQuJIibHD4b@protected.localdomain> (raw)
In-Reply-To: <CAJddU=o5Nx2uM+Pv9Deggzv49v44GQidY=TD7+LQ+AViiyRrbg@mail.gmail.com>
* Yilkal Argaw <yilkalargawworkneh@gmail.com> [2022-12-14 15:48]:
> Shell and Eshell in emacs inherit from ansi-colors which affects how output
> from command line programs that make use of them. While many of the themes
> included with emacs define faces for them, others do not. Specifically
> adwaita, deeper-blue, light-blue, manoj-dark, tsdh-dark, tsdh-light,
> wheatgrass and whiteboard themes. This makes output from terminal
> applications that make use of ansi-colors look awkward or hard to read when
> using those themes(i.e. in shell or eshell). Is it possible to enforce
> definitions for ansi-colors at least in the themes that are included with
> emacs. Because interaction with the shells is an essential part of using
> emacs for so many people.
That IS very disturbing, yes, though I do not know in which
themes it practically creates the problem. You have done better research.
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
prev parent reply other threads:[~2022-12-16 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-14 12:46 bug#60064: adding ansi-color faces for themes that do not have them Yilkal Argaw
2022-12-15 15:54 ` Akib Azmain Turja via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-16 6:24 ` Jean Louis [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y5wPHwQuJIibHD4b@protected.localdomain \
--to=bugs@gnu.support \
--cc=60064@debbugs.gnu.org \
--cc=yilkalargawworkneh@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.