You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report! Unfortunately, I can't tell what's going on, so we'll have to debug a bit 😁
Any idea where those extra flags come from? From a quick search on github, they seem to match the flags of riscv-config. Any chance you have a typo in your config somewhere? Maybe in the ranger / rifle configuration for the file type you're trying to open (not a ranger user, unfortunately)..
On our side, when opening a file, papis just does subprocess.call([opentool, filename]), so we do not add any flags in there (see here). Can you check what the open tool is set to using
papis -l mylib config opentool
? (mine just shows xdg-open) You can also run with debug messages enabled using
papis -l mylib --log DEBUG open
which should print a cmd: rifle [arg] [arg] [arg] 'filename' message when it tries to open the file. That should tell us if there are extra flags in there.
alexfikl
changed the title
rife call with wrong arguments?
rifle call with wrong arguments?
Jan 9, 2023
papis, version 0.12
ranger/rifle, version 3.10.6
how to reproduce the issue
If papis is used to open a pdf file from a library (file exists)
and then an entry is selected, then
This may well be a
rifle
issue. But let it be reported here, as maybe the rifle call in papis has changed.The text was updated successfully, but these errors were encountered: