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

[uzibalqa via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>]

Sent with Proton Mail secure email.

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


> uzibalqa uzibalqa@proton.me writes:
> 
> > 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.
> 
> 
> It is easy enough. It is documented in the Emacs manual and in
> countless pieces of system documentation.
> 
> > Who understands how Xresources works when a user does not even have a user-level
> > configuration dotfile in "~/.Xresources".
> 
> 
> Everyone who uses X is expected to have read the relevant documentation.
> What resources are, and where they are found, is even explained in the
> comp.windows.x FAQ, which is where you should look first for help with
> any problems.

However, it has been recommended to users for ages that customizing faces should be done
from within Emacs, instead of using X resources.  I am trying to get you to follow this
school of thought.  Instead we are trying to push even more stuff, requiring users
to also read the relevant documentation for x-resources.  All this and more, the Emacs
Manual, The Emacs Lisp Reference, The Emacs source code as not everything in documented,
and so on.  If it has been recommended to customise faces from within Emacs, then why
have by default the capture of settings from things not recommended.  This kind of design
ideas is winding up people something awful.  Emacs cannot even agree with itself.