Keep in mind this isn't about putting literal spaces into a script - it's about preserving spaces returned by identifiers or in variables. Edit: oh I see what you mean. Such a $space would be much harder to implement though, if possible at all. Right now, the command line parser first evaluates the line, and then tokenizes it. Support for $space would basically require the evaluation routine to provide feedback to its caller on the byte ranges that are to have their spaces preserved, which would then have to be taken into account by the tokenizer. This is somewhat messy and I'm not exactly sure what would be gained by such flexibility either. Then again I'd be happy with it anyhow of course.
Screw people who make custom aliases that start with a ^, though.
Last edited by Sat; 14/08/15 09:46 AM.
