Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Exit code 1 showing on powerline prompt?? #637

Open
Paulie420 opened this issue Dec 6, 2022 · 5 comments
Open

Exit code 1 showing on powerline prompt?? #637

Paulie420 opened this issue Dec 6, 2022 · 5 comments

Comments

@Paulie420
Copy link

Sorry to post this here - I love Atuin and getting a history w/ the up arrow key, but I'm having an issue...
I installed in Arch Linux with pacman, ran the two shell commands to add two lines to .bashrc and restart my terminal. At first the powershell prompt looks normal, but after the FIRST command I enter it shows an orange "1" on the end of the prompt - i believe thats an exit code???
Anyone have any ideas, as I'd really like to use this software. Cheers.

@arcuru
Copy link
Contributor

arcuru commented Dec 7, 2022

  1. You didn't say, but I assume you downloaded .bash-preexec.sh, so you also have the file ~/.bash-preexec.sh in your home folder.
  2. Assuming that's an exit code, then that most likely just means the command that you ran returned an exit code of 1. Do you get that exit code for every command? Try running just a plain ls.
  3. Do you get any errors when you run atuin history last?

@Paulie420
Copy link
Author

Paulie420 commented Dec 7, 2022

Thanks for the reply, patricksjackson;

Yes I have .bash-preexec.sh located in ~/
Yes, it displays after entering ANY command - terminal comes up and powerline shows no error, entering 'ls' (or any other command) it then shows 1, and the 1 remains there forever. Normally, as you know, if a command returns a 1 exit code, it goes away after the next 0 exit code...

paulie420  ~  1 $ atuin history last
2022-12-07 23:30:35	ls .bash-preexec.sh	37ms

(Know that the 1 is there b/c of this issue, not an error from 'atuin history last' - I think.

Last, I don't know if I love the UP button to activate atuin - in the end I may just remove that funtionality... I believe I just remove the line in .bashrc that loads that .bash-preexec.sh load. I wonder if doing so would 'fix' my issue too.

Again, appreciate you helping me diagnose my issue that I believe is my systems fault, not atuin's.

One last PS; 'atuin search -i' pulls up the interactive mode, but press UP/DOWN doesn't allow me to scroll up... just mentioning cause; isn't it supposed to doso? (I'm hoping of removing the AUTO-up feature and alias search -i to 'history', but if it doesn't scroll...)

@mweirauch
Copy link

Experiencing the same issue. This seems to be related to sourcing .bash-preexec.sh. Without it, this is not happening. Of course then the history isn't caught. Dunno if this is then rather a bash-preexec issue.

Fedora 37, Bash 5.2.15(1)-release, powerline 2.8.3 + powerline-gitstatus 1.3.1

@joeydc
Copy link

joeydc commented Aug 26, 2023

Same issue as well.
Arch Linux, Bash v5.1.16, Powerline v2.8.3

@StephanSchuster
Copy link

StephanSchuster commented Feb 1, 2025

I face the same. But I assume it's not the exit code but the jobNum. I could hide it in Powerline via config. BUt not sure if this is the way to go. Any feedback?

I use Tilix, Powerline and Atuin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants