-
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
Citar fails to display files containing commas #819
Comments
Been awhile since I've looked at that code, but it's tricky to generalize file path parsing of this sort. Edit: a quick test in ELISP> (setq my/f1 "one,two.md;three.md")
"one,two.md;three.md"
ELISP> (citar-file--parser-default my/f1)
("one,two.md" "three.md")
ELISP> (citar-file--parser-triplet my/f1)
nil So that example would work as is. Per Roshan, please share a bib fragment that fails. |
@wenzlawski, could you paste the bib entry that's causing you the issue? |
I failed to realize that it's not the standard format, but the one exported by Calibre catalog. Their export format is a bit strange and I don't think there is a way to change it. The format output from that command is the So when calling
But when calling
|
@roshanshariff the following is a minimal failing bib. Remove the commas from the files and it works as expected.
|
This seems like a variant of #454. You should be able to escape the commas within the filenames by putting a backslash before them. Citar will split the file field at unescaped commas, and then replace the escape sequences in the filenames. |
Describe the bug
Citar fails to find files containing commas when displaying in completing read. Strangely everything works fine when there is only one file associated with an entry. However when there are two files present and one has to select one to display it shows the following error:
To Reproduce
Steps to reproduce the behavior:
citar-open
and select the entryAlternatively, call
citar-open-files
, select the entry and the above error message appears.Emacs version: 29.2
The text was updated successfully, but these errors were encountered: