bug#58459: Getting a fresh emacs session with no customisation

[uzibalqa]

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

Sure, but do you realise how long it took to identify the culprit after the 
enforced settings did not even allow me to see the mode-line because of
terrible contrast.  Make things easy for users, rather than even more difficult.
Who understands how Xresources works when a user does not even have a 
user-level 
configuration dotfile in "~/.Xresources". 
 
> > 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.

The complaint is about the problems associated from taking instructions from 
x-resources.
The problem is simply shifted around to the Trisquel or MATE developers, rather 
than
continuing to rely on a likely broken x-resource database.