Share your Bash prompts!

[asparagus0098@sh.itjust.works]

My bash prompt is just me copying the prompt I have set on fish.

# Prompt
green=$'\e[38;5;2m'
bright_red=$'\e[38;5;9m'
bright_green=$'\e[38;5;10m'
reset=$'\e[0m'

prompt_command()
{
    local exit_status=$?

    if [[ $exit_status != 0 ]]; then
        exit_color=$bright_red
        exit_prompt=" [$exit_status]"
    else
        exit_color=$bright_green
        exit_prompt=""
    fi
}

PROMPT_COMMAND=prompt_command
PS1='\[$green\]\w\[$exit_color\]$exit_prompt\n❯ \[$reset\]'

I have a small issue with this prompt though. Sometimes the ❯ ends up turning white for some reason.

[tankplanker@lemmy.world]

Another starship user. Mostly want it to summarise useful stuff for folders pulled from git or whatever so it's pretty plain rest of the time. I use the same on all my boxes

[mbirth@lemmy.ml]

You shouldn’t just “drop bash commands into it” anyways. And if you really need it, bash is only one bash away.

[billwashere@lemmy.world]

Best I can tell is it’s a normal `username@hostname current_directory$ sorta prompt with some coloring:
• Red for the square brackets
• Orange (color 172) for the username
• Light blue (color 153) for the hostname
• Amber (color 214) for the current working directory

Other than being hard to read from the embedded coloring I’m not sure why this is a war crime.

[mike_wooskey@lemmy.thewooskeys.com]

It is in my .bashrc, but any delay is not noticeable.

[goun@lemmy.ml]

Yeah, its checking if the file exists first, so it's not doing it all the time.

My worry is more related to repos takeovers or hacks. This is pretty hidden, so it could be easy to even forget it's there, probably not the worst, but still..

[teawrecks@sopuli.xyz]

Ah that's fair, I didn't look closely

[thefadingone@feddit.org]

I'm mainly using zsh but I have a backup bash prompt that closely mirrors it.

retval() {
        if [ $? -eq 0 ]; then
                printf ""
        else
                printf "\001\e[31m\002($?)\001\e[0m\002"
        fi
}

gitbranch() {
        if type git 2> /dev/null 1> /dev/null && git rev-parse 2> /dev/null 1> /dev/null ; then
                MODIFIED=""
                if [[ -n $(git status --short) ]]; then
                        MODIFIED=" M"
                fi
                BRANCH=$(git rev-parse --abbrev-ref HEAD)
                SHORTREF=$(git rev-parse --short HEAD)
                printf "\001\e[31m\002%s\001\e[0m\002(%s)\001\e[31m\002%s\001\e[0m\002" $BRANCH $SHORTREF $MODIFIED
        else
                echo -n ""
        fi
}

export PROMPT_DIRTRIM=3

PS1='$(retval)[\001\e[1;95m\002\u\001\e[0m\002@\h : \w $(gitbranch)] \$ '
PS2='> '

[marauding_gibberish142@lemmy.dbzer0.com]

Am I a loser if I stick to POSIX?

[richardisaguy@lemmy.world]

computer /usr/share/ $>

[Guest]

PS1='\[\e[1m\][\[\e[92m\]\u\[\e[0m\]@\[\e[96;1;3m\]\h\[\e[0;1m\]]\[\e[0m\] \[\e[1m\][\[\e[38;5;226m\]\w\[\e[39m\]]\[\e[0m\] \[\e[97;1m\]~\[\e[92;5m\]\$\[\e[0m\] '

Note: The "$" prompt flashes like a typical cursor.

[beirdobaggins@lemmy.world]

Mine shows the full path and a new line for commands.

It will also print the exit code of the last command in red above the prompt, if the exit code is not 0.

PS1='$(ec="$?"; if [ $ec -gt 0 ]; then echo -e "\n"[\e[91m]"exit code: $ec"[\e[0m]; fi)\n[\e[92m]\u[\e[38;5;213m]@[\e[38;5;39m]\h[\e[0m]:$PWD\n$ '

[tiger_man_@lemmy.blahaj.zone]

Mine is just status(if not zero) and wd

[jcg@halubilo.social]

Convert the PWD value to use backslashes, too, for extra cursedness.

[madmadbunny@lemmy.ca]

c/FoundSatan

[questionasker@lemmy.ml]

[username@host ~]$ >

[danielquinn@lemmy.ca]

and rather elaborate. From left-to-right:

• name@server-name
• Uptime (multiplied by 10 and rounded to the nearest integer to save space)
• Percentage disk space available on /
• Number on established network connections
• Git branch : commit
• Python virtualenv
• [new line]
• date and time

The code for this is on GitLab.

[pewpew@feddit.it]