Bookmarks & notes
Two ways to mark up code. Both are scoped per project and stored outside your files.
Bookmarks
Toggle a bookmark on a line with C-c m, or from the editor’s right-click menu
(Add / Remove Bookmark, acting on the line you clicked). It shows a gutter
marker and can carry a short note. The marker itself is display-only: clicking
the gutter used to toggle a bookmark, but the breakpoint strip and the Run ▶ are
narrow targets inside that same gutter, so a slightly-off click added a stray
bookmark instead of hitting what you aimed at.
| Action | Command | Default key |
|---|---|---|
| Toggle bookmark | bookmarks.toggle | C-c m |
| Next / previous in file | bookmarks.next / previous | C-c ] / C-c [ |
| Jump (cross-file) | bookmarks.jump | M-g b |
| Set a mnemonic | bookmarks.setMnemonic | (palette) |
Mnemonics
A bookmark can carry a single character, and that character becomes a
shortcut that jumps to it from anywhere in the project. Set one with
bookmarks.setMnemonic on the bookmarked line; an empty answer clears it.
A mnemonic is unique within a project — 3 means one place, not one place
per file — because the chord is a name for a location, and a name that resolves
to several locations is a menu, not a shortcut. Assigning one that’s already
taken simply moves it, which is also the only behaviour that needs no error
message.
Each of the ten digits gets its own command, bookmarks.gotoMnemonic0 through
bookmarks.gotoMnemonic9, so you can bind each to a single chord in
Settings → Keymap — one keystroke, no prompt, which is the entire point.
Letters work as a mnemonic too and are reachable from the bookmarks picker; only
the digits have a bindable command of their own.
The panel shows the mnemonic first on the row. It’s the only part of a bookmark that is otherwise invisible, and a shortcut you can’t see is one you won’t remember assigning.
The Bookmarks tool window (M-2) lists them across files in an order you
control: reorder a bookmark or a whole file group with Alt+Up/Down, a right-click
Move, or drag and drop. It groups by project, always showing the General
(no-project) group plus the current project, with a Show all projects
toggle to reveal and jump to every other project’s bookmarks. Bookmarks follow
their content through edits, and they’re re-anchored to the saved line text when
a file changes outside the editor, so they survive external edits. They live in
bookmarks.json.
Personal notes
Personal Notes attach an annotation to a word, line, or range, stored outside the file. They’re built for read-only, generated, or shared code where you can’t leave a comment in the source. Notes are off by default; enable them in Settings → Application.
| Action | Command | Default key |
|---|---|---|
| Add a note | notes.add | C-c n |
| Edit the note at the caret | notes.editNote | C-c e |
| Resolve / reopen the note | notes.toggleResolved | (palette) |
| Next / previous | notes.next / previous | (palette) |
| Jump (cross-file) | notes.jump | M-g n |
| Full-text search | notes.search | M-g s |
| Delete note on the line | notes.delete | (palette) |
| Export notes to JSON | notes.export | (palette) |
Add one from the editor right-click menu (Add Personal Note / Add Note to
Selection) or C-c n. A noted span gets a soft highlight and an amber start
marker you can click to edit, and hovering it shows the note body rendered as
Markdown. Note bodies are edited in a multi-line dialog (Ctrl/Cmd+Enter saves)
that honors your keymap’s caret-movement keys.
Notes track their anchor through edits and re-locate themselves by surrounding
text when a file changes externally, marking themselves orphaned only if the
anchor truly disappears. The Notes tool window (M-5) groups them per file
with a filter, and like Bookmarks it groups by project, General plus the current
one, with a Show all projects toggle. They live in notes.json. A second
toggle, Show note indicators, hides just the gutter glyph and highlight while
keeping notes on.