When I have nested folders and I use the \input command, then the LaTeX requires that all paths be relative to the master document. However, the Kile scans the document using the relative path to the current file. Due to this, the file which I have included using the input command \input instead of coming under that specific file subtree from which it was \input instead appears under the main tree. For example, I have the following tree /report-for-input-bug | |---------- main.tex |---------- subdir | | --------- file.tex | --------- input.tex Case 1: main.tex contains the following line \input{subdir/file} subdir / file.tex contains the following line: \input{subdir/input} In this case, the LaTeX program compiles properly but the Kile project tree shows input as different entity. Case 2: main.tex contains the following line \input{subdir/file} subdir / file.tex contains the following line: \input{input} In this case, the LaTeX does not compile, but the Kile shows proper project tree. The source code to reproduce the bug can be downloaded at https://owncube.com/apps/files_sharing/get.php?token=7f0b1e8d766917f96c671dc3ecdbaee7b7778955 (This is the first time I am using this service, so let me know if there are any problems.) There are two folders illustrating the two cases in it. Each folder contains a png image which shows the screenshots of that particular case in action. Reproducible: Always Steps to Reproduce: 1. Try to compile the projects 2. 3. Actual Results: There is a contradiction between Kile's approach and LaTeX's approach. Expected Results: The Kile should be able to follow the syntax followed by LaTeX without any problem.
Created attachment 70856 [details] Source code for the examples
I can confirm this wrong behaviour in the current version, i.e., kile 2.1.3-7 as packaged in arch linux. Particularly I see the annoying Case 1 where kile shows non-root files (of the same project) that are included using \input{subfolder/file} incorrectly as root documents although they should be rather subfiles.
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!