From: Steve Youngs <sryoungs@bigpond.net.au>
Subject: Re: void-function fill-flowed
Date: Fri, 24 Oct 2003 03:43:16 +1000 [thread overview]
Message-ID: <microsoft-free.87oew7n93f.fsf@eicq.dnsalias.org> (raw)
In-Reply-To: <4n4qy0kjvn.fsf@lockgroove.bwh.harvard.edu>
[-- Attachment #1: Type: text/plain, Size: 916 bytes --]
|--==> "TZ" == Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> On Thu, 23 Oct 2003, jas@extundo.com wrote:
>>Adding (require 'gnus-load) to gnus.el still seem useful, but
>>orthogonal to the flow-fill autoload issue.
TZ> please let's add gnus-load.el to the gnus.el requires.
Please don't. It will cause havoc for XEmacs users. In my own
personal set up I go so far as to delete gnus-load.el. I can safely
do this because I set Gnus up properly with 'auto-autoloads.el' and
'custom-load.el' files. I've been meaning to patch the build
procedure so that these two files are created _instead of_
gnus-load.el when building with XEmacs.
--
|---<Steve Youngs>---------------<GnuPG KeyID: A94B3003>---|
| Ashes to ashes, dust to dust. |
| The proof of the pudding, is under the crust. |
|------------------------------<sryoungs@bigpond.net.au>---|
[-- Attachment #2: Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2003-10-23 17:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-23 9:26 Norbert Koch
2003-10-23 9:30 ` Simon Josefsson
2003-10-23 9:48 ` Katsumi Yamaoka
2003-10-23 12:12 ` Simon Josefsson
2003-10-23 11:25 ` Norbert Koch
2003-10-23 12:17 ` Simon Josefsson
2003-10-23 12:40 ` Norbert Koch
2003-10-23 12:57 ` Simon Josefsson
2003-10-23 13:30 ` Norbert Koch
2003-10-23 14:36 ` Norbert Koch
2003-10-23 14:42 ` Simon Josefsson
2003-10-23 16:18 ` Ted Zlatanov
2003-10-23 16:44 ` Simon Josefsson
2003-10-23 17:43 ` Steve Youngs [this message]
2003-10-23 18:13 ` Simon Josefsson
2003-10-23 21:20 ` Steve Youngs
2003-10-23 19:32 ` Ted Zlatanov
2003-10-23 21:33 ` Steve Youngs
2003-10-23 22:37 ` Ted Zlatanov
2003-10-24 3:58 ` Steve Youngs
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=microsoft-free.87oew7n93f.fsf@eicq.dnsalias.org \
--to=sryoungs@bigpond.net.au \
/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).