I’m looking for inspiration for a custom Bash prompt[1]. I’d love to see yours! 😊 If possible, include both the prompt’s PS1, and a screenshot/example of what it looks like.

References
  1. Type: Documentation. Title: “Bash Reference Manual”. Publisher: Gnu Project. Edition: 5.2. Published: 2022-09-19. Accessed: 2025-03-21T02:46Z. URI: https://www.gnu.org/software/bash/manual/html_node/index.html.

Crossposts:

  • Daniel Quinn@lemmy.caEnglish
    1·
    19 hours ago

    My shit is custom and rather elaborate.

    Screenshot of the prompt

    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.

  • beirdobaggins@lemmy.world
    2·
    2 days ago

    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$ ’

    • Ephera@lemmy.mlEnglish
      151·
      3 days ago

      Same. I guess, this is the Starship thread now. My config:

      I adapted it from the Gruvbox Rainbow theme.
      I can post my config, if anyone wants specifically that. (It does kind of assume a light background, though.)

      • fluckx@lemmy.world
        3·
        3 days ago

        I like the timer and the error icon on a fail. I can’t recall how often I think: damn this is taking too long. I should’ve timed the command

    • tankplanker@lemmy.world
      1·
      3 days ago

      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

    • Azzk1kr@feddit.nlEnglish
      4·
      3 days ago

      Fish is a really great shell for daily use. There’s so much built in, its scripting language is better (not portable though if someone else does not have fish).

      • mbirth@lemmy.ml
        31·
        3 days ago

        By now, enough people have fish that you can basically assume those scripts being “portable”. Far better than nushell or xonsh - which are both pretty advanced shells but other tools lack support for them, e.g. Midnight Commander.

    • PlutoniumAcid@lemmy.world
      13·
      3 days ago

      I recently started with fish and dislike that I can’t drop bash commands into it because it parses differently. That is enough to annoy me to uninstall.

      • mbirth@lemmy.ml
        7·
        3 days ago

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

  • SinkingLotus@lemmy.world
    1·
    2 days ago

    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\] '

    image

    Note: The “$” prompt flashes like a typical cursor.

  • golden_zealot@lemmy.mlEnglish
    101·
    3 days ago

    Prompt is pretty simple, mainly just adjusted coloring and added a timestamp.

    PS1='${debian_chroot:+($debian_chroot)}\[\033[01;36;01m\]\t \[\033[01;32m\]\u@\[\033[01;37;01m\]\h\[\033[00m\]:\[\033[01;36m\]\w\[\033[00m\]\$ '

  • Xanza@lemm.eeEnglish
    9·
    3 days ago
    export PS1="\[\e[31m\][\[\e[m\]\[\e[38;5;172m\]\u\[\e[m\]@\[\e[38;5;153m\]\h\[\e[m\] \[\e[38;5;214m\]\W\[\e[m\]\[\e[31m\]]\[\e[m\]\\$ "
        • billwashere@lemmy.worldEnglish
          3·
          3 days ago

          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.

  • Rivalarrival@lemmy.todayEnglish
    71·
    3 days ago

    I didn’t even know I needed to edit my prompt, but now I don’t know how I have lived with it for so long.

  • nore {she/her}@sh.itjust.worksEnglish
    5·
    3 days ago

    Mine’s pretty simple:

    ## .bashrc
export BLA=$(tput setaf 0) # Black
export RED=$(tput setaf 1) # Red
export GRE=$(tput setaf 2) # Green
export YEL=$(tput setaf 3) # Yellow
export BLU=$(tput setaf 4) # Blue
export MAG=$(tput setaf 5) # Magenta
export CYA=$(tput setaf 6) # Cyan
export WHI=$(tput setaf 7) # White

export BOL=$(tput bold)    # Bold
export ITA=$(tput sitm)    # Italic
export UL=$(tput smul)     # Underline
export NC=$(tput sgr0)     # No color & format

_branch() {
    local branch=$(__git_ps1 "%s")
    if [[ -z $branch ]]; then
        printf "${BLA}null${NC}"
    else 
        printf "${CYA}$branch"
    fi
}

PS1='.\[$(_pwd)\] \[$BLA\]〜 \[$MAG\]git\[$BLA\]:\[$(_branch)\] \n \[$NC$CYA\]\! \[$MAG\]\$ \[$NC\]'

## .inputrc

set vi-ins-mode-string \1\e[34m\2.INS
set vi-cmd-mode-string \1\e[33m\2.CMD