unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: uzibalqa <uzibalqa@proton.me>
Cc: Phil Sainty <psainty@orcon.net.nz>,
	58459@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Thu, 13 Oct 2022 18:22:48 +0800	[thread overview]
Message-ID: <87fsfsc9af.fsf@yahoo.com> (raw)
In-Reply-To: <zpxt4R-wW3R6hieHGUf9HHxmWMTUvdDyXyg-oc9_mmESPcWqOdr-rA_f_TWyTnxEIKB8pzVG_NVrZmg_Xiytil40jiSnC_jhVsaQIbb-91Y=@proton.me> (uzibalqa@proton.me's message of "Thu, 13 Oct 2022 02:02:48 +0000")

uzibalqa <uzibalqa@proton.me> writes:

> Fine, but when this happens on Trisquel, then it is a topic of concern.  Aren't
> maintainers supposed to work together?  Most times everybody works independently
> with almost no concern or collaboration.

Users actually want the desktop environment to set resources that make
applications match the system stylesheet.

If you don't, remove the resources.  We cannot make decisions for the
Trisquel developers.

> I wonder the rational behind considering x-resources as authoritative.
> As you mentioned, these days x-resources are a rather esoteric feature.
> Your design should be the other way round. With a flag `enforce-x-resources'.
> So one always gets vanilla emacs with no init file, or when the init file
> does nothing, or something goes wrong.  It is very easy to make an init file
> fail when one is writing emacs functionalities and packages.

Emacs is an X program, and good X programs respect resources set in the
usual locations.  It is a decades old convention.

> It is also an emacs bug from my point of view.  Especially when you confirm 
> that x-resources are not used all that often anymore. 

No.





  parent reply	other threads:[~2022-10-13 10:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-12  0:09 bug#58459: Getting a fresh emacs session with no customisation uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12  9:51 ` Stefan Kangas
2022-10-12 12:52   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 12:56     ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 16:23       ` Stefan Kangas
2022-10-12 17:30         ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 21:11           ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-12 22:47             ` Phil Sainty
2022-10-12 23:16               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13  1:14                 ` Stefan Kangas
2022-10-13  2:02                   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13  3:01                     ` Stefan Kangas
2022-10-13 15:48                       ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 10:22                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-13 12:09                       ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:19                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 12:52                           ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:14                             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:27                               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:19                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:36                                   ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 13:56                               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 14:15                                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 15:47                         ` Eli Zaretskii
2022-10-13 16:06                           ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 16:20                             ` Eli Zaretskii
2022-10-13 17:51                               ` uzibalqa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-13 18:35                                 ` Christopher Dimech
2022-10-14  8:14                                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-14 19:40                                     ` Christopher Dimech
2022-10-13 16:36                           ` Christopher Dimech
2022-10-13 19:13                             ` Eli Zaretskii
2022-10-13 19:20                               ` Christopher Dimech
2022-10-13 10:30                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87fsfsc9af.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58459@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=psainty@orcon.net.nz \
    --cc=stefankangas@gmail.com \
    --cc=uzibalqa@proton.me \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).