* Vincent Lefevre <[EMAIL PROTECTED]> [2002-07-30 13:30]:
> On Tue, Jul 30, 2002 at 14:40:00 +0200, Sven Guckes wrote:
> > a better way is that of vim which includes the info
> > that the option/variable is only available when
> > some code is in binary as indicated by "+feature"
> > in the outut of the ":version" command.
>
> Yes, we should have something like that in Mutt.
anyone?
> And when it depends on the configuration,
> the default value shouldn't be given, as it
> may be wrong (this would confuse the user).
"it"?
anyway..
the default value should *always* be documented.
whether or not the code for the option is in
the mutt binary is another matter altogether.
besides - will mutt adopt option shortnames like vim?
example: "df" for display_filter
let me give an example:
Name: display_filter (short name: df)
Type: boolean, quadoption, number, path, regex, string;
email address, folder magic, sort order.
Default: "" (well, the default is empty for this option)
Requires: --configure-long-option-name
Description: blah blah blah..
Example:
set display_filter="/bin/sed -f $HOME/.mutt/display_filter.default.sed"
Note: Full pathname to filter program is required.
The shell magic '~' for $HOME is *not* evaluated,
but you can use $HOME instead.
additions, corrections, ideas?
Sven
