giovannicoppola / paperpalfred Goto Github PK

Thank you for creating this amazing Alfred paperpile plugin. I noticed I am unable to open certain PDF files using system viewer, i.e. after searching for a paper, pressing "Enter" does not do anything.

After some debugging, I found out that the filename extracted from Alfred Workflow (i.e. the query response item 1) does not match the local file name.

The extracted file name from query response contains an additional space (or empty) character after " ..."

So here is the extracted filename:

"Fleming et al. 2018 - Beyond the Trial - Systematic Review of Real-World ... Digital Self-Help Interventions for Depression.pdf"

But my local file name is:

"Fleming et al. 2018 - Beyond the Trial - Systematic Review of Real-World ... Digital Self-Help Interventions for Depression, Low Mood, or Anxiety.pdf"

Notice the first file name contains double space characters after " ...".

At the moment, I did a workaround in the Alfred shell script (open PDF with system viewer) to replace the " ... " with "*" wildcard:

escape_query=echo "{query}" | sed -e "s/ ... / \*/g"
find "$PAPPATH" -name "$escape_query" | head -n 1 | tr \n \0 | xargs -0 open

But would be much appreciated if the future release can incorporate this change?

Currently some testing of Github automatic export/sync is available and working, would it be possible to have this Workflow point directly to a public Github repo with a sync-ed BibTeX file? Thank you for making this useful Workflow! :)

Since paperpile can auto export library to a bibtex file, I wonder if it is possible to use bibtex as the database? This way the library is always up to date without the need to manually export JSON.

As far as I understand, paperpAlfred requires manual update of JSON paperpile library and reset the PATH, which is not quite feasible for users.

I recently exported my Paperpile Library to a JSON format multiple times to update my list of papers. Despite this, none of my recent papers appear or are searchable in PaperpAlfred. While the plugin's functionality remains mostly intact, it fails to load any new files. I'm uncertain how to best approach debugging this issue.