Re: mutt/2323: feature of creating personal my_variables should be documented
The following reply was made to PR mutt/2323; it has been noted by GNATS.
From: Rocco Rutte <pdmef@xxxxxxx>
To: Mutt Developers <mutt-dev@xxxxxxxx>, bug-any@xxxxxxxxxxxxx
Cc:
Subject: Re: mutt/2323: feature of creating personal my_variables should be
documented
Date: Fri, 7 Jul 2006 12:13:07 +0000
Hi,
* Christian Ebert [06-07-07 13:49:05 +0200] wrote:
>* Alain Bench on Friday, July 07, 2006 at 01:05:01 +0200:
>>| macro index <F42> '\
>>| <enter-command> set my_old_resolve=$resolve resolve=no<Enter>\
>>| ...multiple operations on one mail...\
>>| <enter-command> set resolve=$my_old_resolve &my_old_resolve<Enter>'
> ^
>I don't understand the &my_old_resolve.
>
>Why isn't
>
><enter-command> set resolve=$my_old_resolve<Enter>
>
>enough?
>
>What exactly does/means &my_old_resolve?
The fine manual has this to say:
"The reset command resets all given variables to the compile time
defaults (hopefully mentioned in this manual). If you use the command
set and prefix the variable with â??&â?? this has the same behavior as the
reset command."
And as 'reset' and 'unset' mean to remove the definition of $my_
variables, &my_old_resolve removes the definition.
bye, Rocco
--
:wq!