Darren Schroeder
Darren Schroeder
I'm not having issues. my variables seem to be colored right aka the default colors.  These are my colors with my theme. 
I'm guessing that this is a reedline issue versus a nushell issue.
I didn't think the `start` command was meant run executables, according to the help. ``` > help start Open a folder, file or website in the default application or viewer....
I'm trying to follow your instructions but `start anyfile.nu` doesn't work, so I'm not sure what this is supposed to do.
I got this working ```nushell open tmp.nu pwd out> tmp.txt open tmp2.nu let CUR = (pwd);cd ../;nu $"($CUR)/tmp.nu" nu tmp2.nu open ../tmp.txt # shows the correct ../ path ```
I could live with ``` ```
I'm not a real fan of block comments myself. It's easy enough in most editors to select the lines you want commented and hit the keyboard shortcut to comment them...
I'm not a fan of // and /* */ since we don't support either of those today.
I've always thought that we'd eventually have another sigil to indicate internal command just as `^` indicates external command. Perhaps `@` or `%` or `&`?
> Just had a thought that perhaps the command alternative might be more understandable, discoverable (since help can surface it), and flexible. ya, i think `command` would be more discoverable....