🚀 go-pugleaf

In article <danpop.807749170@rscernix>, Dan.Pop@mail.cern.ch (Dan Pop) wrote:

> >well as if your .elm/elmrc is commented.
>       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> Pushing this idiocy a little bit further: the menus have to be read, too.
> Reading the menus counts as reading the documentation.

Only if I have to use Balloon Help on them.  There is a difference between
seeing a line that reads:

timeout = 10

and

# timeout
#
# On more advanced systems, it's nice to start up the
# mailer in a window and let it sit in background
# unless new mail arrives (see wnewmail for
# another window based program) at which point
# it can be brought up to the forefront of the system
# and read.  In this case, it would be quite convenient
# to have the mailer internally resynchronize every
# so often.  This option specifies the number of seconds that this occurs.
# This is also useful for normal terminals, for example you can
# leave elm running at night (I usually do) and when you
# come in in the morning it'll be all ready to read your mail!
# (The default is a 300 second (5 minute) timeout period).

timeout = 10


Since you seem to be such an elm guru, how come elm screws up if I set
timeout = 1?  It certainly isn't documented anywhere.


Plus, with most menu options, I can figure them out by just trying them. 
How can you do that with parameters like timeout, if they are
undocumented?
-- 
        Nevin ":-)" Liber       nevin@CS.Arizona.EDU    (520) 293-2799
                                                office: (520) 621-1815