Link file with key finishing by _

[melTr]

JabRef version

Latest development branch build (please note build date below)

Operating system

GNU / Linux

Details on version and operating system

No response

Checked with the latest development build

• I made a backup of my libraries before testing the latest development version.
• I have tested the latest development version and the problem persists

Steps to reproduce the behaviour

My key is [auth][shortyear]-[journaltitle]_
Files are automatically linked with the option "starting with" the bibkey

Some files (not all) are not found automagically. However, if I change the key to [auth][shortyear]-[journaltitle], the files are found.
On JabRef5.9 (and 5.10-21.07.2023)

Thanks
Mel

Appendix

...

Log File

Paste an excerpt of your log file here

[ThiloteE]

1. unfortunately - is a special character in java regex, so i would try to avoid that if you want to use special regex to change your citationkey or want to search through your library for keys via regex.
2. unfortunately _ is a special character in latex, so i would try to avoid that if you want to export your library to latex.

Maybe _ is a special character in java (not java regex!) too, I don't know.

[melTr]

Thanks. I used _ since forever in bibkey but I don't use Latex...
However does file linking is achieved via regex? I never had trouble linking files even with -. In fact, _ inside the bibkey is working, but not those ending with _.

[Siedlerchr]

You could try to escape the underscore with a backslash, that might work melTr ***@***.***> schrieb am So., 23. Juli 2023, 23:58:

…

Thanks. I used _ since forever in bibkey but I don't use Latex... However does file linking is achieved via regex? I never had trouble linking files even with -. In fact, _ inside the bibkey is working, but not those ending with _. — Reply to this email directly, view it on GitHub <#10106 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACOFZA6WZEDKRHHPI3RYRLXRWNBHANCNFSM6AAAAAA2UHMW5Y> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[ThiloteE]

While acknowledging this is a bug, I set the priority to low, because there is a workaround and multiple conditions have to be fulfilled to trigger it, which includes non-default citationkeys AND having your external files be named after your citationkey. Having _ in your citationkey is also incompatible with latex, so we would want to discourage users using _ in their citationkey.

The workaround is to use a different citationkey pattern.