* Vincent Lefevre <[EMAIL PROTECTED]> [07-31-02 21:25]:
> On Wed, Jul 31, 2002 at 21:14:18 -0500, Patrick wrote:
> > * Vincent Lefevre <[EMAIL PROTECTED]> [07-31-02 21:04]:
> > > On Thu, Aug 01, 2002 at 02:09:18 +0200, Sven Guckes wrote:
> > > > * Vincent Lefevre <[EMAIL PROTECTED]> [2002-07-31 21:03]:
> > > > > > so the solution is: extend the manual with more information!
> > > > > > eg "Default: "/path/file" (unless specified by --some-option)"
> > > > > The user doesn't necessarily know what options have
> > > > > been used, so this is a bad idea to say that.
> > > >
> > > > i disagree. the manual should include a section which
> > > > tells the user how to check for such information.
> > >
> > > And how can one find the options used to compile Mutt?
> >
> > Guess you should read the informational files included in the
> > tarball/rpm. They are detailed in the INSTALL file of every mutt
> > version I have ever seen.
>
> You are not answering my question.
You are not reading the post. Paragraph above says: They are detailed
in the INSTALL file of every mutt version I have ever seen
(tarball/rpm).
Partial quote from 1.4i:
In most cases, configure will automatically determine everything it
needs to know in order to compile. However, there are a few options
to `configure'' to help it out, or change the default behavior:
--prefix=DIR
install Mutt in DIR instead of /usr/local
--with-curses=DIR
use the curses lib in DIR/lib. If you have ncurses, `configure''
will automatically look in /usr/include/ncurses for the include
files.
--with-slang[=DIR]
use the S-Lang library instead of ncurses. This library seems to
work better for some people because it is less picky about proper
termcap entries than ncurses. It is recommended that you use at
*least* version 0.99-38 with Mutt.
If you need to know more of the config options, you will need to read
the file yourself.
Help yourself, it's good to be inquisitive. hagd,
--
Patrick Shanahan
Registered Linux User #207535
@ http://counter.li.org
