4 ms·
As the path can be long, I do this: a first line for the things the shell want to displays, a second line for the things I type # (user@server):/where/I/am #
by 1996 6y ago
As the path can be long, I do this: a first line for the things the shell want to displays, a second line for the things I type
# (user@server):/where/I/am
#
This gives something like
# (user@server):/where/I/am
# cd now
# (user@server):/where/I/am/now
#
The # is used because I sometimes copy-paste, and I want to avoid problems
- Tyr42 6y agoI use the same pattern, if only because I've not mastered the art of naming directories with clear and short names, so my $PWD tends to get rather long. Add in any git nonsense, and I end up line wrapping anyways. Much cleaner to always put a newline after the $PWD
- roelschroeven 6y agoSame here (except the #). The advantage is not only that it prevents problems with very long paths and/or commands, but it also makes every command I type start at the same offset from the left, irrespective of the length of the path. Much cleaner that way, IMO.