On 5/21/07, Axel Liljencrantz <[EMAIL PROTECTED]> wrote:
> On 5/21/07, Philip Ganchev <[EMAIL PROTECTED]> wrote:
> > The Fish parser treats any "$" character that is unquoted or quoted
> > inside double quotes as a variable reference. Unfortunately, the user
> > may try to use "$" in a regexp inside double quotes. For example:
[...]
> > I'm not sure why the command substitution part is useful.
>
> Because one common way to trigger this $-related errors is by using
> posix-style command substitutions like '$(ls)'. But fish has a special
> cased error message for that situation, so the general error no longer
> needs to mention this. Feel free to send a suggested new wording.
How about:
fish: Incorrect variable reference. The "$" character is used to
access a variable if it is unquoted or inside double quotes ("), but
not single quotes ('). To learn about variables, type "help
variables".
> Agreed, operators like $ are less descriptive than using full commands
> except in the few cases where the meaning of the operator is
> _extremely_ common, like using '+' for addition. It's a tradeoff.
Sure. I guess using a builtin appeases my urge for consistency and my
rebel side.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users
