pablopunk / bashy Goto Github PK

I've found a way to make bashy even faster:

git diff-files --no-ext-diff --quiet || git diff-index --no-ext-diff --quiet --cached HEAD

Problem

It doesn't know about untracked files, and I really don't wanna give up that feature 😭

Show ~ instead of folder name when you are in $HOME

Bigger and more beautiful

The current behavior only works if the current folder is a git repo. It doesn't work if the folder is in a git repo.

You can test if a directory is inside a git tree with

git rev-parse --is-inside-work-tree &>/dev/null

git rev-parse --is-inside-work-tree will print true or false. However, it will send fatal: Not a git repository (or any of the parent directories): .git to STDERR, so adding &>/dev/null prevents either STDOUT or STDERR from printing to the screen.

Reproduce error

~/repos/bashy at pure ✓ # no changes. All good.
~/repos/bashy at pure ✓ echo "change" >> readme.md  # I change one file
~/repos/bashy at pure • # change detected. All good
~/repos/bashy at pure • git add -A # I add the file to the commit
~/repos/bashy at pure ✓ # branch clean cause it's staged. All good
~/repos/bashy at pure ✓ echo "another change" >> readme.md # I make a second change
~/repos/bashy at pure + # HERE is the error. This should show the modified symbol

This happens because the output of git status --porcelain after the second
change is MM readme.md instead of M readme.md like in the first change.

First off, thanks a lot for this awesome prompt. Love it 💙

I've managed to change the color of the foreground symbol to green, but I am struggling with the following:

- How to set symbol to bold

• How to add color to repo and branch text

I am grateful for any help with this. Thanks in advance!

EDIT: Seems the bold was already there, just not clearly visible in Tilda terminal. In Gnome terminal it works well.

When you press the UP arrow to navigate through the history,
eventually the prompt is deleted and the history overlaps the whole line.

This also happens when the current command exceeds the terminal width,
which can be solved escaping PS1 with export PS1="\[$(bashy)\] $ "
but the history problem is still happening.

I had this error before, and it was because not escaping the 0 length
characters like $bold in the PS1 variable. The problem now is that
in bashy I'm not setting the variable itself, I just use echo to print it,
and escaping these variables (\[$bold\]) doesn't work cause those
characters are just for variables and not for echo.

BTW, consider using printf instead of echo. It doesn't solve the problem
but is better for compatibility.