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

use Papis opentool #59

Merged
merged 4 commits into from
Jun 15, 2024
Merged

use Papis opentool #59

merged 4 commits into from
Jun 15, 2024

Conversation

jghauser
Copy link
Owner

@jghauser jghauser commented Jun 4, 2024

No description provided.

@jghauser jghauser linked an issue Jun 4, 2024 that may be closed by this pull request
@jghauser
Copy link
Owner Author

jghauser commented Jun 4, 2024

I just realised that this needs some more thinking because (a) Papis will always have its own opentool settings, so we don't need them in papis.nvim and (b) we can't just run the opentool as a command as the Papis option might include arguments (so we need to split the string to get the command + args). I also noticed there's a difference between the default windows opener, and I'm not sure if that matters.

@jghauser jghauser merged commit fcead3d into main Jun 15, 2024
@jghauser jghauser deleted the opentool branch June 15, 2024 15:41
@jghauser
Copy link
Owner Author

Just a small explanation: papis.nvim now always uses the opentool defined by Papis. This should work as Papis will by default set that to something that works for the OS on which it is 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.

Opening files should respect papis config
1 participant