Bug 120254 - Alternative specification of BiBTeX input files not supported
Summary: Alternative specification of BiBTeX input files not supported
Status: RESOLVED DUPLICATE of bug 179849
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR wishlist
Target Milestone: ---
Assignee: Jeroen Wijnhout
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-16 18:02 UTC by José Luis Tallón
Modified: 2009-01-08 22:18 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description José Luis Tallón 2006-01-16 18:02:01 UTC
Version:           1.8.1 (using KDE KDE 3.5.0)
Installed from:    Debian testing/unstable Packages
OS:                Linux

It would be *very nice* it BibTeX files could also be marked manually. That is, for any given file added to the project and which has the .bib extension, enable a checkmark in its "properties menu"(the one invoked with a right click); My suggestion for this checkmark is "Use as bibliography".

My expected behaviour: that Kile would parse this/these files so that they are available for use with the \cite{} command's popup list.

This solves the problem when one is using a bibliography package which does not use the \bibliography command to find its input (and i don't expect Kile to have a comprehensive list of all such packages)

Thanks
Comment 1 Thomas Braun 2006-01-18 12:51:48 UTC
Hi José,

currently we have this comprehensive lists (e.g. like \ref, \eqref, ... ).
And we have started to give the user the possibilty to add new commands that have the same meaning than existing. See Configure Kile->Latex->Complete->
Configure Commands.
We have to ensure that the alternative commands obey the _exact_ same syntax as the \bibliography command.
If they have the same syntax, the only thing I need is a list of these commands.
I will then hardcode them into kile (and perhapse include this into the kile 1.9 relase), and we will make them configurable in a future release.

For now you can also use the following (ugly) hack:
\iffalse
\bibliography{bibs,...}
\fi
Then latex won't read the bibs but the kile structure view will identify them (because kile doesn't recognize it as an comment) and so add them to the codecompletion.

Thanks for the report
Thomas Braun
Comment 2 José Luis Tallón 2006-01-18 13:00:12 UTC
Thomas Braun wrote:

[bugs.kde.org quoted mail]
I am using the btSect package. That means the bibliography file is
specified like this:

\begin{btSect}[<style>]{<bibfile>}

(and you are interested in the <bibfile> command)

See an actual example below:

-------- 8< ----------
\chapter*{\bibname}
\markboth{\bibname}{\bibname}
\addstarredchapter{\bibname}
\bibliographystyle{unsrt}
\begin{btSect}[unsrt]{biblio/Oasis2}
%\renewcommand{\thebtauxfile}{\jobname.Oasis2.bib}
\section*{\bibname}
\btPrintCited
\newpage
\section*{\bibname~not cited}
\btPrintNotCited
\end{btSect}
 
\begin{btSect}[unsrt]{biblio/RFCindex}
%\renewcommand{\thebtauxfile}{\jobname.RFCindex.bib}
\section*{\bibname~to RFCs}
\btPrintCited
\end{btSect}
-------- 8< ----------

>For now you can also use the following (ugly) hack:
>\iffalse
>\bibliography{bibs,...}
>\fi
>Then latex won't read the bibs but the kile structure view will identify them (because kile doesn't recognize it as an comment) and so add them to the codecompletion.
>  
>

Thanks, i will use this.

However, i still think that having at least the possibility to manually
design files as a source for completions is a superior approach.

>Thanks for the report
>  
>

Thank you for making Kile such an incredible tool :-)

    J.L.
Comment 3 Peter Ansell 2006-03-25 04:55:51 UTC
Resolving the following problem could also be factorised into a plan for fixing this bug.

A bibtex file is added as a child of only one file in
a project. For this file \cite{} commands autocomplete
fine with the keys in the file.

I use the same database over many files in a project
and would like to have autocomplete working for all of
the files.

The slightly strange thing I think is that I have even
tried setting the master document to a file other than
the one which is autocompleting properly and it still
doesn't work for that file.

Thanks,

Peter
Comment 4 Thomas Braun 2009-01-06 22:06:20 UTC
I would like to close this bug and add complete support for biblatex instead.

Any strong objections?

bye,
Thomas
Comment 5 Thomas Braun 2009-01-08 22:18:32 UTC

*** This bug has been marked as a duplicate of bug 179849 ***