Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Ian Soboroff <org@acm.isoboroff>
Subject: Re: Migration to Oort, void url-register-protocol
Date: Tue, 05 Nov 2002 13:23:06 -0500	[thread overview]
Message-ID: <9cfheevooz9.fsf@rogue.ncsl.nist.gov> (raw)
In-Reply-To: <873cqfvqx0.fsf@enberg.org>

Henrik Enberg <henrik+news@enberg.org> writes:

> Ian Soboroff <org@acm.isoboroff> writes:
>
>> I don't find this name anywhere in url, but it seems to be in my w3
>> code.  My w3 is w3-4.0pre.47, which last I looked was the
>> latest.
>
> You probably need w3 from CVS as well.  Get it from
> <http://savannah.gnu.org>

That fixed it, except it seems that ssl.el in w3 CVS is broken... I
couldn't connect to my IMAP server until I copied over and compiled
the old ssl.el.

ian


      reply	other threads:[~2002-11-05 18:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9cfel9zoqee.fsf@rogue.ncsl.nist.gov>
2002-11-05 17:59 ` Henrik Enberg
2002-11-05 18:23   ` Ian Soboroff [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=9cfheevooz9.fsf@rogue.ncsl.nist.gov \
    --to=org@acm.isoboroff \
    /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).