From: Leon <sdl.web@gmail.com>
Subject: Re: bundle no gnus with emacs CVS
Date: Fri, 28 Apr 2006 00:34:20 +0100 [thread overview]
Message-ID: <m2k69ak2yr.fsf@sl392.st-edmunds.cam.ac.uk> (raw)
In-Reply-To: <v9vesu90ko.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <reinersteib+gmane@imap.cc> writes:
> On Thu, Apr 27 2006, Leon wrote:
>
>> gdt@work.lexort.com writes:
> [...]
>>> (setq load-path
>>> (cons (expand-file-name "~/SOFTWARE/GNUS/gnus/lisp") load-path))
>>> (require 'gnus-load)
> [...]
>> I have used gnus this way before. But I am thinking about
>> bundling it in emacs.
>
> Maybe you should explain what you mean with "bundling it in emacs".
>
> Bye, Reiner.
I want to upgrade gnus in my local emacs cvs tree to No Gnus. But I
don't know how to cleanly do this i.e. can I just upgrade lisp/gnus to
the latest gnus.
Cheers,
--
Leon
next prev parent reply other threads:[~2006-04-27 23:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 16:56 Leon
2006-04-27 17:00 ` gdt
2006-04-27 17:24 ` Leon
2006-04-27 21:21 ` Reiner Steib
2006-04-27 23:34 ` Leon [this message]
2006-04-28 7:48 ` Steinar Bang
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=m2k69ak2yr.fsf@sl392.st-edmunds.cam.ac.uk \
--to=sdl.web@gmail.com \
/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).