Re: changeset 5920 / manual.xml.head

2009-06-23 Thread Rocco Rutte
Hi, * Vincent Lefevre wrote: > First, there's a small typo: mutt -> Mutt. Good catch. > Also, I'd say simply (if I understand correctly): > In case of parsing errors, Mutt will print error messages. Done, thanks. Rocco

Re: changeset 5920 / manual.xml.head

2009-06-23 Thread Rocco Rutte
Hi, * Vincent Lefevre wrote: > No, the fact that it seems to work doesn't mean that it is allowed. > Never use undocumented features! Well, actually this is documented for years (4713:9f3afe005e3d). Rocco

Re: changeset 5920 / manual.xml.head

2009-06-22 Thread Vincent Lefevre
Hi, On 2009-06-20 15:26:49 +0200, Rocco Rutte wrote: > I've tried to clarified the issue and extended it a bit because the > conversion rule (type1 <-> string <-> type2) applies to all commands. Thanks. This is much better... except In case of parsing errors, mutt will print error messages as

Re: changeset 5920 / manual.xml.head

2009-06-21 Thread Cameron Simpson
On 20Jun2009 11:51, Vincent Lefevre wrote: | On 2009-06-19 23:43:24 +0200, Rocco Rutte wrote: | > * Vincent Lefevre wrote: | > > Whenever a user-defined variable is used in an assignment for a built-in | > > variable or vice versa, Mutt string representations to do the | > > assignment. As a

Re: changeset 5920 / manual.xml.head

2009-06-21 Thread Cameron Simpson
On 20Jun2009 07:59, Patrick Shanahan wrote: | * Vincent Lefevre [06-20-09 05:52]: | > Are these the only possibly assignments? Isn't it possible to do: | > set my_foo=$my_bar | > or | > set status_format="-%r-Mutt: %f...%>-(%P)-$timeout--" | | Very simple to determine yourself, just try it!

Re: changeset 5920 / manual.xml.head

2009-06-21 Thread Vincent Lefevre
On 2009-06-20 07:59:04 -0400, Patrick Shanahan wrote: > * Vincent Lefevre [06-20-09 05:52]: > > Are these the only possibly assignments? Isn't it possible to do: > > > > set my_foo=$my_bar > > > > or > > > > set status_format="-%r-Mutt: %f...%>-(%P)-$timeout--" > > Very simple to determine

Re: changeset 5920 / manual.xml.head

2009-06-20 Thread Rocco Rutte
Hi, * Vincent Lefevre wrote: > On 2009-06-19 23:43:24 +0200, Rocco Rutte wrote: > Are these the only possibly assignments? Isn't it possible to do: > set my_foo=$my_bar > or > set status_format="-%r-Mutt: %f...%>-(%P)-$timeout--" I guess you know the answer just as we all do. Nevertheless

Re: changeset 5920 / manual.xml.head

2009-06-20 Thread Patrick Shanahan
* Vincent Lefevre [06-20-09 05:52]: > > Are these the only possibly assignments? Isn't it possible to do: > > set my_foo=$my_bar > > or > > set status_format="-%r-Mutt: %f...%>-(%P)-$timeout--" Very simple to determine yourself, just try it! -- Patrick Shanahan Plainfield, Indi

Re: changeset 5920 / manual.xml.head

2009-06-20 Thread Vincent Lefevre
Hi, On 2009-06-19 23:43:24 +0200, Rocco Rutte wrote: > * Vincent Lefevre wrote: > > Whenever a user-defined variable is used in an assignment for a built-in > > variable or vice versa, Mutt string representations to do the > > assignment. As a result, a user-defined variable can be assigned

Re: changeset 5920 / manual.xml.head

2009-06-19 Thread Rocco Rutte
Hi, * Vincent Lefevre wrote: > Whenever a user-defined variable is used in an assignment for a built-in > variable or vice versa, Mutt string representations to do the > assignment. As a result, a user-defined variable can be assigned to any > other variable under the restriction that its

changeset 5920 / manual.xml.head

2009-06-19 Thread Vincent Lefevre
A paragraph added in r5920 in doc/manual.xml.head: Whenever a user-defined variable is used in an assignment for a built-in variable or vice versa, Mutt string representations to do the assignment. As a result, a user-defined variable can be assigned to any other variable under the restric