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

The command "Push entries to external application" adds a "null" prefix and suffix to an existing Citationkey in LaTeX. #10568

Closed
2 tasks done
NeymanDmitry opened this issue Oct 24, 2023 · 10 comments
Labels
bug Confirmed bugs or reports that are very likely to be bugs

Comments

@NeymanDmitry
Copy link

JabRef version

5.11 (latest release)

Operating system

GNU / Linux

Details on version and operating system

Ubuntu 22.04 (64-bit)

Checked with the latest development build (copy version output from About dialog)

  • 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

  1. Create a new entry or use an existing one with Citationkey "CITATION_EXAMPLE" - for example in JabRef 5.11.
  2. Open a LaTex document in TexStudio.
  3. Click on the "Push entris to external application" button or use the command (ctrl+L) to add an entry to latex.

As a result, the following link with the following content will appear in the latex document:

\cite{nullCITATION_EXAMPLEnull}

Appendix

...

Log File
Paste an excerpt of your log file here
@koppor
Copy link
Member

koppor commented Oct 24, 2023

Can you show to us, how your preference look like?

image

(Side note: This might be a regression comming from #10303)

@koppor koppor changed the title The command "Push entris to external application" adds a "null" prefix and suffix to an existing Citationkey in LaTex. The command "Push entris to external application" adds a "null" prefix and suffix to an existing Citationkey in LaTeX. Oct 24, 2023
@NeymanDmitry
Copy link
Author

Screenshot from 2023-10-24 17-17-42

@NeymanDmitry
Copy link
Author

It looks like this (in my picture) but I tried it like this "\cite{key1,key2}" but the result is the same.

@koppor
Copy link
Member

koppor commented Oct 24, 2023

What happens if you change to \cite{key1Xkey2} and select two entries and press Ctrl+L?

Here, I get \cite{Kopp2008bXDecker2008a}, which is fine...

@koppor koppor added the bug Confirmed bugs or reports that are very likely to be bugs label Oct 24, 2023
@koppor koppor changed the title The command "Push entris to external application" adds a "null" prefix and suffix to an existing Citationkey in LaTeX. The command "Push entries to external application" adds a "null" prefix and suffix to an existing Citationkey in LaTeX. Oct 24, 2023
@NeymanDmitry
Copy link
Author

What happens if you change to \cite{key1Xkey2} and select two entries and press Ctrl+L?

Here, I get \cite{Kopp2008bXDecker2008a}, which is fine...

In this case I got a similar result. After which I put a comma instead of X and everything began to work correctly.

@hchuanqi
Copy link

hchuanqi commented Nov 2, 2023

I encountered the seem issue, and then got back to 5.10 as workaround.

@koppor
Copy link
Member

koppor commented Nov 2, 2023

@hchuanqi Does the reset button introduced in #10569 and available at https://builds.jabref.org/main/ help?

@hchuanqi
Copy link

hchuanqi commented Nov 3, 2023

@hchuanqi Does the reset button introduced in #10569 and available at https://builds.jabref.org/main/ help?

By your suggestion and reviewing the manual exactly, I reinstalled v5.11 and modified the Cite command from \footcite (working properly in and before v5.10) to \footcite{key1,key2}, then it works fine now...

In v5.11, with previous setting of Cite command by \footcite , the push entries to external application (TeXstudio) command generated something like \cite{nullGross1995null},
while the expected output was \footcite{Gross1995}.

Before I changed the Cite command setting, I tried the reset button in your suggestion but there was no effect I could sense.

@Siedlerchr
Copy link
Member

Thank you for reporting this issue. We think, that is already fixed in our development version and consequently the change will be included in the next release.

We would like to ask you to use a development build from https://builds.jabref.org/main and report back if it works for you. Please remember to make a backup of your library before trying-out this version.

@koppor
Copy link
Member

koppor commented Feb 4, 2024

This was even fixed at the latest release version 5.12. See the CHANGELOG at https://github.com/JabRef/jabref/blob/main/CHANGELOG.md#512--2023-12-24

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bugs or reports that are very likely to be bugs
Projects
None yet
Development

No branches or pull requests

4 participants