-
Notifications
You must be signed in to change notification settings - Fork 55
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
Batch Note Insertion in Citar #837
Comments
Can you clarify this part a bit more? |
is this perhaps related to #835? |
So hopefully we can fix that sometime soon, though no promises on when that might be. Perhaps when that is fixed, it may be more straightforward to do what you want to do functionally. |
Background:
I previously used
helm-bibtex
and customized an action where I could pass in keys. If a key had a corresponding note, it would skip it; if not, it would add a new one. This allowed me to batch add notes when selecting multiple items, which was particularly useful for managing lists of books or movies.I implemented a
notes-source
where notes were added as outlines to an existing file rather than creating new files.Issue:
In
citar
, while selecting multiple entries and inserting citations works perfectly, attempting to open notes for multiple entries results in an error:embark PCH: (wrong-type-argument stringp nil)
. I initially assumed this would batch insert notes, but it seems there is a limitation or bug.Feature Request:
I would like to request a feature in
citar
that allows for batch note insertion for multiple selected entries, similar to my previous setup withhelm-bibtex
. This feature should:notes-source
setup (e.g., as outlines in an existing file).Questions:
I'm not sure if modifying the existing function to implement this feature is appropriate...
The situation is indeed quite complex, simply looping the :create function may be not enough.
If I want to add a new function to embark to achieve this feature, which keymap should I hack? how should I get the selected keys from citar?
The text was updated successfully, but these errors were encountered: