From: Christopher Dimech <dimech@gmx.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: luangruo@yahoo.com, psainty@orcon.net.nz, uzibalqa@proton.me,
58459@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#58459: Getting a fresh emacs session with no customisation
Date: Thu, 13 Oct 2022 21:20:29 +0200 [thread overview]
Message-ID: <trinity-c4f51126-8b1c-43bd-b896-c99b9fcb67af-1665688829579@3c-app-mailcom-bs03> (raw)
In-Reply-To: <83bkqfa65k.fsf@gnu.org>
> Sent: Friday, October 14, 2022 at 7:13 AM
> From: "Eli Zaretskii" <eliz@gnu.org>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: uzibalqa@proton.me, luangruo@yahoo.com, psainty@orcon.net.nz, 58459@debbugs.gnu.org, stefankangas@gmail.com
> Subject: Re: bug#58459: Getting a fresh emacs session with no customisation
>
> > From: Christopher Dimech <dimech@gmx.com>
> > Cc: uzibalqa <uzibalqa@proton.me>, luangruo@yahoo.com, psainty@orcon.net.nz,
> > 58459@debbugs.gnu.org, stefankangas@gmail.com
> > Date: Thu, 13 Oct 2022 18:36:43 +0200
> >
> > > And X resources are as much user settings as what the user sets on the
> > > init files. So Emacs cannot but obey them. It is user's
> > > responsibility to set up his/her settings according to his/her
> > > preferences.
> >
> > The user makes a good point. When a user want emacs to obey x-resources,
> > the user specify the x-resources in their init file. Rather than obey them
> > when a user did not specifically ask for that to happen.
>
> That's not how X applications work, and that's not how Emacs has
> worked since day one on X.
>
> So please stop arguing, this is not going to change.
It is my prerogative to state my outlook. And that also is not going
to change.
next prev parent reply other threads:[~2022-10-13 19:20 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
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 [this message]
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=trinity-c4f51126-8b1c-43bd-b896-c99b9fcb67af-1665688829579@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=58459@debbugs.gnu.org \
--cc=eliz@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).