blob: b0717d0927f2ac7d13ccd5a2d4075a14b67960b2 [file] [log] [blame]
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en">
<HEAD>
<meta name="copyright" content="Copyright (c) IBM Corporation and others 2000, 2013. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1">
<META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css">
<LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css">
<title>Starting a Quick Text Search</title>
</HEAD>
<body>
<h1>Starting a Quick Text Search</h1>
<p>Quick Text Search is a convenient alternative to Search Dialong and Search View.
It provides a popup dialog that is especially well-suited to jump around the workspace
quickly using textual matches.
</p>
<p>A Quick Text Search can usually be started by pressing its keyboard shortut CTRL-ALT-SHIFT-L (
or CMD-ALT-SHIFT-L on Mac). This will popup the following dialog:
</p>
<p>
<img src="../images/quick-text-search.png" alt="Quick Text Search dialog" border="0">
</p>
<p>To run a workspace-wide Quick Text Search, simply type text in the main search field and you'll see
the list of possible matches updated live as you type. You can also select some text in a Eclipse view
or editor prior to opening the dialog. The selected text will be entered automatically into the
search box.</p>
<p>The dialog has these features:</p>
<ul>
<li>A main search box in which you can enter a search string. The string can contain <code>*</code> and <code>?</code>
wildcard characters. These characters will be interpreted in the usual way (<code>*</code> matches any
sequence of characters and <code>?</code> matches any single character).
</li>
<li>The 'In:' input allows limiting the search scope to files who's path/name matches any of
a list of patterns. The syntax is the same as that used in '.gitignore' inclusion patterns.
Multiple patterns can be entered and are separated by commas. The patterns are matched
against workspace paths. So you can use a pattern like <code>/project-name/**</code> to search files
in a specific project.
</li>
<li>
A table of 'Matching Items'. You can select items in the table by clicking on them or
using the arrow up/down keys. The contents of the table is updated in real time, as you type
in the search box.
</li>
<li>
A 'Open' button. Clicking this will open the currently selected match in a editor.
If no match is currently selected, the first match will be opened instead.
This action can also be invoked by pressing
the 'Enter' key rather than clicking the button. By default the dialog is 'modal'
and it will close upon invoking this action.
</li>
<li>
A pull-down menu provides options to:
<ul>
<li>Switch between case-sensitive versus case-insensitive matching</li>
<li>Keep the dialog open (i.e. the dialog becomes 'non-modal' and does not close after selecting an item and
opening it.</li>
</ul>
</li>
<li>
A 'Refresh' button. This can be useful to manually trigger the dialog to refresh its matches.
This may be especially useful if you are using the dialog in a 'non-modal'
way (because the non-modal dialog may remain open for extended periods of time, but its matches are not
automatically refreshed if the file content is changed).
</li>
</ul>
</BODY>
</HTML>