Bug 156363

Summary: Auto-completion stops to work when unkown reference is used
Product: [Applications] kile Reporter: Andrea <andrea.turrini>
Component: generalAssignee: Michel Ludwig <michel.ludwig>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Andrea 2008-01-22 10:36:32 UTC
Version:           2.0.0 (using 3.5.8 "release 33.1" , openSUSE )
Compiler:          Target: i586-suse-linux
OS:                Linux (i686) release 2.6.22.13-0.3-default

Hi all,
I've noted that when a reference or citation is misspelled, then the auto-completion of references, citations and commands is no longer available. 

For example, consider this document:

\documentclass[a4paper,10pt]{article}
\usepackage[latin1]{inputenc}
\begin{document}
\section{test}\label{sec:test}

In section~\ref{sec:test}
\end{document}

When I type \ref, the popup of command completion works and when I open the bracket, sec:test is proposed as possible completion of the reference. If I choose it or if I type it correctly, then there are no problems. Instead, if I misspell the reference, then there is no way to use again the auto-completion for commands, references and citations. The only way I found to restore auto-completion popups is to close and reopen kile.

I can reproduce this problem using projects or single files not connected to a project. And the problem is system-wide: when it is activated, auto-completion is disabled for all open files and projects.

Sometimes auto-completion seems to stop to work even when no \ref or \cite commands are used, but I've not yet found a possible activation sequence and, at the moment, I ignore causes in this case. Furthermore, no error messages are provided, when I start kile from command line and I activate the problem using a misspelled reference.

I don't know if this problem is a real bug or simply an error in some kile's configuration, but it is quite boring.

Regards,
Andrea
Comment 1 Andrea 2008-01-22 11:41:29 UTC
I think that this problem can be related to this bug report: http://bugs.kde.org/show_bug.cgi?id=155044

Sorry for the possible duplication of the bug, but I've not seen the other bug before to post this one.
Comment 2 Michel Ludwig 2008-01-22 12:12:10 UTC

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