unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Colin Baxter 😺" <m43cap@yandex.com>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: , help-gnu-emacs@gnu.org
Subject: Re: Kill all proportional fonts!
Date: Tue, 28 Dec 2021 07:32:14 +0000	[thread overview]
Message-ID: <87bl11422p.fsf@yandex.com> (raw)
In-Reply-To: <87wnjp95v2.fsf@gmail.com> ("Kévin Le Gouguec"'s message of "Mon, 27 Dec 2021 20:59:13 +0100")

>>>>> Kévin Le Gouguec <kevin.legouguec@gmail.com> writes:

    > Colin Baxter 😺 <m43cap@yandex.com> writes:
    >> But I want a permanent global solution. Is there any emacs-init
    >> setting I can use to banish proportional fonts totally from emacs
    >> - preferably forever.

    > The Modus themes provide a straightforward boolean user option
    > (modus-themes-variable-pitch-ui) to opt in to proportional fonts;
    > FWIW, I think it would make sense for Emacs to provide similar
    > user options (e.g. ui-use-variable-pitch, shr-use-variable-pitch,
    > outline-use-variable-pitch).

    > IMO it would be more user-friendly and robust than advising users
    > to tweak face attributes themselves.  Consider the snippet we put
    > in NEWS during last month's mode-line experiment:

    >> (set-face-attribute 'mode-line nil :inherit 'default)

    > This puts the onus on the user to check future releases to make
    > sure the mode-line face is not supposed to inherit from other
    > elements beside variable-pitch.  Conversely, Modus-style booleans
    > mean the user can rest easy assuming Emacs will DTRT.

I agree. I personally don't like having to alter my ~/.emacs just to stay the
same. I think it should be the other way round - but what do I know?

Best wishes,

Colin Baxter.



  parent reply	other threads:[~2021-12-28  7:32 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-27 18:19 Kill all proportional fonts! Colin Baxter 😺
2021-12-27 18:34 ` Eli Zaretskii
2021-12-28  6:21   ` Colin Baxter 😺
2021-12-27 19:59 ` Kévin Le Gouguec
2021-12-28  6:25   ` Colin Baxter 😺
2021-12-28  7:32   ` Colin Baxter 😺 [this message]
2021-12-28  7:51     ` tomas
2021-12-28  8:00       ` Po Lu
2021-12-28  8:31         ` tomas
2021-12-28  9:38           ` Po Lu
2021-12-28 10:13             ` tomas
2021-12-28 19:02             ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-12-28 19:35     ` Someone start maintaining luddites.el Teemu Likonen
2021-12-28 19:45       ` Colin Baxter 😺
2021-12-28 22:44       ` Fu Yuan
2021-12-28 23:40         ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-12-29  0:58           ` Fu Yuan
2021-12-29  4:48             ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-12-29  6:13             ` Po Lu
2021-12-29  6:51               ` Yuan Fu
2021-12-29  7:05                 ` Po Lu
2021-12-29  8:06                   ` Yuan Fu
2021-12-29  9:19                     ` Po Lu
2021-12-31 22:00                       ` Yuan Fu
2022-01-01  0:05                         ` Po Lu
2021-12-29 11:41         ` Philip Kaludercic
2021-12-31 21:49           ` Yuan Fu
2021-12-31 15:03     ` Kill all proportional fonts! Ken Goldman

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=87bl11422p.fsf@yandex.com \
    --to=m43cap@yandex.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=kevin.legouguec@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.
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).