From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: uzibalqa Newsgroups: gmane.emacs.help Subject: Re: [External] : Running emacs without any customisation Date: Fri, 14 Oct 2022 18:28:58 +0000 Message-ID: References: <7HiwKI9ptNll3M2bOs3ZkSdNAwhZVriIna8lWb4iFHq8HXpm2snZJVHjpxj5gq5GSaaq5OjY5vE-8j7ZECzKIdcDJjzPR5m4mOs7B9mkfOQ=@proton.me> <87lepk4te0.fsf@web.de> <87r0zcn13o.fsf@web.de> <87k053xa5g.fsf@dataswamp.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25721"; mail-complaints-to="usenet@ciao.gmane.io" Cc: help-gnu-emacs@gnu.org To: Emanuel Berg Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Fri Oct 14 20:30:49 2022 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1ojPSJ-0006Sx-Ih for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Oct 2022 20:30:47 +0200 Original-Received: from localhost ([::1]:56466 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ojPSI-0004nV-4o for geh-help-gnu-emacs@m.gmane-mx.org; Fri, 14 Oct 2022 14:30:46 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37200) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojPQr-0004mT-Sh for help-gnu-emacs@gnu.org; Fri, 14 Oct 2022 14:29:19 -0400 Original-Received: from mail-40130.protonmail.ch ([185.70.40.130]:33453) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ojPQo-00073G-0H for help-gnu-emacs@gnu.org; Fri, 14 Oct 2022 14:29:17 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=proton.me; s=protonmail; t=1665772148; x=1666031348; bh=tlhFWAEB8Usn1zY32iABrkDU3xI7XWAmEatyc5R/mQE=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID; b=E/oV3xSGPEQVvbbwvjw2jXZXsHekEOYEB2ydNk2ve1mT26rWraL3zZ5dPmnFy8GAx s38lZ9vyoSax0TYo4cpv69e/53yYML031t9M6JQOl4Wlq993OL32q90RD3gh/2/EnB d3baIH5eG08vbeLldxz47firdwTRme2LWGGoTFU0dSEe8ALTJAHB046Kr+jjKJEy+V Ox+jcslR3UP19xGb7gG4vYdBWyWVLNAzMCpxVpiHfUdtbJBEH9qQKcRNpa0U6ihE4f +4tCH2wiuM6kngs+93DXuoVqFdwAFjMu5WEt438C4NYO2nBVGx473IN/lLkv/RXOli Q7z44VVAplYKA== In-Reply-To: <87k053xa5g.fsf@dataswamp.org> Feedback-ID: 52887082:user:proton Received-SPF: pass client-ip=185.70.40.130; envelope-from=uzibalqa@proton.me; helo=mail-40130.protonmail.ch X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:139945 Archived-At: ------- Original Message ------- On Friday, October 14th, 2022 at 5:10 AM, Emanuel Berg wrote: > Here is that old (2013-08-07) article again. >=20 > I understand it but not the 1-3 part, really? I wonder what > I is? >=20 > ~/.Xdefaults and ~/.Xresources >=20 > 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. >=20 > 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). >=20 > 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 Correct. I tested that, xrdb doesn't necessarily read "~/.Xresources". Would there be side effects if users customarily inhibit x resaurces. What happens when emacs utilises x resources and an emacs theme is enabled? =20 =20 > With Xresources any user can use, or not use, xrdb to > load settings. =20 > Xresources are mobile; compare to ~/.Xdefaults which hs to be > in $HOME. >=20 > To test the enhanced mobility, after reading resources with > xrdb, do the following: >=20 > 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! >=20 > 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. >=20 > 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. >=20 > Notes: >=20 > The #1 Google hit on this issue recommends making ~/.xinitrc > an executable, with 'chmod +x' - this is not needed. >=20 > 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 '&'. >=20 > Some xterm settings useful for testing: >=20 > xtermautoWrap: true > xtermpointerMode: 2 > xtermgeometry: 77x28 > xtermbackground: black > xtermforeground: green4 > xtermfaceName: default > xterm*metaSendsEscape: true >=20 > -- > underground experts united > https://dataswamp.org/~incal