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

Weird output when using in-terminal file manager #1280

Open
dorsiflexion opened this issue Nov 26, 2024 · 0 comments
Open

Weird output when using in-terminal file manager #1280

dorsiflexion opened this issue Nov 26, 2024 · 0 comments

Comments

@dorsiflexion
Copy link

dorsiflexion commented Nov 26, 2024

Affected Version

paru v2.0.4 - libalpm v15.0.0

Description

Just a minor thing, but the output seems to be interrupted and overwritten when using a terminal file manager like nnn that opens in the same terminal window as paru. It becomes visible when you close the file manager which you reviewed the changes with. One can continue as usual, but the output just looks weird. Also, as you write over the package name, it is not really clear what you are inputting to the Accept changes? prompt.

It does not seem to be nnn, because it's the same with ranger.

IIRC, this was introduced with v2.0.0.

Output

$ paru --fm nnn -Su

[…]

Aur (2)                    Old Version  New Version    Make Only
aur/discord_arch_electron  0.0.75-1     0.0.76-1       No
aur/hibiscus               2.10.21-1    2.10.23-1      No

:: Proceed to review? [Y/n]:

:: Downloading PKGBUILDs...
:: Accept changes? [Y/n]: on-0.0.76-1                [--------------------------------------------------]

When the paru git clones are up to date, it does not happen:

:: Downloading PKGBUILDs...
 PKGBUILDs up to date
:: Accept changes? [Y/n]:

paru.conf probably does not matter, but anyway:

[options]
BatchInstall
SaveChanges

[bin]
GitFlags = -c user.name=paru_cache
Sudo = doas
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 a pull request may close this issue.

1 participant