Halloween Bash Profile Generator • Hacker News Board

Re: Halloween Bash Profile Generator

#21

Post by myhf » Wed, Oct 31, 2012, 7:30 PM UTC

michaelhoffman wrote: post #12

dllthomas wrote: post #10

Earlier quoted context omitted.

Interesting. I've been using $PIPESTATUS at the start of my prompt for a while now.

I use this, which allows a similar effect but is enabled for PIPESTATUS, and also does some good things for eterm and screen. PIPESTATUS_REGEX="^ +$" # check to see if any of the pipe statuses don't start with 0 # ${_CMD_PIPESTATUS[@]#0} results in null if they all do _PIPESTATUS=" _CMD_PIPESTATUS=(\${PIPESTATUS[@]}) if [[ \"\${_CMD_PIPESTATUS[*]#0}\" && ! \"\${_CMD_PIPESTATUS[*]#0}\" =~ \$PIPESTATUS_REGEX ]] then _R…

It's cool to also see the name of the signal that caused exit status > 128. Sadly this only fits in a tweet if it can assume the possible signal names are listed contiguously, which isn't so on 64-bit Linux these days.

  S=(`trap -l`);e(){ for N in ${PIPESTATUS[@]};do ((N>128))&&echo ${S[$((2*N-257))]}||echo $N;done;};trap $'echo "\e[41m Exit "`e`" \e[m"' ERR

Re: Halloween Bash Profile Generator

#22

Post by Symmetry » Wed, Oct 31, 2012, 7:49 PM UTC

jdp wrote: post #19

Symmetry wrote: post #17

Very nice. I sort of with there was an easy way to do fish style prompt paths in bash (/home/username/bin -> /h/u/bin), but that's hardly this excellent website's fault. I guess I'm just annoyed at being tied to bash due to ROS.

Here's one from the Arch mailing list. Also does the ~ expansion for home directories: http://www.mail-archive.com/arch-general@archlinux.org/msg07...

Thanks! With this complementing the git status function I already had, my prompt is now 20% cooler.

Re: Halloween Bash Profile Generator

#23

Post by graywh » Wed, Oct 31, 2012, 8:41 PM UTC

cjg_ wrote: post #5

Nice! A bug report, space tokens should not exhaust. Currently you can at max have 2 spaces, the one that is in the config by default and one from the available tokens.

Same for the other single characters.

Re: Halloween Bash Profile Generator

#24

Post by rexf » Wed, Oct 31, 2012, 9:55 PM UTC

Tyr42 wrote: post #4

One option that is missing that I really thing is useful is wincolour=$yellow errorcolour=$red # To provide a coloured version of $?, wrapped in (). Used in PS1 pretty_exit_code(){ LAST_COMMAND_STATUS=$? if [ $LAST_COMMAND_STATUS = 0 ]; then echo -e "$wincolour($LAST_COMMAND_STATUS)$black"; else echo -e "$errorcolour($LAST_COMMAND_STATUS)$black"; fi } Which just provides the exit code of the last command, but coloure…

Just added exit status to the page. Thanks for the suggestion.

Re: Halloween Bash Profile Generator

#25

Post by paupino_masano » Thu, Nov 01, 2012, 3:22 AM UTC

I love this idea - especially for those that are unfamiliar with BASH yet still want to customize their command line experience. Unfortunately due to a previous HN article I now use zsh - would love to see a zsh prompt generator too!

Re: Halloween Bash Profile Generator

#26

Post by asdfprou » Thu, Nov 01, 2012, 2:01 PM UTC

At first I wondered how you managed to extract my username and then I realized it was hardcoded when I looked through the code.

Re: Halloween Bash Profile Generator

#27

Post by michaelhoffman » Thu, Nov 01, 2012, 5:44 PM UTC

myhf wrote: post #21

michaelhoffman wrote: post #12

Earlier quoted context omitted.

I use this, which allows a similar effect but is enabled for PIPESTATUS, and also does some good things for eterm and screen. PIPESTATUS_REGEX="^ +$" # check to see if any of the pipe statuses don't start with 0 # ${_CMD_PIPESTATUS[@]#0} results in null if they all do _PIPESTATUS=" _CMD_PIPESTATUS=(\${PIPESTATUS[@]}) if [[ \"\${_CMD_PIPESTATUS[*]#0}\" && ! \"\${_CMD_PIPESTATUS[*]#0}\" =~ \$PIPESTATUS_REGEX ]] then _R…

It's cool to also see the name of the signal that caused exit status > 128. Sadly this only fits in a tweet if it can assume the possible signal names are listed contiguously, which isn't so on 64-bit Linux these days. S=(`trap -l`);e(){ for N in ${PIPESTATUS[@]};do ((N>128))&&echo ${S[$((2*N-257))]}||echo $N;done;};trap $'echo "\e[41m Exit "`e`" \e[m"' ERR

That's a great idea. I've rewritten my own version to use these signals instead of numbers where possible.