From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: New Gnus and Exchange 2003 - Usable?
Date: Thu, 30 Sep 2010 09:40:25 +0200 [thread overview]
Message-ID: <yb0zkuzsmqe.fsf@dod.no> (raw)
In-Reply-To: <87ocbf7lzf.fsf@marauder.physik.uni-ulm.de>
>>>>> Reiner Steib <reinersteib+gmane@imap.cc>:
> On Wed, Sep 29 2010, Steinar Bang wrote:
>> ;; Are we running XEmacs or Emacs?
>> (defvar running-xemacs (string-match "XEmacs\\|Lucid" (emacs-version))
>> "Hold a numerical value if this is XEmacs, nil if it isn't")
> I'd recommend (featurep 'xemacs) instead.
Ok. My .emacs file has... er... lots of history in it. The reference
to "Lucid", is a clue...:-)
Parts of it goes back to 18.55 in 1989. I'm not entirely sure, because
I didn't start version controlling it until 1997, and the current
history doesn't go further back than 2001.
next prev parent reply other threads:[~2010-09-30 7:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-29 13:06 Jake Colman
2010-09-29 13:56 ` Robert Pluim
2010-09-29 18:04 ` Steinar Bang
2010-09-30 7:02 ` Reiner Steib
2010-09-30 7:40 ` Steinar Bang [this message]
2010-09-30 7:48 ` Steinar Bang
2010-10-03 11:35 ` Tibor Simko
2010-10-05 18:07 ` Tibor Simko
2010-09-29 16:46 ` Ted Zlatanov
2010-10-03 1:50 ` Jake Colman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yb0zkuzsmqe.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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 NNTP newsgroup(s).