Re:macOS deprecating scripting language runtimes, including ...
by wyufro on Thursday June 06, 2019 @03:37AM
(#20112358)
Just that the prompt automatically goes on a new line makes iTerm2 so nice though. As well as the built in timing of commands, jump to previous prompt, double click selects matching parentheses, etc. it's those little details.
[ Parent
| on HN ]
Re:macOS deprecating scripting language runtimes, including ...
by coldtea on Thursday June 06, 2019 @04:30AM
(#20112636)
>Just that the prompt automatically goes on a new line makes iTerm2 so nice though.
Not sure what you mean here, but I don't think that's something you don't get, or can't get, on Terminal.app. In fact, that's the default...
Re:macOS deprecating scripting language runtimes, including ...
by saagarjha on Thursday June 06, 2019 @04:48AM
(#20112708)
If you have a command that doesn't print a new line, the prompt normally ends up on the same line as the output of the last command. iTerm can "fix" this.
Re:macOS deprecating scripting language runtimes, including ...
by skohan on Thursday June 06, 2019 @05:52AM
(#20112995)
See this is where I would rather have my terminal obey the program rather than imposing its own behavior. IMO a good terminal should be extremely minimal, and anything extra should be opt-in.
Re:macOS deprecating scripting language runtimes, including ...
by snazz on Thursday June 06, 2019 @08:04AM
(#20113666)
Don’t shells usually fix this? I know that Fish at least includes a little Unicode “return” arrow when it appends a newline.