Bug 235698

Summary: Regression in 2.1b4: kile does not identify the master document automatically while opening project
Product: [Applications] kile Reporter: Andrea <andrea.turrini>
Component: generalAssignee: Michel Ludwig <michel.ludwig>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 2.0.85   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Andrea 2010-04-29 10:43:30 UTC
Version:           2.0.85 (using 4.4.2 (KDE 4.4.2), KDE:KDE4:Factory:Desktop / openSUSE_11.2)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.31.12-0.2-desktop

I have just created by myself the rpm packages for kile 2.1b4 in the same way I generated rpms for kile 2.1b3 (using the same spec file and kde 4.4.2 from opensuse11.2 - factory repository).

If I install 2.1b4 and open an existing project (also created with kile 2.1b4), then kile is not able to identify the master document/main file if it is not opened with the project. A consequence of this is that the autocompletion does not work for commands defined in a different file belonging to the project and included by the main file using the \input{} command.

If I simply open the main file (without marking it as master document using the specific button), then autocomplete starts to work again.

This is also highlighted by the small icon near file names in the "File and Project" side view: for just opened projects, the icon of all files is a small yellow box, while if I open the main file (clicking on it in the "File and Project" view or using the File menu), then the icon becomes a TeX-red box. Similarly, also the input-dependency between file is correctly updated since initially almost all files are put in the same level.

On the contrary, using kile 2.1b3 the main file is correctly identified even if the icon is a yellow box and the file is not opened manually or with the project.
Comment 1 Michel Ludwig 2010-04-29 10:58:00 UTC
Thanks but this has been already been reported in bug 233667 (and has been fixed in SVN).

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