From: Emanuel Berg <incal@dataswamp.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : Running emacs without any customisation
Date: Fri, 14 Oct 2022 07:10:51 +0200 [thread overview]
Message-ID: <87k053xa5g.fsf@dataswamp.org> (raw)
In-Reply-To: JcP34vyoVs0Q6Qc4EwbSxecpkgYBh3FpPFe8Uc674j3Wp4FSKZ1lNfsM4OMlHhhd1I1p4sjIfyUbDdHeRJZVziflzWtPdfCR7pHKV5uUSbQ=@proton.me
Here is that old (2013-08-07) article again.
I understand it but not the 1-3 part, really? I wonder what
I is?
~/.Xdefaults and ~/.Xresources
The old solution was: Whenever an X (Xlib) application is
started, it looks in ~/.Xdefaults for settings before it
executes; the file had to be on the same filesystem, in the
user's HOME.
The new or half-new solution is: Whenever an X application is
started, it looks for settings in RESOURCE_MANAGER
(XA_RESOURCE_MANAGER) in the root window of screen 0.
Settings are there only if xrdb(1) has been executed since the
start of X. If not, the _fallback_ is to look for settings in
~/Xdefaults (every time and for every application, i.e.
the same as the old solution).
xrdb doesn't necessarily read ~/.Xresources, that's
a convention. In face xrdb can read many and any file, even
~/.Xdefaults. xrdb has to be used even for
With Xresources any user can use, or not use, xrdb to
load settings.
Xresources are mobile; compare to ~/.Xdefaults which hs to be
in $HOME.
To test the enhanced mobility, after reading resources with
xrdb, do the following:
1. In X, a WM (e.g. openbsd-cwm) a terminal emulator (xterm),
ssh to some system with the -Y option. There, start xterm,
or any other application that you have configured on your
local system but not on the system to which you ssh'd.
Then, do the same on you local system, start xterm.
They look the same!
2. Now, on your local system, run 'xrdb -remove'. Again, start
xterm on both the remote and the local system - again, they
look the same, only now, they aren't configured.
3. Last, to demonstrate the limited scope of Xdefaults,
without using xrdb since step 2, on you local system, run
'cp ~/.Xresources ~/.Xdefaults' (after salvaging anything
of value from Xdefaults), then run xterm on both remote and
local system. The remote xterm is unconfigured, but the
local xterm is - only this time from Xdefaults.
Notes:
The #1 Google hit on this issue recommends making ~/.xinitrc
an executable, with 'chmod +x' - this is not needed.
Also, the same article exemplifies the use of xrdb in
.xinitrc with a trailing '&', making xrdb a background
process. This isn't right, as the next program run from
.xinitrc may use the very same settings, that xrdb is in the
process of setting up, and that must be completed before any
application that depends on it can be run. The cure is,
remove the '&'.
Some xterm settings useful for testing:
xterm*autoWrap: true
xterm*pointerMode: 2
xterm*geometry: 77x28
xterm*background: black
xterm*foreground: green4
xterm*faceName: default
xterm*metaSendsEscape: true
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2022-10-14 5:10 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 [this message]
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
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=87k053xa5g.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--cc=help-gnu-emacs@gnu.org \
/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).