Search and traces

Search the folder's indexed text files, and turn a pasted error into a jump list.

Search in Rip has two homes. The search bar finds text in the current file. The search tab finds text in the folder's indexed files. A third tab, Locations, turns any text with file references into a list you can jump through.

Search the folder#

Press FCtrl+Shift+F. A search tab opens with a query field. Results appear while you type, grouped by file, with each match highlighted. Rip searches on background threads, so a long query never blocks the editor. If you search while Rip still builds the index, edit the query to search again. The search skips files that Git ignores, including through the global ignore file, and files that a .ignore file names. It also skips the .git, target, and node_modules folders, symbolic links, binary files, and files over 4 MiB. It shows up to 250 matches per file and 5,000 in total, and the index covers up to 200,000 files.

↓↓ and ↑↑ move through the results. ↩Enter opens the selected match in the editor at that line.

To find text in one file, use the search bar. Editing describes it.

Locations: paste a trace#

An error message, a stack trace, or compiler output names files and lines. Copy that text and press JCtrl+Shift+J. The Locations tab opens and lists the path:line:col references it finds, up to 500. A reference to a text file under 8 MiB gets a few lines of context, when the line exists. Rip reads the clipboard when the tab is new or empty. The text must name at least one file and be under 200,000 bytes. To paste a new trace, select the old text in the tab first, then paste. Rip matches a bare file name against the index. If the tab opened while Rip still built the index, edit the text to match again.

↓↓ and ↑↑ move through the list. ↩Enter opens the file at that line, or at the last line when the file is shorter. A reference that matches no file stays in the list, but ↩Enter does nothing on it. ⎋Esc returns to the editor.

Keys#