From: Emanuel Berg <embe8573@student.uu.se>
To: help-gnu-emacs@gnu.org
Subject: Re: Sanest way to make emacs behave on a Solaris OS
Date: Tue, 06 Aug 2013 00:04:17 +0200 [thread overview]
Message-ID: <87li4fu74u.fsf@VLAN-3434.student.uu.se> (raw)
In-Reply-To: mailman.2569.1375733828.12400.help-gnu-emacs@gnu.org
Bob Proulx <bob@proulx.com> writes:
> xrdb -m ~/.Xresources
>
> The -m merges. The -l loads. I selected merging because you
> may have sevaral files all merged together so this would only
> change what you changed. Using -l would empty first and then
> only load that file so if you had several files, perhaps a
> /etc/X11/something, then that other would be lost. But I will
> use -l when I want only what is in that file, nothing more and
> nothing less, and want to avoid anything else that might have
> been set elsewhere. Somewhat like the emacs -Q of things.
Interesting. I have
xrdb ~/.Xresources
as the first line of .xinitrc - which is read after 'xinit', in
.zprofile (of zsh).
Without an operation (like -merge or -load, or -m/-l) the default
operation is -all, according to the man page. But what that means,
is not the easiest thing to understand, even with the man page:
> This option indicates that operation should be performed on the
> screen-independent resource property (RESOURCE_MANAGER), as well
> as the screen-specific prop‐ erty (SCREEN_RESOURCES) on every
> screen of the display. For example, when used in conjunction
> with -query, the contents of all properties are output. For
> -load, -override and -merge, the input file is processed once
> for each screen. The resources which occur in common in the
> output for every screen are collected, and these are applied as
> the screen-independent resources. The remaining resources are
> applied for each individual per- screen property. This the
> default mode of operation.
I used it the same way when I did my experimentation on Solaris:
that is, without any operation.
--
Emanuel Berg - programmer (hire me! CV below)
computer projects: http://user.it.uu.se/~embe8573
internet activity: http://home.student.uu.se/embe8573
next prev parent reply other threads:[~2013-08-05 22:04 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.2072.1375151019.12400.help-gnu-emacs@gnu.org>
2013-07-30 2:32 ` Sanest way to make emacs behave on a Solaris OS Dan Espen
2013-07-29 18:18 ` Harry Putnam
[not found] ` <mailman.2176.1375205273.12400.help-gnu-emacs@gnu.org>
2013-07-30 18:00 ` Dan Espen
2013-07-30 18:16 ` Emanuel Berg
2013-07-31 3:23 ` Harry Putnam
[not found] ` <mailman.2199.1375241187.12400.help-gnu-emacs@gnu.org>
2013-07-31 17:55 ` Emanuel Berg
2013-07-31 18:26 ` Emanuel Berg
2013-08-02 12:48 ` Harry Putnam
2013-08-03 7:03 ` Bob Proulx
2013-08-05 2:32 ` Harry Putnam
2013-08-05 2:51 ` Stefan Monnier
[not found] ` <mailman.2500.1375671147.12400.help-gnu-emacs@gnu.org>
2013-08-05 7:59 ` Emanuel Berg
2013-08-05 13:43 ` Stefan Monnier
2013-08-04 5:32 ` Harry Putnam
2013-08-05 22:40 ` Stefan Monnier
2013-08-04 10:35 ` Harry Putnam
2013-08-06 5:49 ` Bob Proulx
2013-08-06 12:52 ` Harry Putnam
2013-08-06 13:09 ` Peter Dyballa
[not found] ` <mailman.2603.1375794577.12400.help-gnu-emacs@gnu.org>
2013-08-06 21:33 ` Emanuel Berg
2013-08-05 13:55 ` Dan Espen
2013-08-05 20:16 ` Bob Proulx
2013-08-04 10:10 ` Harry Putnam
[not found] ` <mailman.2580.1375742208.12400.help-gnu-emacs@gnu.org>
2013-08-05 22:47 ` Emanuel Berg
[not found] ` <mailman.2569.1375733828.12400.help-gnu-emacs@gnu.org>
2013-08-05 22:04 ` Emanuel Berg [this message]
2013-08-05 22:29 ` Bob Proulx
[not found] ` <mailman.2579.1375741786.12400.help-gnu-emacs@gnu.org>
2013-08-05 22:44 ` Emanuel Berg
[not found] ` <mailman.2498.1375670121.12400.help-gnu-emacs@gnu.org>
2013-08-05 7:58 ` Emanuel Berg
2013-08-05 14:48 ` Eli Zaretskii
[not found] ` <mailman.2536.1375714107.12400.help-gnu-emacs@gnu.org>
2013-08-05 15:32 ` Dan Espen
2013-08-05 16:50 ` Eli Zaretskii
2013-08-05 18:03 ` Emanuel Berg
2013-08-05 18:51 ` Dan Espen
2013-08-05 17:51 ` Emanuel Berg
2013-08-05 18:23 ` Eli Zaretskii
2013-08-05 19:25 ` Óscar Fuentes
[not found] ` <mailman.2559.1375730782.12400.help-gnu-emacs@gnu.org>
2013-08-05 22:23 ` Emanuel Berg
[not found] ` <mailman.2552.1375727048.12400.help-gnu-emacs@gnu.org>
2013-08-05 18:25 ` Emanuel Berg
2013-08-05 19:03 ` Eli Zaretskii
[not found] ` <mailman.2419.1375513430.12400.help-gnu-emacs@gnu.org>
2013-08-03 10:42 ` Emanuel Berg
2013-08-05 20:04 ` Bob Proulx
[not found] ` <mailman.2567.1375733090.12400.help-gnu-emacs@gnu.org>
2013-08-05 21:53 ` Emanuel Berg
2013-08-05 23:21 ` Emanuel Berg
2013-08-05 23:41 ` Dan Espen
2013-08-06 5:54 ` Bob Proulx
2013-08-06 21:15 ` Emanuel Berg
2013-08-07 0:38 ` Dan Espen
2013-08-07 12:06 ` Emanuel Berg
2013-08-08 15:36 ` Emanuel Berg
2013-08-07 0:22 ` Emanuel Berg
2013-08-08 15:43 ` Emanuel Berg
2013-08-08 18:08 ` Dan Espen
2013-08-08 20:19 ` Emanuel Berg
[not found] ` <mailman.2372.1375447876.12400.help-gnu-emacs@gnu.org>
2013-08-02 18:34 ` Emanuel Berg
2013-08-02 13:02 ` Harry Putnam
[not found] ` <mailman.2374.1375448728.12400.help-gnu-emacs@gnu.org>
2013-08-02 18:39 ` Emanuel Berg
2013-08-02 19:12 ` Emanuel Berg
2013-08-02 18:52 ` Emanuel Berg
2013-08-02 19:32 ` Emanuel Berg
2013-07-30 2:20 Harry Putnam
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=87li4fu74u.fsf@VLAN-3434.student.uu.se \
--to=embe8573@student.uu.se \
--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).