Run the following to see your PATH settings in easy to read format on screen:
```
tr ":" "\n" <<<"$PATH"
tr ":" "\n" <<<"$PATH" | lolcat
```
This is a little more portable
```
echo "$PATH" | tr ":" "\n"
echo "$PATH" | tr ":" "\n" | lolcat
```

#unix #linux

@nixCraft pipe together toilet and lolcat

@nixCraft Nice tr command, thanks!

But you might want to remove the extra 'o' from 'lolocat'. (Debian, at least, doesn't have a lolocat; I haven't tried installing lolcat because I don't know what it does and it has a bunch of ruby dependencies.)

@akkana fixed it. it was a typo on my part.

@nixCraft

'lolcat' needs 18 dependencies with a total size of 46,2 MB , lol no thanks.

@nixCraft ok, thanks to you I installed this and then also remembered to reinstall fortune and cowsay :)
#linux

@nixCraft Hi.

I love tr but I love pure Bash even more:

IFS=':' read -r -a path_parts <<< "$PATH"; printf '%s\n' "${path_parts[@]}"

By the way, get ready for every opinionated sysadmin to post here, we are wired that way :-D

Thanks for sharing.

@josevnz

Looks complex. (-:

C shell:

% printf '%s\n' $path

Z shell:

% printf '%q\n' "$path[@]"

#UnixShells #CShell #ZShell #zsh #csh

@JdeBP @josevnz Yeah, IFS for just that makes it needlessly complex when it can also be like this:

ksh, mksh, zsh: $ echo ${PATH//:/\\n}

ksh, mksh, bash, yash, busybox sh, sash: $ echo "${PATH//:/$'\n'}"

@lanodan @JdeBP Oh yeah, I forgot about the Bash regex substitution. Yeah, this is the best solution.
@nixCraft Thanks!!!
It turns out I had duplicate entries in $PATH