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

citar-file--possible-names broke #412

Closed
bdarcus opened this issue Nov 16, 2021 · 5 comments · Fixed by #413
Closed

citar-file--possible-names broke #412

bdarcus opened this issue Nov 16, 2021 · 5 comments · Fixed by #413

Comments

@bdarcus
Copy link
Contributor

bdarcus commented Nov 16, 2021

Something isn't working correctly with this function now, which has cascading impacts (for example, open-notes now doesn't work correctly). It now only returns existing files, but should always return a list of paths.

ELISP> (citar-file--possible-names "low2001" citar-notes-paths '("org"))
("/home/bruce/org/roam/biblio/low2001.org")
ELISP> (citar-file--possible-names "low200X1" citar-notes-paths '("org"))
nil

cc @localauthor @roshanshariff

bdarcus added a commit that referenced this issue Nov 16, 2021
Fix #412.

Also, autoload citar-org-open-notes-default.
@bdarcus
Copy link
Contributor Author

bdarcus commented Nov 16, 2021

The problem appears to be here; #413 should fix it, though I haven't tested it extensively.

bdarcus added a commit that referenced this issue Nov 16, 2021
Fix #412.

Also, autoload citar-org-open-notes-default.
@bdarcus
Copy link
Contributor Author

bdarcus commented Nov 16, 2021

OK @massdorp, I merged a fix. Can you test and confirm?

@maasdorp
Copy link

Thank you! Now it works as intended once again. I could create a new note from the template using citar-open-notes.

@roshanshariff
Copy link
Collaborator

Yes, sorry, my mistake. I hadn't realized how that function is used for creating new notes as well.

@bdarcus
Copy link
Contributor Author

bdarcus commented Nov 16, 2021

No worries; I should have caught that.

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

Successfully merging a pull request may close this issue.

3 participants