From: don provan <dprovan@comcast.net>
Subject: Re: X Resources?
Date: 14 May 2005 00:16:27 -0700 [thread overview]
Message-ID: <uis1mqnuc.fsf@comcast.net> (raw)
In-Reply-To: 4284e503_2@news1.prserv.net
kgold@watson.ibm.com (kgold) writes:
> I avoid using X resources whenever possible, as I try to share my
> .emacs between Windows and Unix machines.
Funny you should mention that: I also share my .emacs between various
systems, which is exactly why I use X resources: I give emacs (as well
as other applications) different color schemes depending on where the
application is running to help me keep them straight. You can do that
in .emacs, of course, but the X resources on the source node is the
obvious place.
-don provan
next prev parent reply other threads:[~2005-05-14 7:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5003.1115967988.2819.help-gnu-emacs@gnu.org>
2005-05-13 7:33 ` X Resources? Stefan Monnier
2005-05-13 17:33 ` kgold
2005-05-14 7:16 ` don provan [this message]
2005-05-16 5:51 ` Dhruva Krishnamurthy
2005-05-19 7:40 ` don provan
2005-10-31 18:30 ` Susan Pinochet
2005-05-13 7:01 Greg Novak
2005-05-13 8:35 ` Peter Dyballa
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=uis1mqnuc.fsf@comcast.net \
--to=dprovan@comcast.net \
/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).