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

[Feature Request] Allow Independent File Handling Settings for Chrome Extension #612

Open
cpfy opened this issue Sep 19, 2024 · 1 comment
Labels
feature-request New feature request low-priority low priority

Comments

@cpfy
Copy link

cpfy commented Sep 19, 2024

Hi~ Firstly, I want to express my heartfelt gratitude for your exceptional work on this open-source academic paper management tool. It has been incredibly useful for managing my research papers effectively.

Describe the Feature

Currently, when using the Paperlib Chrome extension to import PDFs, an extra copy of the PDF files remains in the $HOME/Download directory. After a period of exploration, I guess that the Chrome extension inherits the file handling settings from the Paperlib app (Copy/Cut/Symlink). Changing the setting to "Cut" removes the leftover files in the Download directory, but this also affects how local files are handled when imported through the app.

I would like to request a feature enhancement where the Chrome extension can have independent file handling settings, separate from the main Paperlib app. This would allow users to control how files are managed during import via the extension without impacting the app's local file settings.

Additional Context

Thank you for considering this feature request. I'm looking forward to seeing how this tool continues to evolve!

@cpfy cpfy added the feature-request New feature request label Sep 19, 2024
@GeoffreyChen777
Copy link
Member

Hi, because we use the same method for these two ways. The chrome extension download the pdf to your Downloads folder and paperlib move it to the library, just like you drag and drop a pdf into paperlib.

We can enhance this later, but it's a low-priority work.

@GeoffreyChen777 GeoffreyChen777 added the low-priority low priority label Sep 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature request low-priority low priority
Projects
None yet
Development

No branches or pull requests

2 participants