From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Gnus v5.4.1 is released
Date: 26 Jan 1997 06:58:04 +0100 [thread overview]
Message-ID: <m2d8ut3rmb.fsf@proletcult.slip.ifi.uio.no> (raw)
In-Reply-To: Randal Schwartz's message of 25 Jan 1997 21:50:59 -0700
Randal Schwartz <merlyn@stonehenge.com> writes:
> 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?
The easiest would probably just be to byte-compile that file manually
(uhm -- not doing the actual byte-compiling manually, :-) but `M-x
byte-compile-file'). Or you could push the w3 dir onto the load-path
in the dgnushack.el file.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@ifi.uio.no * Lars Ingebrigtsen
next prev parent reply other threads:[~1997-01-26 5:58 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 [this message]
1997-01-27 14:18 ` Brent B. Powers
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=m2d8ut3rmb.fsf@proletcult.slip.ifi.uio.no \
--to=larsi@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).