FindInFiles-addon
Add-on for Sublime Text's Find-In-Files-feature
Details
Installs
- Total 56
- Win 29
- Mac 22
- Linux 5
Jan 31 | Jan 30 | Jan 29 | Jan 28 | Jan 27 | Jan 26 | Jan 25 | Jan 24 | Jan 23 | Jan 22 | Jan 21 | Jan 20 | Jan 19 | Jan 18 | Jan 17 | Jan 16 | Jan 15 | Jan 14 | Jan 13 | Jan 12 | Jan 11 | Jan 10 | Jan 9 | Jan 8 | Jan 7 | Jan 6 | Jan 5 | Jan 4 | Jan 3 | Jan 2 | Jan 1 | Dec 31 | Dec 30 | Dec 29 | Dec 28 | Dec 27 | Dec 26 | Dec 25 | Dec 24 | Dec 23 | Dec 22 | Dec 21 | Dec 20 | Dec 19 | Dec 18 | Dec 17 | |
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Windows | 0 | 1 | 0 | 0 | 0 | 2 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 2 | 0 | 3 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 1 | 1 | 1 | 0 | 1 | 1 | 0 | 0 | 0 | 0 | 0 | 1 | 1 |
Mac | 0 | 0 | 2 | 0 | 2 | 0 | 0 | 2 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 2 | 1 | 2 | 0 | 0 | 1 | 0 | 1 | 1 | 0 | 2 | 0 | 0 | 0 | 1 | 0 | 0 | 1 | 0 | 1 | 2 | 1 |
Linux | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0 | 0 |
Readme
- Source
- raw.githubusercontent.com
Sublime Text - Find in Files hacks
The plugin with the following features:
Make all lines in a find-in-files result buffer double-clickable.
Bind
<enter>
to do the same thing, namely go to that line. (But also set the column, well … just the complete selection.)Bind
,
and.
to go to the previous or next match staying in the result buffer. Just move the cursor (“navigate”) around. Wraps at the edges but stays in the same search. [1]But you can also bind
fif_addon_prev_match
andfif_addon_next_match
on your own.Bind
ctrl+enter
to open a preview, side-by-side. The preview will update when you navigate around. Both,enter
andctrl+enter
will close the preview. As there is no side-by-side to a results panel, this will only work for result buffers. Also, if you already use the newish “find_in_files_side_by_side” setting, there is no real difference as you already opted-in to always use a side-by-side view. (Hint: Turnfind_in_files_side_by_side
off and use the preview feature here.)Bind
ctrl+r
[2] to refresh the view, t.i. redo the last search. Hm, :thinking:, maybe we can change that and redo the search the cursor is currently in. But for now it is the last search in the buffer.Bind
alt+c
[3] to toggle case sensitivity,alt-w
to toggle the whole word flag and redo the search immediately.Bind
alt+r
to toggle regex mode. The pattern will be escaped/unescaped and the panel will open to edit the pattern further.Bind
+
and-
to change the number of context lines. For ease of use, hit-
repeatedly as a toggle between no context and your default, or if your default is no context between that and some context.If you reuse the result buffer (and it is a tab, not the panel thing at the bottom of the window), the tab moves with you so that closing the tab (aka
ctrl+w
) brings you to the view where you initiated the search.Add the search summary (e.g. “2 matches across 2 files”) to the search header line (“Searching 9 files for …”)
Re-bind
ctrl+shift+f
to immediately do the search if you have exactly one selection. Exclude untitled buffers in that case. (You can turn this off by setting"leave_my_keys_alone.FindInFiles-addon": true
in the user preferences.) Sets “whole_word” if you've selected a whole word, unsets it if that's not the case. Also normalizescase_sensitive
andregex
tofalse
.
[1] You know, the result buffer can be re-used and then holds the results of multiple searches.
[2] On Linux and Windows, F5
can be used as well.
[3] On Mac, the standard super+alt
modifier is used.
I personally like it when escape
closes the results view. You can add that
to your own key bindings. E.g.
{
"keys": ["escape"],
"command": "close",
"context": [
{ "key": "selector", "operand": "text.find-in-files" },
// negate all default escape contexts, even if they're not likely to ever match
{ "key": "auto_complete_visible", "operator": "not_equal" },
{ "key": "has_prev_field", "operator": "not_equal" },
{ "key": "has_next_field", "operator": "not_equal" },
{ "key": "num_selections", "operator": "equal", "operand": 1 },
{ "key": "overlay_visible", "operator": "not_equal" },
{ "key": "panel_visible", "operator": "not_equal" },
{ "key": "popup_visible", "operator": "not_equal" },
]
}