[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kdevelop-bugs
Subject:    [Bug 160143] find in files: search in included files
From:       Adrián Chaves Fernández <adriyetichaves () gmail ! com>
Date:       2012-08-04 8:29:20
Message-ID: bug-160143-40295-uFGCDvNFVQ () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=160143

Adrián Chaves Fernández <adriyetichaves@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |adriyetichaves@gmail.com

--- Comment #9 from Adrián Chaves Fernández <adriyetichaves@gmail.com> ---
Hi,

I have been trying to sketch a specification for this feature request. I've got
the following points:

- Add the "Included Files" option to the "Location(s)" drop-down list in the
Find In Files dialog.
- At the right side of the "Recursive" checkbox, there should be a "Depth"
SpinEdit control to indicate a inclusion depth level, with the following
possible values: Infinite (as recursively currently behaves), 1 (only included
from the current file), 2 (included from this file and from files included from
this file), etc.
  - The control would be disabled (grayed out) if the "Recursive" field is
unmarked.
  - For coherency, the Depth field should also be implemented for the rest of
the existing "Location" values, based on directory levels (instead of inclusion
levels).
- The rest of the fields in the Find In Files dialog should work fine with the
new Location option.
  - To be noted that the "Limit to Project Files" checkbox applies to this new
option as well.
- The new Location option should only be available (listed in the drop-down
menu) when the current file supports inclusion.
  - It should be available, for example, for C++ (#include), PHP (include,
require, etc.) and Python (import).
  - It should not be available, for example, for .txt files.

Am I missing something?

Also, writting them a couple of questions araised:
- If the current file supports inclusion but there is no actual inclusion
statement in it, should the drop-down list for the search location provide this
new option?
- If the current file supports inclusion and has inclusion statements but they
are all unresolved, should the drop-down list for the search location provide
this new option?

What do you think?

-- 
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
KDevelop-bugs mailing list
KDevelop-bugs@kdevelop.org
https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-bugs

[prev in list] [next in list] [prev in thread] [next in thread]