From: Christopher Dimech <dimech@gmx.com>
To: pquessev@gmail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: [External] : Running emacs without any customisation
Date: Thu, 13 Oct 2022 18:41:33 +0200 [thread overview]
Message-ID: <trinity-288807ad-9515-412c-9817-9c30140476cb-1665679293131@3c-app-mailcom-bs03> (raw)
In-Reply-To: <82mt9zkbmz.fsf@gmail.com>
> Sent: Friday, October 14, 2022 at 3:04 AM
> From: "Pascal Quesseveur" <pquessev@gmail.com>
> To: help-gnu-emacs@gnu.org
> Subject: Re: [External] : Running emacs without any customisation
>
> >"u" == uzibalqa <uzibalqa@proton.me> a écrit :
>
> u> Hello Pascal. Someone said that other parameters besides those
> u> tagged EMACS could affect emacs configuration.
>
> It could happen that a general resource can affect emacs. If I'm not
> mistaken if there is a general resource eg. *.background it could be
> applied to a client if the client does not set the value by some
> means.
You are completely correct Pascal. Emacs does take *.background
and much more from whatever there is in the x-resource database.
Keeping in mind that the x-resource database can be modified by
programs the user does not fully have control of, I resist the
school of thought that says that one should obey the x-resource
database whatever they are. Using the x-resource database in
emacs blindly in unwise.
> u> happen if I remove all x-resource setting from the database.
> u> Would you reckon serious repercussions, a user might not be aware
> u> he is doing?
>
> It's hard to say because it depends on how other programs work.
>
>
> --
> Pascal Quesseveur
> pquessev@gmail.com
>
>
>
next prev parent reply other threads:[~2022-10-13 16:41 UTC|newest]
Thread overview: 118+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-10 11:36 Running emacs without any customisation uzibalqa
2022-10-10 11:46 ` Thibaut Verron
2022-10-10 11:54 ` uzibalqa
2022-10-10 12:10 ` Thibaut Verron
2022-10-10 12:41 ` uzibalqa
2022-10-10 23:40 ` Emanuel Berg
2022-10-11 15:00 ` [External] : " Drew Adams
2022-10-10 23:30 ` Emanuel Berg
2022-10-11 15:02 ` Michael Heerdegen
2022-10-11 15:13 ` Michael Heerdegen
2022-10-11 15:56 ` uzibalqa
2022-10-11 15:59 ` uzibalqa
2022-10-11 16:19 ` Michael Heerdegen
2022-10-11 15:57 ` [External] : " Drew Adams
2022-10-11 16:17 ` Michael Heerdegen
2022-10-11 17:24 ` Drew Adams
2022-10-11 22:48 ` Michael Heerdegen
2022-10-12 1:33 ` Drew Adams
2022-10-11 18:52 ` uzibalqa
2022-10-11 19:10 ` Michael Heerdegen
2022-10-11 19:13 ` uzibalqa
2022-10-11 19:43 ` Michael Heerdegen
2022-10-11 20:26 ` uzibalqa
2022-10-11 20:45 ` Michael Heerdegen
2022-10-11 20:53 ` uzibalqa
2022-10-11 21:23 ` Michael Heerdegen
2022-10-11 22:01 ` uzibalqa
2022-10-11 22:28 ` Michael Heerdegen
2022-10-11 22:31 ` uzibalqa
2022-10-11 22:47 ` Michael Heerdegen
2022-10-11 23:00 ` uzibalqa
2022-10-11 17:45 ` RE: [External] : " Christopher Dimech
2022-10-12 0:12 ` uzibalqa
2022-10-12 1:44 ` Michael Heerdegen
2022-10-12 9:59 ` Dr Rainer Woitok
2022-10-12 12:47 ` uzibalqa
2022-10-12 14:45 ` Michael Heerdegen
2022-10-12 15:30 ` Drew Adams
2022-10-12 15:56 ` uzibalqa
2022-10-12 17:03 ` Michael Heerdegen
2022-10-12 17:50 ` uzibalqa
2022-10-12 18:25 ` Michael Heerdegen
2022-10-12 18:54 ` uzibalqa
2022-10-12 19:06 ` Michael Heerdegen
2022-10-12 20:42 ` uzibalqa
2022-10-12 20:51 ` Michael Heerdegen
2022-10-12 21:05 ` uzibalqa
2022-10-12 21:35 ` Michael Heerdegen
2022-10-12 21:45 ` uzibalqa
2022-10-12 22:11 ` Michael Heerdegen
2022-10-12 22:25 ` uzibalqa
2022-10-13 0:33 ` Dale Snell
2022-10-13 0:46 ` uzibalqa
2022-10-14 5:10 ` Emanuel Berg
2022-10-14 18:28 ` uzibalqa
2022-10-13 0:40 ` Po Lu
2022-10-13 0:43 ` Po Lu
2022-10-13 1:09 ` uzibalqa
2022-10-13 2:02 ` Po Lu
2022-10-13 11:17 ` Dr Rainer Woitok
2022-10-13 13:18 ` Emanuel Berg
2022-10-13 14:56 ` uzibalqa
2022-10-14 0:37 ` Po Lu
2022-10-14 0:47 ` uzibalqa
2022-10-14 3:21 ` Po Lu
2022-10-13 15:03 ` Christopher Dimech
2022-10-13 16:47 ` Michael Heerdegen
2022-10-13 17:55 ` Christopher Dimech
2022-10-14 4:18 ` Jean Louis
2022-10-13 0:42 ` Po Lu
2022-10-13 0:50 ` uzibalqa
2022-10-13 1:07 ` Po Lu
2022-10-13 1:11 ` uzibalqa
2022-10-13 2:01 ` Po Lu
2022-10-13 2:05 ` uzibalqa
2022-10-13 4:03 ` Po Lu
2022-10-13 6:19 ` Emanuel Berg
2022-10-13 12:17 ` uzibalqa
2022-10-13 12:39 ` Po Lu
2022-10-13 13:10 ` uzibalqa
2022-10-13 13:20 ` uzibalqa
2022-10-14 4:09 ` Jean Louis
2022-10-14 5:11 ` Emanuel Berg
2022-10-13 13:21 ` Po Lu
2022-10-13 14:02 ` uzibalqa
2022-10-13 15:59 ` Emanuel Berg
2022-10-14 16:30 ` Drew Adams
2022-10-13 14:03 ` Pascal Quesseveur
2022-10-13 14:18 ` uzibalqa
2022-10-13 15:04 ` Pascal Quesseveur
2022-10-13 15:26 ` uzibalqa
2022-10-13 16:41 ` Christopher Dimech [this message]
2022-10-14 0:38 ` Po Lu
2022-10-14 2:02 ` Christopher Dimech
2022-10-14 3:19 ` Po Lu
2022-10-14 3:49 ` Christopher Dimech
2022-10-14 4:45 ` uzibalqa
2022-10-14 4:52 ` Christopher Dimech
2022-10-14 6:16 ` Po Lu
2022-10-14 6:31 ` Emanuel Berg
2022-10-14 16:01 ` Jean Louis
2022-10-14 18:43 ` tomas
2022-10-15 6:58 ` Jean Louis
2022-10-15 8:39 ` tomas
2022-10-15 17:38 ` Christopher Dimech
2022-10-15 19:37 ` tomas
2022-10-14 20:55 ` Emanuel Berg
2022-10-14 2:33 ` Emanuel Berg
2022-10-14 4:14 ` Jean Louis
2022-10-14 5:32 ` Christopher Dimech
2022-10-14 8:47 ` Dr Rainer Woitok
2022-10-14 9:57 ` Po Lu
2022-10-14 12:30 ` uzibalqa
2022-10-14 13:48 ` Christopher Dimech
2022-10-16 4:57 ` Jean Louis
2022-10-14 20:50 ` Emanuel Berg
2022-10-13 1:12 ` Christopher Dimech
2022-10-13 0:40 ` Po Lu
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-288807ad-9515-412c-9817-9c30140476cb-1665679293131@3c-app-mailcom-bs03 \
--to=dimech@gmx.com \
--cc=help-gnu-emacs@gnu.org \
--cc=pquessev@gmail.com \
/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.
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).