unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: uzibalqa <uzibalqa@proton.me>, Phil Sainty <psainty@orcon.net.nz>
Cc: 58459@debbugs.gnu.org
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Wed, 12 Oct 2022 18:14:33 -0700	[thread overview]
Message-ID: <CADwFkmnVydkSeqHZa1axZ1St6Y-dciQBY3N5s-Kxw1bUUhUkCQ@mail.gmail.com> (raw)
In-Reply-To: <3gN0Jqr94UeUj3xJtDV3zGvZVbUyjtQFAloYxrdvwN_ZHa3tEUYyFv8h3VcYYSk_gxgMaaBW94kAkaAUCgbd9QKZMkkYJBty-7XOadbzHHQ=@proton.me>

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.





  reply	other threads:[~2022-10-13  1:14 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 [this message]
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
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=CADwFkmnVydkSeqHZa1axZ1St6Y-dciQBY3N5s-Kxw1bUUhUkCQ@mail.gmail.com \
    --to=stefankangas@gmail.com \
    --cc=58459@debbugs.gnu.org \
    --cc=psainty@orcon.net.nz \
    --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).