unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Sivaram Neelakantan <nsivaram.net@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: terminal emacs configuration take 2
Date: Fri, 13 Aug 2021 21:22:06 +0530	[thread overview]
Message-ID: <858s15wdeh.fsf@gmail.com> (raw)
In-Reply-To: CAHa53uz3Py48gGgzCzJX9dr96JmCSAnkJ+Lh9oiPK6f=UF5ecg@mail.gmail.com

On Thu, Aug 12 2021,Tim Visher wrote:


[snipped 14 lines]

> IMHO the best way to 'theme' emacs in a terminal is to apply the color
> theme to the terminal emulator and leave emacs alone, save for setting the
> frame-background-mode to light or dark if it's not being detected properly.
> The reason for this is that anything that I want to change about colors for
> emacs I'd really like to have applied for all my terminal applications. Why
> would I settle for nice colors in emacs and then jarring in colors in bash?
>
> Furthermore many of the configuration options you're referring to have no
> analog in terminal emacs. Certainly fonts but also toolbars and frame
> borders and such just aren't configurable in any meaningful way AFAIK. That
> said, again setting the font in your terminal emulator makes emacs _and_
> the rest of your terminal experience nice.

Right, went ahead and changed the MS Terminal fontsize instead of
trying anything in emacs.

>
> That said, if you can already detect that you're in a terminal and
> furthermore that you're trying to have a single config that behaves
> differently in CLI vs. GUI then whatever you're configuring can just go
> behind if or when statements in your config file. Just be aware that some
> of it isn't relevant.

Yeah, using (when (window-system) ... to wrap my GUI settings.


Thanks.

[snipped 14 lines]



sivaram
-- 




      reply	other threads:[~2021-08-13 15:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11 14:51 terminal emacs configuration take 2 Sivaram Neelakantan
2021-08-12 12:54 ` Tim Visher
2021-08-13 15:52   ` Sivaram Neelakantan [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

  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=858s15wdeh.fsf@gmail.com \
    --to=nsivaram.net@gmail.com \
    --cc=help-gnu-emacs@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.
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).