Replies: 3 comments
|
If I understand correctly, this is because of two things:
I agree that for most people's use-case it's not practical for this to be the default behavior. You'd have to press Is this meant to happen even when there's no output (e.g. from |
0 replies
it behaves like that, yes. |
0 replies
$ git branch 1>/dev/null # Pipes stdout to /dev/nullhttps://www.cyberciti.biz/faq/how-to-redirect-output-and-errors-to-devnull/ Additionally you should just be able to pipe it even when it's doing |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
a non-oh-my-bash system
git branchdoes roughly this:so, it returns to stdout and provides a fresh prompt and you can proceed working.
with
oh-my-bashthis changes to some sort onless-ishoutput behaviour , meaning the stdout is piped to less.you need to leave that with the
qto get back to a fresh prompt to continue working.I find this not practical and am wondering how to switch this off in an
oh-my-bashpowered terminal?All reactions