Re: leading whitespace & alias/command expansion

On Thu, 2004-12-23 at 10:00, will guaraldi wrote:
> Out of curiosity, why do you have commands with whitespace in front of 
> them?  Is it a typo issue or are you trying to do something else that is 
> causing problems?  Where's this problem stemming from?

If I want to string several commands together, it's nice to be able to
stick a space in after the ';' so that it is slightly easier to read, or
so that it is more forgiving of typos if i need to do whatever it is
quickly.

# this line would not have worked before (at least not as expected)
/alias {ineedtodothisquickly} { alias1;alias2; /somecommand;/5 say
hi;/test}

The only problem that I can see with this is where a command or alias is
the same as a mud command, then stripping leading whitespace would
prevent one from dealing with the conflict by using a leading space to
send the mud command and no leading space to excute the lyntin
command/alias. Of course the whole whitespace thing could be made
configurable to allow folks to choose for themselves.

-davidc




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/