Bug 208866 - Bibtex completion fails when spaces included in \bibliography{} list
Summary: Bibtex completion fails when spaces included in \bibliography{} list
Status: RESOLVED WORKSFORME
Alias: None
Product: kile
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-29 13:20 UTC by Jan-Willem van de Meent
Modified: 2023-01-07 05:25 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jan-Willem van de Meent 2009-09-29 13:20:03 UTC
Version:            (using KDE 4.3.1)
OS:                Linux
Installed from:    Ubuntu Packages

Version: Kile 2.0.83 (svn 1014763)

The bibtex completion feature in Kile is really fantastically useful. There is a small issue with the parsing of the included bibtex files though. It appears that any spaces in the list cause kile to fail to recognise the included bibtex files. 

This command works as expected:

  \bibliography{file1.bib,file2.bib,file3.bib}

But completion fails for file2.bib and file3.bib when using either of these commands:

  \bibliography{file1.bib, file2.bib, file3.bib}

  \bibliography{file1.bib,% 
                file2.bib,% 
                file3.bib}

Only file1.bib is being recognised as included in the source under the project view

  Project Name
  |-file2.bib
  |-file3.bib
  |-source.tex
  --|-file1.bib

It would be nice if this could be fixed. In big projects which may have 10+ included bib files, it's really more convenient to have each file on a separate line. Moreover the current behaviour is very confusing since it will not be apparent to the user why completion is only working for the first included bib file. 

Many thanks for this great piece of software!
Comment 1 Andrew Crouthamel 2018-11-02 22:53:58 UTC
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!
Comment 2 Andrew Crouthamel 2018-11-16 02:49:09 UTC
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?

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-08 23:51:26 UTC
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!
Comment 4 Bug Janitor Service 2022-12-23 05:22:50 UTC
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!
Comment 5 Bug Janitor Service 2023-01-07 05:25:37 UTC
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!