Valgrind
-
Look at you going all fancy. All I did was install powershell (and even that was mostly for the
vimaddons)
I need to up my game methinks.
-
I relatively frequently have paths extend for more than half the width of the terminal.
I do like
fish's solution to that:—————————————————————————————————————————————————————————————————————— 15:45:43 kane@kane-laptop [~/projects/Applied-Energistics-2/src/main/java/appeng/me] $ vim Grid.java —————————————————————————————————————————————————————————————————————— 15:45:53 kane@kane-laptop [~/projects/Applied-Energistics-2/src/main/java/appeng/me] $ fish Welcome to fish, the friendly interactive shell Type help for instructions on how to use fish kane@kane-laptop ~/p/A/s/m/j/a/me>
-
Depends whether root's init scripts override the shell. Not at a linux box right now.
They do.I do like fish's solution to that:
I don't. Matter of preference.
-
Same here, I don't have a problem with the path extending halfway across the screen. But when my ad-hoc shell scripts already wrap lines twice, and I change working directories at some point, I can lose track of what part of the script is doing what.
-
I do like fish's solution to that
I don't. I have way too many directories that start with the same first letter for that to be useful for me:
/proj/gpfs/user/user_project_dev_num/vproject/...
Everything that tells me the most important thing, which project I'm working on in that window, starts with the same letter. Not to mention that all the projects start with the same prefix.
-
I don't. I have way too many directories that start with the same first letter for that to be useful for me
I use
\h:\W \u\$as my prompt (in bash). It gives the key things I need to know — what machine, what directory (just the last part though; I canpwdif I need more) and what user — without taking lots of space.
-
Mine:
$ echo "'$PS1'" '\u:${PRODUCT_SPECIFIC_VAR:--}@\h(${PRODUCT_SPECIFIC_VAR_2:--}):\w\n\$ '
