-
Notifications
You must be signed in to change notification settings - Fork 22
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
papers --add fails if in a subdir? #64
Comments
Hmm, your command looks correct. Which version of |
Regarding the file-formatting issue, not all fields are available. So far only author, title, year and ID, in various formatting options. Here an example:
It would be better to have generic filters such as |
papers 2.4 -- I'll try your branch now... |
OK, super -- on your branch, this issue is no longer observed:
|
I would indeed find "journal" useful, if it's not too much work; please let me know... |
What might be a good way to go it to merge pr-perfect-undo if it's not too work-in-progress, and then I can get up to speed on that, as a whole. |
@perrette By chance, does the config file change between pr-perfect-undo and 2.4? I see:
This still does reproduce the error above when I remove the call to "journal" and just try the add:
Cheers! |
It has been a while now, but it may change the default location in relation to local/global install (possibly it also does local by default, I can't remember now). This is a feature branch that grew up bigger than it should have. Should be merged and be done with it. Calling it version 3 I guess. Anyway to remove the warning why not follow the recommendation in the message and remove the config file that triggers the warning? |
Oh, sorry -- yes, I was not sure of the downstream consequences on the install/not-install state there, since I'm still new to that bit... |
Hey @perrette -- I'm reading through https://github.com/perrette/papers/tree/pr-perfect-undo (specifically papers/filename.py). Do I understand correctly that the available fields are defined solely there? If so, I can try to come back with a PR that adds the journal; do let me know... Cheers! |
Yes exactly. The fields are defined in |
@perrette -- this is extending the conversation in #65 I looked at this, and can confirm the behavior in https://github.com/perrette/papers/tree/pr-perfect-undo I saw: -- when running -- if checking the bibtex yields a duplicate AND that duplicate has a -- then the duplicates' In my case, I had the Pardon2013 paper in my database, with So, question -- how corner-case'y is this corner-case? |
@perrette hello, hello -- let me know? |
I see
The pdf itself is OK, I think -- this is the right PDF metadata after the add.
My papers is installed, and the config is:
Note that if I switch to the {journal} tag in the config ( by doing "template": "{journal}/{year}{author}{title}") which should be supported, as {journal} is a valid BibTex field, I get
I can refile this as two issues, but am I calling "add" correctly? The behavior I expect is to have the PDF renamed and moved, and the entry added to the end of library.bib.
The text was updated successfully, but these errors were encountered: