<< Search in files [69/117] >>

Search in files

Home / Projects / PIEdit / PIEdit-Documentation / Search in files

Search in files

With the help of this very powerful function (particularly with larger programming projects) it is possible to scan e.g. several source code files for a certain text and/or a regular expression. The results of the search are represented here in their own text field at the lower edge of the editor.
With looking for by means of regular expressions the search results become sorted according to the 1. Capturing Group. I.e. one can look e.g. for all methods of a Java program, and let it view sorted.
Manner of operation: If now one clicks the Button ( search_in_files

), one can determine in a coming up window, where to be looked for (file or directory), and which type of file to be scanned (indication of suffix: Also several suffixes can be indicated separately by a blank).
Over a checkbox can one determine whether an individual file or a complete directory should be scanned. In addition can be indicated whether a complete directory tree recursively should be scanned.
File/directory input field is set on the straight opened file.
The search text is set on the straight selected text, if something is selected.
The expenditure for search result appears at the lower edge of the editor. The expenditure for result consists here of the file name, the line number in that the text occurs, and the corresponding complete line in that the text found.
Through doubleclick on a result the appropriate file loaded (if it is not yet open), and the line in that the search text occurs indicated.
By right-click the search result window can be updated.
Already open files are scanned directly.
At the lower edge several pre-defined regular expressions are selectable.
Areas of application (examples):
- To "clearing up" programs
- Renaming of method names
- To finding out, where which function is called
- Where which exceptions (e.g. searchtext= "exception") are treated
- Navigation over the methods of a Java program (particularly practical with large programs)
- Search for catch-constructs with sorted listing of the type of exception (IOException, BadLocationException, etc.)
- Statistics: e.g. a project has how many Java classes altogether
- Scanning text databases
- and many different

JSWins (JavaScript-Desktop-System)