On Friday, July 7 at 12:29 PM, quoth Rocco Rutte:
- set: obviously set a new value - reset: reset to value given for first set - unset: remove definition - toggle: not allowedFor mutt, both reset and unset make the definition disappear and I wonder if there're cases where a reset for $my_ variables make sense.
Hmm. Personally, I think reset and unset should behave as they currently do in mutt. This is how the manual describes “reset”:
The reset command resets all given variables to the compile time defaults. If you reset the special variable all, all variables will reset to their system defaults.Now, while the difference between “system defaults” and “compile time defaults” isn’t clear, I think it is at least *consistent* to have reset be equivalent to unset for $my_ variables, since the “compile time default” value for a $my_ variable is non-existence.
That, and I can’t think of a reason I would need this alternate version of reset. :)
Oh, and while I’m thinking of it, there’s a typo in the manual here. A patch to fix it is attached.
~Kyle -- We are all worms, but I do believe I am a glow worm. -- Winston Churchill
--- muttrc.man.head.old 2006-07-07 11:02:58.000000000 -0400 +++ muttrc.man.head 2006-07-07 11:03:13.000000000 -0400 @@ -350,8 +350,8 @@ with a default answer of \(lqyes\(rq and default answer of \(lqno.\(rq .IP The \fBreset\fP command resets all given variables to the compile -time defaults. If you reset the special variabe \fBall\fP, all -variables will reset to their system defaults. +time defaults. If you reset the special variable \fBall\fP, all +variables will reset to their compile time defaults. .TP \fBsource\fP \fIfilename\fP The given file will be evaluated as a configuration file.
Attachment:
pgp6DMmK5YdFH.pgp
Description: PGP signature