unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
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 13:56:53 +0000	[thread overview]
Message-ID: <LBMxUMsOl4TcEenBheVBoSLi86AMIb25Mh2gqYzKkMy_wcpUgZutCxk9oRYdowQsR-aerKsM14ZVQPnA311NfpqDHpb6Ds7IWKagQK7U6ik=@proton.me> (raw)
In-Reply-To: <87o7ufc1cr.fsf@yahoo.com>


------- Original Message -------
On Thursday, October 13th, 2022 at 1:14 PM, Po Lu <luangruo@yahoo.com> wrote:


> uzibalqa uzibalqa@proton.me writes:
> 
> > But things are working the other way round. Things get messed up, then have
> > to figure out what produced it, thing gets too complicated beyond what I consciously
> > did, then emacs uses them. Does a user have control this way? Of course not.
> 
> 
> You have control: inhibit-x-resources.

The sensible way is to have the user exactly specify the file he wants for setting
the resource parameters.  This would avoid picking up settings that only the gods 
know where they are, and what had set them up in the first place. 

What could happen if the actual x-resource settings are removed from the system?
Would it be detrimental to users in unknown ways?
 
> > My challenge in why emacs is taking authority from x-resources. Rather than
> > firing vanilla emacs with some properly defined face with good accessibility.
> 
> 
> [...]
> 
> > If emacs maintainers are actually so smart, how long is it going to take exactly
> > for vanilla emacs to start using some well defined accessibility metrics such
> > as modus-themes, so that the maximum number of users can comfortably use it.
> 
> 
> Take the complaint to the Trisquel or MATE developers.





  parent reply	other threads:[~2022-10-13 13:56 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
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 [this message]
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='LBMxUMsOl4TcEenBheVBoSLi86AMIb25Mh2gqYzKkMy_wcpUgZutCxk9oRYdowQsR-aerKsM14ZVQPnA311NfpqDHpb6Ds7IWKagQK7U6ik=@proton.me' \
    --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).