| Summary: | Multiple citations in a single \cite{} do not auto-complete from bib file | ||
|---|---|---|---|
| Product: | [Applications] kile | Reporter: | mmdanziger |
| Component: | editor | Assignee: | Michel Ludwig <michel.ludwig> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | tprotopopescu |
| Priority: | NOR | ||
| Version First Reported In: | 2.1.3 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
This feature works for me, using 2.1.3. Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone! Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |
Often one wants to cite multiple citations in one \cite command so that they appear as "previous research [1-20]" in the final compiled file. To do so you type \cite{einstein1,einstein2,heisenberg1,higgs2}. In Kile, only the text input immediately following the { triggers a lookup in the project's bib file to suggest an auto-complete. Since \cite takes multiple comma-separated arguments, a comma following a { should trigger auto-complete as well. Currently, I go to the beginning after every citation reference then copy paste the reference to the desired position in the chain. When there are 10 or more citations, this can become very tiring. Reproducible: Always Steps to Reproduce: 1. Create a project with a bib file 2. type \cite{ref1,ref2} 3. notice that ref2 is not suggested in auto complete Actual Results: No auto-complete for references after first reference Expected Results: Auto-complete from bib file for every term following { OR , following the \cite command. This is sort of a feature request but it's also an implemented function that does not work when it should work, so that would be a bug. I've classed it as "normal bug" for now and I leave it to the mod's discretion whether to reclassify it as a feature request.