From: David Z Maze <dmaze@mit.edu>
To: info-gnus-english@gnu.org
Subject: Re: How do you select a server?... for gnus
Date: Thu, 21 Jun 2007 10:12:58 -0400 [thread overview]
Message-ID: <y68sl8lcs5x.fsf@contents-vnder-pressvre.mit.edu> (raw)
In-Reply-To: <rnsl8mtfrg.fsf@succubus.panacea.null.org>
Joel Reicher <joel@panacea.null.org> writes:
> Perhaps it's called .gnus.el instead? There was a name change, I
> think, but I'm not sure why.
Either .gnus or .gnus.el will work fine. If you have a .gnus.el, you
can byte-compile it, and your .gnus.elc will get used instead. But on
modern hardware, the minimal performance you'll get out of that isn't
worth the effort of actually running the byte-compile and the
aggravation of having an out-of-date copy used preferentially.
(I believe for similar reasons you could have a .emacs.el/.emacs.elc,
but don't really want to these days.)
--dzm
prev parent reply other threads:[~2007-06-21 14:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-14 20:05 thesak
2007-06-15 19:49 ` William F Hammond
2007-06-15 23:14 ` thesak
2007-06-16 9:13 ` Dick Hoogendijk
2007-06-20 7:54 ` Joel Reicher
2007-06-20 8:07 ` thesak
2007-06-20 9:06 ` Glyn Millington
2007-06-20 22:36 ` Joel Reicher
2007-06-21 14:12 ` David Z Maze [this message]
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=y68sl8lcs5x.fsf@contents-vnder-pressvre.mit.edu \
--to=dmaze@mit.edu \
--cc=info-gnus-english@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 NNTP newsgroup(s).