Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Cc: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>, ding@gnus.org
Subject: Re: Can't start CVS gnus.
Date: Tue, 03 Dec 2002 16:04:55 +0100	[thread overview]
Message-ID: <84u1hvuors.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <20021203130346.GC15650@merlin.emma.line.org> (Matthias Andree's message of "Tue, 3 Dec 2002 14:03:46 +0100")

Matthias Andree <matthias.andree@gmx.de> writes:

> Kai Großjohann schrieb am Dienstag, den 03. Dezember 2002:
>
>> +;; Make sure it was the right mm-util.
>> +(unless (fboundp 'mm-guess-mime-charset)
>> +  (error "Wrong `mm-util' found in `load-path'.  Make sure the Gnus one is found first."))
>> +
>
> That's near-to-impossible to achieve on e. g. SuSE and their site
> scripts. "Make sure the Gnus one is loaded first" might be more to the
> point.

???  Usually, people do (require 'mm-util).  That searches through
load-path.  So the right one should come first.

Or do you mean that the sequence should be:

    Emacs starts
    Gnus gets added to load-path
    mm-util from Gnus gets loaded
    W3 gets added to load-path

This avoids loading the wrong one, of course.  But this is not a
solution, since it would require loading everything.  That would be
dog slow.

-- 
~/.signature is: umop ap!sdn    (Frank Nobis)



  reply	other threads:[~2002-12-03 15:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-25  0:13 Matthias Andree
2002-11-25  0:51 ` Matt Armstrong
2002-11-25  2:11   ` Matthias Andree
2002-11-25  7:43     ` Kai Großjohann
2002-11-25 20:40       ` Matthias Andree
2002-11-25 21:12         ` Raymond Scholz
2002-11-25 23:25           ` Matthias Andree
2002-11-26  7:23         ` Kai Großjohann
2002-11-26 13:37         ` Reiner Steib
2002-11-27  2:10           ` Matthias Andree
2002-11-27  7:51             ` Kai Großjohann
2002-11-29 12:38               ` Matthias Andree
2002-11-27  8:54             ` Reiner Steib
2002-11-29 12:39               ` Matthias Andree
2002-11-29 13:23                 ` Kai Großjohann
2002-11-29 21:54                   ` Matthias Andree
2002-11-30 17:31                     ` Kai Großjohann
2002-12-01 22:54                       ` Matthias Andree
2002-12-02  7:57                         ` Kai Großjohann
2002-12-02 20:10                           ` Matthias Andree
2002-12-03  7:22                             ` Kai Großjohann
2002-12-03 13:03                               ` Matthias Andree
2002-12-03 15:04                                 ` Kai Großjohann [this message]
2002-12-03 15:38                                   ` Matthias Andree
2002-12-03 15:57                                     ` Kai Großjohann
2002-12-03 20:47                                       ` Matthias Andree
2002-12-04  7:39                                         ` Kai Großjohann
2002-12-04 15:39                                           ` Matthias Andree
2002-12-04 16:20                                           ` Reiner Steib
2002-12-04  5:06                                     ` kgreiner
2002-12-03 22:06                               ` Matthias Andree

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=84u1hvuors.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@uni-duisburg.de \
    --cc=ding@gnus.org \
    --cc=ma@dt.e-technik.uni-dortmund.de \
    /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).