-
-
Notifications
You must be signed in to change notification settings - Fork 89
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
Faster way to view PKGBUILD, etc. on first install #648
Comments
i replied via email, but that reply is not showing up for some reason. forgive the duplicate reply if that message eventually comes up! pikaur handles future updates to packages (installed by pikaur) by showing the future version's PKGBUILD and relevant install files diff's against the prior PKGBUILD and install files. perhaps a nice to have feature would be to have the option to pipe the PKGBUILD's contents through less if the goal is to only view the PKGBUILD without editing it. and with a few more keystrokes you might be able to submit the pull request that accomplishes exactly this ;) |
I think there's a misunderstanding here. I was talking about the first install, where unlike yay and paru, pikaur shows the diff as nothing instead of the entire file. I think the current behaviour is fine for updates. |
i think it could be new config option added for choosing alternative command for viewing file for the first time (if it's not set - normal editor logic should be executed) - so people could choose |
pikaur handles future updates to packages (installed by pikaur) by
showing the future version's PKGBUILD and relevant install files diff's
against the prior PKGBUILD and install files.
perhaps a nice to have feature would be to have the option to pipe the
PKGBUILD's contents through less if the goal is to only view the
PKGBUILD without editing it.
and with a few more keystrokes you might be able to submit the pull
request that accomplishes exactly this ;)
|
Is there a faster way to view the PKGBUILD on the first install (eg. showing diff against an empty file like yay does)? Going into edit and then hitting :q takes way too many key presses.
The text was updated successfully, but these errors were encountered: