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

[Stefan Kangas]

uzibalqa <uzibalqa@proton.me> writes:

>> > I am continually amazed how unreactive emacs maintainers can be to
>> > users. Either shaming them, make them look stupid
>>
>> Wow? This discussion has been between you and Stefan Kangas, and at
>> no point has Stefan been anything other than polite and informative!
>
> Early on in the discussion, the response was immediately "notabug
> close thanks".  But perhaps you are right and I am being excessive.
> Nevertheless, I am yet to be convinced how this resource thing is
> straightforward.

Please do not take us closing bugs personally.  We have thousands of
open bugs, and we try to handle them based on objective criteria.

>> > but then months or years later, it gets recognised they were right
>> > all along.

X resources are of course a rather esoteric feature these days, to most
users.  There's a reason they're not used all that often any more.  But
we will never stop supporting them, as this stuff has been that way for
decades.

> Looks that "internal-set-lisp-face-attribute-from-resource" is doing the work.
> So if emacs does not not even find an emacs init file, why does it start 
> launching
> them.

Again, I think Emacs behaves correctly here.  It's good to hear that
using `inhibit-x-resources' fixes your problem.

> Something must be going on, perhaps in the distro or desktop environment that 
> could be
> using something outside the traditional X11 approach to loading Xresources.  
> Or something
> else.
>
> I am using one of the Official Gnu Distributions (Trisquel 9).  These systems 
> should work
> well together with Gnu Programs.  At least, it is always said things are 
> planned to be this
> way.

Then you should investigate why this happens in your environment.
If you find any bugs, you should report them to the appropriate people.
If you find that it is indeed a bug in Trisquel, then it is not correct
to report it here, as we can't do anything about it.

But note that it is good form to make sure that there is a bug before
reporting one.  I would ask in some support forum first.