Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Question about gnus-picon
Date: 05 Dec 1998 17:03:46 +0100	[thread overview]
Message-ID: <m3k9068tjx.fsf@sparky.gnus.org> (raw)
In-Reply-To: Christian Kurz's message of "04 Dec 1998 07:42:28 +0100"

Christian Kurz <shorty@jupiter.rhein-neckar.de> writes:

> This solved this problem. But no I get the following message during the
> compilation:

[...]

> The problem is, that I haven't installed w3 and I don't want to install
> it just because gnus needs it.

You don't need w3.  Just ignore the warnings.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen


      reply	other threads:[~1998-12-05 16:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1998-12-02 21:48 Christian Kurz
1998-12-03 11:49 ` Lars Magne Ingebrigtsen
1998-12-03 17:10   ` Christian Kurz
1998-12-04  2:10     ` Lars Magne Ingebrigtsen
1998-12-04  6:42       ` Christian Kurz
1998-12-05 16:03         ` Lars Magne Ingebrigtsen [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=m3k9068tjx.fsf@sparky.gnus.org \
    --to=larsi@gnus.org \
    /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).