Skip to content

Conversation

@coolreader18
Copy link

I wasn't sure if this behavior was to some degree intentional, but it's tripped me up a couple times. Now, when you run paru -Sc and then ^C, it fully exits immediately, rather than just the pacman process being cancelled and having to ^C again the paru process. If it was intentional to not immediately exit on pacman error, maybe clean could just check whether it exited from a signal or not.

@Morganamilo
Copy link
Owner

This should probably be checked the same way as elsewhere. An overall ret value that we return at the end of the function. Doing this would mean a non 0 from pacman would stop the AUR clean from running.

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

Successfully merging this pull request may close these issues.

2 participants