Bug 315639 - Kile project management does not work correctly with nested documents
Summary: Kile project management does not work correctly with nested documents
Status: RESOLVED WORKSFORME
Alias: None
Product: kile
Classification: Applications
Component: user interface (other bugs)
Version First Reported In: 2.1.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-22 17:14 UTC by David Kremer
Modified: 2023-02-09 03:53 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 David Kremer 2013-02-22 17:14:25 UTC
Hello

I will give a short example to demonstrate the problem.
Let's imagine we have a root document "root.tex", which contains the preamble of a latex document and several includes/input commands into it.

It looks like that :

root.tex :
\documentclass[a4paper,12pt]{article}
%...
\begin{document}
\input{chapter1/chapter1}
\input{chapter2/chapter2}
%...
\end{document}

If you start a project with the above document as your root document, and you add chapter1, chapter2, etc, to the project, then the files chapter1.tex and chapter2.tex located in the subdirectories chapter1/ and chapter2/ will be loaded in the subtree which is rooted at the file "root.tex".

Then, if I want to put the sections of chapter 1 in a separate file, I will have :

chapter1/chapter1.tex :
\input{chapter1/section-1-file}
\input{chapter1/section-2-file}
% ....

At this point, I want also add chapter1/section-1-file.tex in the project file tree, but it stays outside, being not recognized as a part of the project sub-tree even if I add this files correctly to the current project with as a root file, the "root.tex" file located in the project directory.

I think this is a wrong behaviour, since any file which is called from a given file in a project tree should be a leaf or a sub-tree of the file from which it is called with the "\input{}" macro.

Could you set the things ok with the subtree ? I believe it should be not that much work, but it would add a lot of coherence of how project management is driven.

Thank you very much.

David

Reproducible: Always

Steps to Reproduce:
1. Create a project with the previously described subfolders and files.
2. Add all the listed files to the project
3. Observe the behaviour previously described.
Actual Results:  
The files which are called in this way are not recognized as leaf or subtrees.

Expected Results:  
The software should recognize chapter1/section-1.tex and chapter1/section-2.tex as leaf of the subtree starting at chapter1.tex and chapter1.tex should be the root of the subtree having itself a root with root.tex located in the base directory.
Comment 1 Andrew Crouthamel 2018-11-10 03:23:23 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-21 04:38:29 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2023-01-10 01:52:15 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 2023-01-25 05:05:37 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-02-09 03:53:54 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!