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

rifle call with wrong arguments? #474

Open
ttxtea opened this issue Jan 6, 2023 · 1 comment
Open

rifle call with wrong arguments? #474

ttxtea opened this issue Jan 6, 2023 · 1 comment

Comments

@ttxtea
Copy link

ttxtea commented Jan 6, 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)

papis -l mylib open

and then an entry is selected, then

rifle: error: the following arguments are required: --isa_spec/-ispec, --platform_spec/-pspec

This may well be a rifle issue. But let it be reported here, as maybe the rifle call in papis has changed.

@alexfikl
Copy link
Collaborator

alexfikl commented Jan 6, 2023

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 alexfikl changed the title rife call with wrong arguments? rifle call with wrong arguments? Jan 9, 2023
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

No branches or pull requests

2 participants