all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: hackerb9 <maildaemon@wongs.net>
Cc: 36320@debbugs.gnu.org
Subject: bug#36320: 25.1; Do not prioritize Xresources over customized font, especially not *Font
Date: Thu, 26 Nov 2020 13:00:38 +0100	[thread overview]
Message-ID: <87y2iotjix.fsf@gnus.org> (raw)
In-Reply-To: <87blyrlc7a.fsf@yourmachine.yourdomain.tld> (hackerb9's message of "Thu, 20 Jun 2019 22:49:45 -0700")

hackerb9 <maildaemon@wongs.net> writes:

> You can test it like so:
>
>     $ echo '*font:variable' | xrdb -merge
>     $ emacs
>
> You'll notice that it overrides a default font saved in your .emacs
> file. E.g., 
>
>     (custom-set-faces
>      '(default ((t (:family "Latin Modern Mono" :foundry "GNU" :slant normal :weight normal :height 120 :width normal)))))
>
> This is very confusing behavior. It makes more sense that anything set
> within a user's .emacs init file will override an Xresource preference —
> which could have even been set by the site's system administrator, not
> the user.

The X resources are set per display, so it's more likely that they are
correct than the .emacs settings (which make sense as a fallback).

If you're not working on different systems with a shared $HOME (over NFS
or something), then this probably doesn't make that much sense, but
that's the common architecture when this was made, and changing this now
would break many people's setups, probably.

So this can't be changed at this point, and I'm closing this bug report.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2020-11-26 12:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-21  5:49 bug#36320: 25.1; Do not prioritize Xresources over customized font, especially not *Font hackerb9
2020-11-26 12:00 ` Lars Ingebrigtsen [this message]
2020-11-26 15:44   ` martin rudalics

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=87y2iotjix.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=36320@debbugs.gnu.org \
    --cc=maildaemon@wongs.net \
    /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.