From: "Brent B. Powers" <powers@ml.com>
Cc: ding@ifi.uio.no
Subject: Re: Gnus v5.4.1 is released
Date: Mon, 27 Jan 1997 09:18:08 -0500 [thread overview]
Message-ID: <199701271418.JAA02296@swapsdvlp02.ny-swaps-develop.ml.com> (raw)
In-Reply-To: <8cpvyt11l8.fsf@gadget.cscaper.com>
Randal Schwartz writes:
> From: Randal Schwartz <merlyn@stonehenge.com>
> To: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
> Subject: Re: Gnus v5.4.1 is released
> Date: 25 Jan 1997 21:50:59 -0700
>
> >>>>> "Lars" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
>
> Lars> Randal Schwartz <merlyn@stonehenge.com> writes:
> >> I get these errors during build. Ick. Note in particular the "w3"
> >> error. I presume that means that nnweb won't work.
>
> Lars> Yes, nnweb needs w3 to work.
>
> Right. I have w3 in the loadpath at runtime (thanks to my personal
> ".emacs"), but since you load emacs -q, it doesn't show up at
> *bytecompile* time. And that seems to break things.
>
> What am I to do? What handle do I need to jiggle?
>
I also do a separate vm/gnus xemacs, which doesn't load .emacs, so I
do most of the manipulation of the loadpath in .vm or .gnus. However,
I still need to make sure that my personal copy of vm gets loaded, so
when I call it, I call it as:
xemacs -q -eval '(setq load-path (cons "/home/powers/lib/emacs/vm" load-path))' -funcall vm -iconic -geometry 100x55+250+45&
next prev parent reply other threads:[~1997-01-27 14:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-25 11:18 Lars Magne Ingebrigtsen
1997-01-25 15:33 ` Randal Schwartz
1997-01-25 15:57 ` Lars Magne Ingebrigtsen
1997-01-26 4:50 ` Randal Schwartz
1997-01-26 5:58 ` Lars Magne Ingebrigtsen
1997-01-27 14:18 ` Brent B. Powers [this message]
1997-01-25 22:41 ` Steven L Baur
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=199701271418.JAA02296@swapsdvlp02.ny-swaps-develop.ml.com \
--to=powers@ml.com \
--cc=ding@ifi.uio.no \
/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).