all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: adding ansi-color faces for themes that do not have them
Date: Wed, 14 Dec 2022 12:40:21 +0000	[thread overview]
Message-ID: <CAJddU=qTS4xLwo0uZFOOjTTA+XYMK96_aHDjms+y=9haxZbx9w@mail.gmail.com> (raw)
In-Reply-To: <838rjanpcn.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

Will do, thanks!

On Wed, Dec 14, 2022 at 12:26 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Yilkal Argaw <yilkalargawworkneh@gmail.com>
> > Date: Wed, 14 Dec 2022 07:10:08 +0000
> >
> > 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.
>
> Please report this as a bug, so we don't forget the issue.
>
> Thanks.
>

[-- Attachment #2: Type: text/html, Size: 1396 bytes --]

      reply	other threads:[~2022-12-14 12:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-14  7:10 adding ansi-color faces for themes that do not have them Yilkal Argaw
2022-12-14 12:26 ` Eli Zaretskii
2022-12-14 12:40   ` Yilkal Argaw [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='CAJddU=qTS4xLwo0uZFOOjTTA+XYMK96_aHDjms+y=9haxZbx9w@mail.gmail.com' \
    --to=yilkalargawworkneh@gmail.com \
    --cc=eliz@gnu.org \
    --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 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.