-
-
Notifications
You must be signed in to change notification settings - Fork 363
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
yay --diffmenu using kompare opens empty #2478
Comments
what arguments does kompare expect to work? can you run with the config json entry "debug": true and share the output as well? |
kompare expects two arguments, one for each file to compare, in this pattern: (-c can be used for remote files' respective URLs)
I have no AUR packages in need of an update right now. I tried to force it by changing the PKGBUILD in the yay/cache, but was unable to. I must be missing something stupid. I'll either wait for an updated release to come, or try again to force later. If you know how to do so easily, tips are appreciated. |
Here is the output, with diff menu, and debug active:
|
Running something like the below command works, by making a file that kompare can actually ready. But I am struggling to get kompare to accept direct input from git diff.
Was anyone able to reproduce this?
The command above successfully pipes the correct differences to kompare, but I wouldn't know how to modify yay to do this by default. |
Affected Version
yay v12.3.5 - libalpm v14.0.0
Describe the bug
When using
yay
to compile/install AUR software, if the user opts to view diffs, the configured diff toolkompare
is opened but without the files preselected, resulting in a kompare window with empty fields.Reproduction Steps
kompare
as the diff tool foryay
(via git's config, the $GIT_PAGER or $PAGER environment variables).yay
to update an AUR package.kompare
opens but without preselecting the diff files/PKGBUILD.Expected behavior
kompare
should open with the diff files preselected, showing the differences between the files.Output
The text was updated successfully, but these errors were encountered: