Editora 0.19.0 docs. You are reading an archived version, kept so links from that release keep working. Read the 0.21.0 docs →

Navigation & search

This page covers the fuzzy pickers and search commands that take you anywhere without the mouse.

For moving around code in particular (symbols, definitions, the scope you’re in), see Code navigation.

Command palette

The command palette (palette.show) lists every command by name. Type a few letters (matching is fuzzy, see How matching works), press Enter, and it runs.

Each row shows the command’s current keybinding, and the highlighted row’s description appears under the list. The docs key opens that command’s documentation in your browser: C-h in the Emacs keymap, and F1 or Shift+F1 in the keymaps that already use Ctrl+H or F1 for something else. The hint line along the bottom names the key that applies.

A command that can’t run right now stays listed and dimmed, with an explanation of what would enable it, rather than disappearing.

Search Everywhere

Search Everywhere (search.everywhere) is one picker over commands, project files and symbols, so you can type the name of the thing instead of first deciding which of Editora’s five pickers, each behind its own chord, it lives in.

A leading sigil restricts it to a single source when you already know:

These are VS Code’s sigils, chosen because the muscle memory for them already exists.

Results stay grouped by source rather than interleaved on raw score. The sources differ in size by orders of magnitude (tens of thousands of symbols, thousands of files, a few hundred commands), so a flat merge would fill the list from the biggest source and push the other two out. Each source gets a guaranteed share (8 rows, 24 overall), the groups compete on their best result rather than their bulk, and the overall cap trims a group’s tail instead of dropping a source outright.

A single-source query is not capped. When a sigil restricts the picker to one source, or when the query is empty (which lists commands), there is no smaller source for a large one to crowd out, so you get the whole list. Before 0.14.0 a > search returned at most eight commands, fewer than the command palette it stands in for.

An empty query lists every command and touches no other corpus, so opening it is a browsable list rather than a blank box. A bare sigil is a scope rather than an empty query: it names what it will search and walks nothing.

A single-line selection seeds the query, the same way the find bar and Find in Files do.

The symbol half is backed by Editora’s own project symbol index, so it works with no language server installed.

Commands you can’t run yet

A command whose feature is switched off is listed, greyed, with an explanation naming the setting that would enable it, the same way the command palette treats it. In 0.13.0 such commands were omitted, which is tidier in a short mixed list but means you never learn the command exists. Greyed rows sort after everything you can run, and both the cursor and the mouse step over them.

The highlighted row’s description appears under the list, and the docs key (C-h in the Emacs keymap) opens that command’s documentation in your browser. Both match the palette. The hint line along the bottom names them, alongside C-n/C-p.

Opening it

M-S-x was chosen because it sits beside M-x. (Through 0.13.0 the command had no chord in any bundled keymap, so the only way to reach it was the palette.)

It can also take over the command palette’s shortcut: switch on Palette shortcut opens Search Everywhere under Settings → Interface → Pickers, or run view.togglePaletteSearchEverywhere. It is off by default, because which picker a chord opens is muscle memory and a release should not change it for you. Nothing is lost by switching: an empty query lists every command exactly as the palette does, and typing also reaches project files and symbols. Search Everywhere keeps its own chord either way.

How matching works

Every picker scores what you typed rather than only testing whether it matched, and emboldens the characters responsible for the match.

• Contiguity, boundaries and case. A character earns a bonus for landing on a word boundary (the start, after a separator, a camelCase hump, a letter→digit transition) or for continuing a run. Spread-out matches are penalized. So an exact prefix beats an acronym beats a scattered subsequence.
• The best alignment, not the first. The match is computed by dynamic programming rather than greedily left to right, so mc matches the two humps of MainController rather than whichever c comes first.
• Several terms, any order. Whitespace splits the query into terms that must all match, in any order, so toggle git finds Git: Toggle Blame.
• Paths know their basename. The Project tree’s filter scores the whole relative path, so a query can name a directory as well as a file.

Grouped and structural lists (build actions, branches, the Structure tree) use the same matcher but keep their own order, because a tree that reorders under a filter is harder to read.

Jump pickers

Each of these opens an in-scene picker with a footer legend of its keys. Type to filter; Enter opens.

The pickers share styling and dirty-file markers, so an unsaved buffer shows the same dot you see on its tab.

The file finder

C-x C-f opens an Emacs find-file-style path finder with prefix autocomplete. Type and press Tab to complete, Enter to descend into a folder or open (or create) a file. There’s a matching folder finder for picking a directory.

The tab switcher

C-x C-b (switcher.show) opens an IntelliJ-style switcher over the open files, listed in tab order with the current tab preselected. C-n / C-p or the arrow keys move through the list, releasing Ctrl or pressing Enter switches, and C-g or Esc cancels. The chord is the Emacs keymap’s; the other keymaps leave the command unbound, so run it from the palette or bind it in Settings → Keymaps.

Find in the current file

C-s / C-r open the Find/Replace bar at the top of the editor. It searches as you type (incremental), highlights every match, and shows a “{n} of {total}” count. A repeated C-s / C-r cycles to the next or previous match, and C-g closes the bar. Case, regex, and whole-word toggles are on the bar, along with AB (preserve case) and Sel (find in selection); a clear (✕) button empties a field in one click.

Preserve case recases each replacement after the text it replaces, so replacing foo with bar rewrites FOO as BAR and Foo as Bar instead of flattening everything to lowercase. snake_case and kebab-case are cased per segment. Find in selection is picked up automatically when you open the bar with a multi-line selection, scoping both search and Replace All to it and following the region as you edit; a single-line selection seeds the query instead.

Replace understands regex capture groups: search (\w+)_(\w+) and replace with $2-$1. A replacement naming a group the pattern doesn’t have reports the error and leaves the buffer untouched. In literal (non-regex) mode $ is inserted verbatim. Alt+Enter puts a cursor on every match at once (see Multiple cursors).

Open the bar in replace mode with Ctrl+H in the CUA, Sublime and VS Code keymaps or Ctrl+R in IntelliJ (Option+Cmd+F and Cmd+R on macOS). The Emacs keymap has no chord for it: there M-% runs query-replace instead, the replace-with-confirmation loop, and the find bar’s own replace is still on the bar and in the palette.

Occur

Edit: Occur… (M-s o) lists every line in the current buffer matching a regular expression in a keyboard picker, and picking one jumps to it. It is the buffer-scoped counterpart to Find in Files, and the picker’s own filter narrows the list further as you type.

Find in files

C-S-f opens the Find in Files tool window and focuses it. It searches the active project (skipping dot-dirs, oversize, and binary files) plus the in-memory text of open buffers, so unsaved edits are included. Results are grouped by file; Enter or double-click jumps to a match. Case, regex, and whole-word apply here too.

Replace in files rewrites matches across the project after a confirmation: open buffers are edited in-memory (undoable) and closed files are rewritten on disk, preserving their line endings. The search re-runs afterward to refresh the panel.

There’s also a lightweight Find in Files popup (search.inFilesPopup) if you prefer a quick, keyboard-first search without opening the tool window.

Folding

The gutter carries a fold chevron beside every foldable region. Beyond clicking it:

Fold Level n collapses everything at that nesting depth, like VS Code’s Ctrl+K Ctrl+1..7. Fold Recursively collapses the region at the caret and everything nested inside it, and unfolding recursively reveals the whole subtree. The three Go to … Fold commands move the caret to a fold header, revealing it first if it is hidden. None of these has a default key; bind them from Settings → Keymaps.

Folds of your own

Fold the selection creates a fold range from whatever lines you picked, with no syntactic basis. Unlike a detected region, which is recomputed from the text as you type, a manual range is tracked through your edits, and it persists across restarts with the rest of your session. Remove Manual Fold Ranges clears them for the file.

Fold All Block Comments and Fold All #region Markers fold exactly those. The marker families recognized are //#region, //region, #region, # region, #pragma region, <!-- #region --> and --region; Markdown and Markwhen are excluded, since # region there is a legal heading. Fold All Except Caret collapses everything but the block you are in.

All of these merge with the folds Editora detects, and with any a language server reports, rather than replacing them.

Where a language server is running, the fold regions come from the server rather than from brace and indent scanning, so import blocks and javadoc fold as single regions. Collapsed regions are saved per file and restored with your session.

Back and forward

Jump around and step through your navigation history with Go: Back (nav.back) and Go: Forward (nav.forward), like a browser’s back/forward for the caret.

Recent Locations

Go: Recent Locations… (nav.recentLocations) lists the session’s trail newest-first, each row showing the line you were on. A location such as Foo.java:214 says nothing about why you were there, and the line’s text usually does.

It reads the same trail Back walks rather than keeping a second log, so the picker and Back can never disagree about where you have been.

The picker also previews: the highlighted row is shown in the editor as the selection moves, and dismissing the picker puts everything back where it was. Without that restore, arrowing through a list and pressing Escape would leave you wherever the cursor stopped. Preview navigates without taking focus and without recording history, so browsing a picker can’t itself become something to navigate back through, and a location whose file isn’t open lands in the preview tab, so a list of twenty locations costs one tab rather than twenty.

AceJump

M-g j labels every visible occurrence of the next character you type. Type a label to jump the caret there. Esc or C-g cancels. It’s the fastest way to move the caret to something you can see. Line mode (nav.aceJumpLine, M-g L) labels every visible line so you can jump straight to one.

Closing tool windows

M-g closes a focused tool window (any of them) and returns focus to the editor. View: Close Current Tool Window (view.closeFocusedToolWindow, C-x 0) does the same as a regular command.