[0.27.0] - 2026-11-05
Added
-
Java debugging: Show toString() values. Settings → Debugging → Java has a switch (on by default) for the
toString()text after each object in Variables, watches, inline values and hover. Values load within a 1.5 s budget per stop; past it a row reads “(toString() not loaded yet: click to load)” and loads on a click, Enter or expanding it. -
Python: quick fixes and format on save. Code Actions and the lightbulb on a Python error offer Import X (from Pyright, else the standard-library module a common name comes from), Remove unused import and Ignore on this line (
# pyright: ignore[rule]); Pyright itself gives none. Ruff or Black can format a Python file after an explicit save (Settings → LSP → Python → Format on save, off by default). -
Python sub-projects get their own Pyright. A folder inside a project with its own
pyproject.toml,setup.py,setup.cfgorpyrightconfig.jsonis analysed by its own Pyright, with its own.venv,src/and[tool.pyright]; a uv workspace member shares its workspace’s. Problems → Whole project now checks every Python file, not only the open ones. -
Starlark, Cython and SCons files open with Python highlighting (BUILD.bazel,
.bzl,.star, Tiltfile,.pyx/.pxd/.pxi, SConstruct/SConscript,.pythonrc), and ipython, graalpy, micropython and pythonw shebangs are recognised. -
The Map’s Project overview card has −/+ and opens first. Like a file’s preview card, its title bar has −/+ to make its text smaller or larger; the next overview opens at the same size. It now opens before the project’s own column, the way the map flows — left of it left to right, right of it right to left, above it top to bottom, below it bottom to top — and the map moves aside just enough to make room, instead of the card covering the panel’s far side.
-
Find File opens a folder as a project. In the Find File popup (C-x C-f in Emacs), C-d opens the highlighted folder as a project instead of descending into it. With the field ending in a separator and the highlight not moved, it opens the folder being listed; on a file, the folder the file is in. The legend shows the key when project support is on and the keymap lets C-d reach the popup (it is a global command in the IntelliJ macOS keymap, Start Debugging, so the popup leaves it alone there).
-
JavaScript and TypeScript: ESLint, Prettier/Biome and actions on save. A project’s own ESLint (from
node_modules, with aneslint.config.*,.eslintrc*orpackage.jsoneslintConfig) now checks JS/TS files when they are shown, after a pause in typing and on save; its problems join the TypeScript server’s (sourceeslint) in the squiggles, the counter and the Problems window. Its fixes and suggestions are in Code Actions, and ESLint: Fix All Problems applies every automatic fix. Format Document uses the project’s Prettier (when the project uses it) or Biome (with abiome.json), else the TypeScript server as before (Settings → LSP → TypeScript → Formatter); a selection is formatted by Prettier’s range. Organize imports, ESLint fixes and format can run after an explicit save, as one undo step. All of them run only in trusted folders; an untrusted one says so once, with Trust Folder. Doctor shows the project’s ESLint, Prettier and Biome. -
The Linux downloads are signed. Every
.deb,.rpm,.AppImageand.tar.gzhas an OpenPGP signature beside it (.asc), by the key attached to the release aseditora-signing-key.asc— the same key that signs Termina’s and Torrenta’s. The.rpmand.debare signed inside as well, forrpm -K, dnf anddebsig-verify. Check a download withgpg --verify <file>.asc <file>. -
Project Map: a Structure column on file previews. A file preview card whose file has an outline has a Structure button in its title bar. It sticks the file’s Structure column beside the card — the same declarations as the Map’s own Structure column, as an indented list, coloured as the editor colours them and as wide as the longest name needs — and clicking a method or type (or Enter on it) opens its declaration preview beside the column, tied to its row by a connector line. It moves, resizes and zooms with the card, works even when the file’s row is filtered or scrolled off the map, and the card’s sticky notes stand past it.
-
Project Map: declaration previews open narrowed. A method or type preview’s Open now opens the file in the editor narrowed to that declaration, as Open Narrowed does.
-
Project Map: close one sticky note. Each Personal Note stuck on a preview card has a × that closes just that note on the card; the note stays saved and comes back when the card’s notes are shown again.
-
Project Map: find anything in a big project (Map review 3).
- The Map’s search covers the whole project, however large or deep: it filters a list of the project’s files built
once and kept current, instead of walking the disk on every keystroke (Kubernetes: every
types.go, 6–15 ms a query). On an SSH project the list comes from one command on the host, with.gitignoreapplied. - Folders match the search, and a folder match is selected and opened. A query with
/matches the path (core/v1/types.go,cmd/kube-scheduler); a trailing/finds folders only;#namefinds files only;@namefinds declarations (symbol index, plus the language server where one runs) and shows the hit in its file’s Structure column. - A results strip under the search field counts the matches (“3 of 49”, “partial” when the search did not reach the whole project), with previous/next buttons and a list of every match. Enter / Shift+Enter in the field and F3 / Shift+F3 step through them, and Ctrl+Enter (Cmd+Enter on macOS) opens the current one. A broad search opens the folders of the best 30 matches; the rest stay in the list.
- The Map window has its own status line: everything the Map has to say appears there, not in the editor window. Ctrl+F (Cmd+F; C-s in Emacs) in the Map window focuses “Search the map…”.
- The Map’s search covers the whole project, however large or deep: it filters a list of the project’s files built
once and kept current, instead of walking the disk on every keystroke (Kubernetes: every
-
Project Map: orientation (Map review 3).
- A Project overview card opens on a project’s first Map open and from ⋯ → Project overview: the README, build system and modules, languages, top-level folders with file counts, likely entry points, and the test and docs folders. Module folders carry a badge, and folder tooltips give the project-relative path and what they hold.
- Gitignored, dependency, vendored and generated (
linguist-generated) files and folders are dimmed, with the reason in their tooltip; ⋯ → Hide ignored and generated takes them off the map. - Zoomed below 60%, columns become labelled blocks (title, item count, matches); Fit and zoom go down to 15%, and the overview is never narrower than 90 px. ⋯ → Compact rows gives denser rows, and each column then shows its filter, Show hidden and lock only while it is in use.
-
Project Map: keep your bearings (Map review 3).
- Back and Forward go through the places you visited (files opened or previewed, search landings, reveals, breadcrumb jumps) instead of every keystroke; right-click either button for the list.
- The Map remembers your exploration per workspace: open folders, the selected row, Back/Forward, zoom and pan, and open code cards come back after a restart (workspace schema 27 → 28).
- Type a name to jump to a row in the current column; End and Home go to its last and first rows (Shift+Home to the first column’s first row).
- Default keys open the Map (Alt+Shift+1, ⌘⇧1 on macOS, C-c o m in Emacs) and reveal the active file (Alt+F1, C-c o r); a crosshair after the breadcrumb and a ⋯ item do the same, and Search Everywhere’s Show in Map (Alt+Enter) selects a file on the Map. Open cards show as marks in the overview and in ⋯ → Open cards.
-
Project Map: follow the code from a card (Map review 3). A card’s and a declaration row’s menu have Go to Definition, Find Usages, Go to Implementation, Type and Call Hierarchy (opening the file in the editor at that spot; F12 and Shift+F12 work in a card), Related Test / Subject (revealed on the Map) and Show Git History. A folder’s menu, in the tree and the Map, has Find in Folder… and Git ▸ Show Git History.
-
Project Map: working sets and trails.
- ⋯ → Working sets ▸ Save Current As… keeps the Map’s view under a name: open folders, the selected row, zoom and pan, and open cards with their Structure columns. Pick one to go back to it as a restart would, or delete it. Sets are kept per workspace (workspace schema 28 → 29).
- Trails are guided tours of a project, kept in its
.editora/map-trails/folder to commit with it. Add a stop from a card (⋯ → Trails or the card’s menu) with a note; Play steps through the stops with a bar, opening each stop’s card at its lines with the note beside it; Edit reorders, removes and renames stops. A damaged trail file is listed and left alone.
-
Project Map: where the work happens and who owns it. ⋯ → Show recent changes tints files and folders by how many commits touched them in the last 90 days, with a heat bar along each row; the tooltip gives the count and who changed it last, and the Project overview lists the most changed folders. Tooltips and the overview name owners from CODEOWNERS or Kubernetes-style OWNERS files. The history read is capped, and shallow clones say why they show no heat.
-
Project Map: follow the code as cards. A card’s or a declaration’s menu has Show References as Cards and Show Callers as Cards: up to six places open as cards around it, joined by labelled edges (“calls”, “references”); a “+N more” chip lists the rest. The language server already running for the language answers for files with no editor tab, without opening the editor; with none, the name is matched in the project’s files and the edges say “by name”.
-
Project Map: more from a card. Find in a card (Ctrl+F, Cmd+F, C-s) with “k of N” and match case; pin a card so it is never closed to make room; step a declaration card through its file’s declarations (‹ ›, Alt+Page Up/Down) and Show in Structure; the status line ends with the last change to the file or the declaration’s lines, with Annotate in the menu. Structure columns use the outline of a language server already running, even for files with no tab.
-
Project Map: tidy and share the map. ⋯ → Collapse All, and a row’s Close Other Branches. ⋯ → Export saves the view as a PNG at twice its size, or the whole map as an SVG with every name as text; the PDF export is now searchable. Reveal in Map on editor tabs and in the Project tree’s menus. Screen readers move through the rows on screen as tree items.
Changed
-
The Python interpreter setting is on Settings → LSP → Python, editable with debugging off, next to a Choose… button that opens Python: Select Interpreter and Format on save (Ruff/Black). The picker names each environment by its folder, can be filtered by path, lists one interpreter once, checks a Browse… pick and keeps its arguments. The status-bar interpreter is the one Pyright analyses with.
-
Python snippets: the one-letter triggers
s,#and__are nowself,docanddunder, and Tab afterobj.never expands a snippet in any language. Narrow to Defun in Python takes the def or class you are in, with its decorators. Structure lists module constants and class fields without LSP and marks async, property and classmethod defs. -
Completion shows the server’s whole list (
os.has all its members, not 50) and “Waiting for Pyright…” while a slow server answers. Turning on inlay hints, semantic highlighting or code lenses says when the file’s server gives none. Doctor shows a missing Ruff/Black as optional unless Format on save is on. -
Java debugging: Run ▸ Debugger and the Debug window (second debugging review). The Run menu keeps Start / Continue, Debug Main Class, Attach, Stop, Restart and Toggle Breakpoint; stepping, watches, breakpoint and exception items moved into a Run ▸ Debugger submenu (the menu fits a 1080p screen again). Caught and Uncaught exception stops are one ⚠ button. The Breakpoints list shows each kind with its gutter glyph and short folders; Edit Breakpoint names its file and line and shows the line. The IntelliJ keymap opens the Breakpoints list with Ctrl+Shift+F8; CUA and Sublime open the Debug window with Ctrl+Shift+Y and show F11 for Step Into. Mute Breakpoints also mutes exception stops. Settings → Debugging has a Debugged programs card for the program-console and Terminal-tab switches (they apply to Python and JavaScript too). “Debug Log” is now Application Log: it is Editora’s own log.
-
Java files without Maven or Gradle run on the Settings JDK, else the
javaon PATH, and the Java language server builds for that same JDK. A changed Default JDK reaches a running language server without a restart. Gradle daemons the language server starts stop after 10 idle minutes. -
Debug in a JUnit test file debugs the test at the caret (or the whole class), as Debug Test does, instead of the project’s main class.
-
Project Map: pins, linked cards and trails after Map review 4.
- A pinned card stays until you close it with its own ×: Collapse All, Close Other Branches, closing its folder, Escape on the map, the orphan check and a trail moving on all leave it open.
- Result cards from Show References / Callers as Cards close with the card they were asked from (unless pinned), open at the call with the name selected, and put the code nearest the declaration first, tests last. Stepping the asked card to another declaration ends its question.
- Ctrl+→ / Ctrl+← (Cmd on macOS) step a playing trail from the map, its bar or a note, and Escape ends the trail before it closes cards. New commands: Project Map: Next Trail Stop, Previous Trail Stop, Close Trail. Showing a working set ends a playing trail.
- Print, PDF and SVG show a long folder by its first 300 rows and “+N more”, and one print or PDF makes at most 40 pages. Whole folders list at most 60,000 rows between them.
- Turning on Show recent changes says on the Map’s status line why nothing is tinted (a shallow clone, no Git history, a quiet or failed read) or that only the newest commits were read. Recent changes follow renamed files. Most changed counts commits to each folder’s own files and leaves out generated, vendored, ignored and deleted folders.
-
Search Everywhere and the Project tree filter use the Project Map’s file list. One list of the project’s files, kept current as you work, and one ranking: the name as typed first, then the project’s own source, then vendored code, then tests. Deep and very large projects are searched completely (the tree filter no longer stops at 20,000 entries or 25 levels), and a path such as
core/v1/types.gonarrows a common name. -
Project Map: long folders and quieter chrome. On a local project a long folder is listed whole (up to 50,000 entries), so a 5,000-file folder scrolls end to end with no “+N more”; remote folders keep “+N more”. The flow direction moved into ⋯ → Flow, and a column’s lock shows only while you use that column. A file’s Personal Notes badge opens its card with the notes beside it (note cards remain for folders), and a card’s lock reads “Preview — read only; Open to edit”.
-
Project Map: search ranking. The name in the case you typed comes first, then source before tests, fixtures, resources and docs, then project code before vendored code. A top-level
README.md,go.modorMakefilenow ranks above nested files of the same name, in the Map and in Go to File. -
Project Map: clearing the search keeps your place. The selected file and the folders that lead to it stay open, and Back returns to where you were before the search. During a search, “+N more” reads “+N not matching” and never hides a match.
-
Project Map: a card’s Structure column. A click or Enter on a declaration scrolls the card to it and marks its lines; Shift+click or Shift+Enter opens the declaration’s own card. The Structure command (Alt+7 in the Emacs and IntelliJ keymaps) and a card menu item open the column from the keyboard. The column goes on whichever side of its card hides least of the map and moves when the card is dragged.
-
Project Map: reveals and names. Revealing a file puts it a third of the way down with the folders that lead to it in view and flashes the row; the zoom bar and overview fade while the pointer is on a row they cover. Long sibling names are cut where they differ, card titles keep the file and declaration name, read-only is a lock icon, and a code card opens past a leading licence header.
-
Structure outlines (window and Map). Go outlines list methods by receiver (
(*Kubelet).Run) under their type, plus struct fields, interface methods and constants, and no longer list the package or embedded fields as types. Java fields are listed, and a Java or Kotlin class whose header wraps before its{holds its members. Kotlin annotations are no longer types,*.gradle.ktsscripts are outlined by their blocks, a YAML key covers its block or list, Dockerfiles are outlined by build stage, Makefile targets defined twice are labelled by line, and shell outlines lose their$rows. The Map’s Structure columns read files up to 4 MB, and a card cut at its display limit says “Showing lines 1–7,515 of 9,135” and ends with a line that opens the file. -
Project Map: speed on big and slow projects. Opening a file from the Map or moving between Editora’s windows no longer re-lists every open folder; coming back from another program only checks which folders changed. Big folders of files list faster on Linux, the folder you are reading keeps its rows at the 1,200-row limit, an unchanged Git status is not re-applied, a hidden Map does not redraw, icons and column controls are built ahead of a big search, and card connectors are drawn once per frame. On an SSH project a folder’s listing is reused for 30 s.
-
Project tree and Map: folders of hash-named files sort in plain order (
07c96f…before7c781c…). -
The macOS DMGs are signed and notarized. Editora for macOS (Apple silicon and Intel) is now signed with a Developer ID certificate and notarized by Apple, so it opens on first launch with no Gatekeeper warning and no trip to System Settings → Privacy & Security. The Windows MSI is still unsigned.
-
Every release file has a build provenance attestation. The release workflow now records a signed statement for each installer, archive and jar, naming the repository, commit and tag that built it. Check a download with
gh attestation verify <file> --repo adriandeleon/Editora --source-ref refs/tags/v<version>. -
Updated commonmark-java to 0.31.0, Apache MINA SSHD to 2.20.1, Gson to 2.15.0 and joni to 2.2.8.
Fixed
-
Sticky-scroll headers keep their height while the top line is partly scrolled off; they used to shrink to a few pixels and draw over each other.
-
Java debugging (third debugging review, 25 findings). A plain-folder project with more than one package can be debugged again: when the Java language server cannot build a file without Maven or Gradle, Editora compiles it with javac from its source root, and only errors in code the program uses stop the launch (a broken unrelated file or a JUnit test without JUnit no longer does); “Unresolved compilation problem” code never runs. Gradle Debug Main Class and Debug of a run configuration run the edited code, and Editora’s own Gradle daemons stop after 10 idle minutes. The language server builds for the JDK the program runs on even when that JDK is outside the usual folders; on macOS the
/usr/bin/javastub no longer hidesJAVA_HOME; a removed Default JDK is reported and thejavaon PATH is used. A slow or stucktoString()no longer holds up a stop or wedges the session; after Pause, objects readType@idwith a note instead of “null”; eachtoString()runs once per stop. Set Value works on Integer, record and enum variables; values refresh after a console evaluation; boxed numbers read42everywhere; a 1 MB String no longer hides the rows below it; wrapping or re-indenting a line keeps its breakpoint. F5, Debug ▶, Debug File in the editor menu and Debug Test share one check: a session that is paused, running or still being built is replaced only after asking. A loose launch shows “Building…” with Stop from the moment you press F5, F5 on a test’s annotations debugs that test, and files changed outside Editora just before F5 are built. The Debug console wraps, and the Debug and Run consoles stay readable with mixed light and dark themes. Pause is greyed while paused, Run ▸ Debugger no longer lists “Debug: Continue”, and with the program console off the state reads “Program ended, output still arriving” while the last output comes in. -
Every language server says when it is done. “‹server›: Loaded and ready” sometimes never came. Metals counted each new spinning status as new work and ended only one of them. A server that sent the same progress Begin twice, or an End for work it never began, threw off the count of open work. Each piece of work now counts once, and work a ready server began but never ended is taken as over after 30 seconds of silence, so the ready line (and the end of the loading bar) always comes.
-
Go: Beginning/End of Defun describe what they do in Python. The palette description said “top-level definition” in every language; in Python the commands take the innermost def or class, decorators included.
-
Node.js on a remote host, in WSL or in a container honours the project’s
.nvmrc. Run, a test file’s ▶ and Debug now read a.nvmrcor.node-versionon the host (from the file’s folder up to the project, or the package root) and run the Node.js of that version from the host’s nvm ($NVM_DIR, then~/.nvm), as a local run does. A version the host’s nvm does not have, or an alias such aslts/*, falls back to the host’s Node.js setting or itsnode, and the console says so. The runtime chip says why that Node.js was chosen on a host too. -
Doctor and Settings no longer run npx to look for the Mermaid linter. With the default maid command (
npx -y @probelabs/maid), Doctor, the Settings → Mermaid status and every start-up with Mermaid on ran npx just to ask whether maid was there: seconds each time, and npx looked the package up on the npm registry and downloaded it when it was missing. An installed maid is now found by its files — a global install (npm i -g @probelabs/maid, beside the Settings Node.js, node on PATH or the npm prefix), amaidon PATH that is that package, or npx’s own cache — and shown with its version and folder; without one the row is optional and says how to install it. A maid command of your own is still run to check it, as before. -
JavaScript and TypeScript with no TypeScript that can run. When the only TypeScript beside the TypeScript server is a TypeScript 7 (which has no tsserver), or there is none, the file’s install banner now offers Install, which adds Editora’s own TypeScript 5.9.3 and typescript-language-server 5.3.0 to its own folder (never
npm install -g). “Not now” and the install-prompts setting hold for it as for a missing server. The status line says the action first (“Install TypeScript 5.9 (Settings → LSP) …”) and is no longer cut off before it in a 1300 px window. -
JavaScript and TypeScript: a long word no longer slows colouring. A long run of letters and digits with no spaces (a token, a hash or base64 in a string, a template, a regex or code) took time that grew with the square of its length to colour: 0.2–0.5 s for 2,000 letters and 7–8 s for 10,000, while that tab and every other JavaScript or TypeScript tab waited for colours. It now takes a few milliseconds, and every colour is the same as before.
-
Python editing: the first
caseof amatchstays inside it (one Enter on a correctcaseline used to move it out),finallylines up with itstry, Tab indents the way Enter does, Enter between"""and"""opens a line, f-strings with nested quotes no longer confuse the indenter, and the status bar warns when tabs and spaces are mixed the way Python rejects. PEP 614 decorators are no longer painted as errors. -
Pyright and the venv: a venv created after the project was opened, and packages installed into it with pip, are picked up without a restart; a venv in a subfolder, a uv workspace’s shared venv and a bare interpreter name such as
python3.12reach Pyright; files in the project’s.venvopen read-only. Remote (SSH, WSL, container) projects pick up files changed on the host when the window comes back to the front, or within a minute. -
Format Document (Python) no longer empties a file Black skips (
force-exclude), never applies a cut-off result, and no longer adds a blank line when Ruff writes CRLF line endings (the same line-ending fix applies to Prettier, Biome and ESLint fixes). A narrowed, read-only or remote file says why it was not formatted. -
Find References from a Python call lists that call, and from a function’s only call it no longer jumps to the definition. Unused imports stay faded after LSP is turned on; the problem counter matches Problems; completion documentation is as wide as its signature; a library file opened by Go to Definition says Read-Only; a 50,000-line Python file with a final newline keeps Pyright; the Python banner is not shown when Pyright is switched off.
-
All languages: sticky-scroll headers line up with the code they name, a long file’s screen is coloured within a fraction of a second, regex group names no longer appear in Structure, and
def fis no longer shown asf() : de. Status-bar items are keyboard buttons, and completion rows have spoken names. VS Code keymap: Shift+Alt+O organizes imports, Ctrl+Shift+Space shows parameter hints; CUA: Ctrl+Space completes. -
Map: a Java file’s Structure column opens its class again. With the Java language server running, the Map’s Structure column (and a file card’s) stopped at the package and the class, because the server lists the package as a top-level entry of its own. A lone package, namespace or module line no longer counts, so the class’s members are listed straight away as before.
-
Java debugging (second debugging review, 38 findings). A loose
.javafile or a plain-folder project is built before every Debug and stops on compile errors: edits always run, where the code as first built used to run, and code that does not compile no longer runs. Hot code replace works in those folders (it failed with ”…: null” when two JDKs disagreed), a replace with running methods is reported as applied (with Restart Frame), a breakpoint on a line edited during the session keeps working, and Stop during a replace no longer switches it off for the window. Records, enums, dates and boxed numbers show their values in Variables, inline values and the value popup (GREEN,Point[x=3, y=4],42instead ofMain$Color@18); a String’s popup shows its whole text with Copy Value, and lambdas readlambda@N. JDK frames show the source of the JDK the program runs on. The Variables right-click menu opens (it never did). An attach ends the session before it; Stop cancels a start that is still being prepared; F5 asks before replacing a launch that is still starting, and Esc on the main-class chooser cancels it. With the program console off, a program’s last output and exit line are no longer lost; the console says when the program runs in a Terminal tab and when it dropped old output. A failed Maven/Gradle import is named as one, build errors show project-relative paths for the launched project only, Attach remembers its address and explains a port nothing listens on, and evaluation errors, library stops and Smart Step Into (calls in run order) read plainly. Names stay readable with a dark UI and a light editor theme. -
Doctor no longer offers a newer typescript-language-server than Editora installs. Check for Newer Versions looked it up on npm although Editora pins 5.3.0, whose next release needs Node.js 22.22.2. It is now pinned like the HTML, CSS and JSON servers: not looked up, and Install… replaces an own copy older than the pin.
-
The trust dialogs point at Settings → Advanced. The build, HTTP and folder trust messages said Trusted Folders was under Workspace, in every language.
-
A terminal no longer ties up a shared background thread while it is open. Each open terminal, and each program run on an SSH host, kept one of the JVM’s shared background threads waiting for its end; the pool has one thread fewer than the machine has cores. With a program that never ended they could all be taken, and then completion, link checks, debugger timers and other background work stopped until restart. A program that ignores Stop and whose terminal nobody reads any more is now also ended on macOS: its terminal is closed after the grace period, since macOS does not let a process finish exiting while its output is unread.
-
JavaScript, TypeScript, Node.js and npm (JS/TS review).
- Which TypeScript runs. Install now puts typescript-language-server 5.3.0 and TypeScript 5.9.3 in Editora’s
own folder instead of
npm install -g, so it no longer replaces your owntsc. TypeScript 6, which the last release installed, leaves out@types/nodeunless a tsconfig lists it, so Node projects showed “Cannot find name ‘process’” and plain JavaScript gotanyfor every Node API. The status bar shows the TypeScript in use, and an untrusted folder whose own TypeScript differs says so once. - One Node.js, really. npm, pnpm, yarn and bun scripts now run on the Node.js that Run, Debug and the language
server use; they used whatever
nodewas on the PATH. A project’s.nvmrcor.node-versionnow wins over the Node.js setting,$NVM_DIRis honoured, a version nvm lacks is named, and the runtime chip says where the version came from. The Node.js setting moved to its own card on Settings → Build Tools; it was greyed out under Debugging unless debugging was on. - TypeScript runs. ▶ on a
.tsfile uses the project’s tsx (--import tsx), else its compiledoutDirfile (with a warning when that is older than the source), else plain Node with a hint; a./x.jsimport used to fail with ERR_MODULE_NOT_FOUND, Editora’s own template included. Debug starts a file exactly as Run does and prints the real command line. - Language server. Fix all, Add all missing imports and Remove unused are back in Code Actions on a line with a
problem. A dead tsserver restarts the server instead of leaving it silently empty. Moving or renaming a
.ts/.jsfile updates its imports. A monorepo opened without a project runs one server, not one per package. JS/TS files keep their server up to 50,000 lines (was 10,000). The completion pane shows the signature. Dark popups no longer draw code in light-theme colours. A settings change no longer restarts a server that kept crashing. - JSON.
tsconfig.json,jsconfig.json,.eslintrc,.babelrc,.swcrc,.vscode/*.jsonand*.code-workspaceallow comments and trailing commas;package.jsonandtsconfig.jsonare checked and completed offline against bundled schemas. - Editing. Typing in files with long lines no longer stalls (about 850 → 10 ms a key on 8,000-character lines);
such lines are shown plain instead of half-coloured. Minified, huge and very-long-line files open in View mode with
the reason; “Editable, No Undo” shows while undo is off. In JSX, Toggle Comment writes
{/* … */}, Enter between tags indents, and elements andreturn (fold. Without a server, Go to Definition finds parameters, locals and imports. New JS/TS/JSON/YAML files indent 2 spaces. A typed bracket no longer pairs right before a word (all languages). Related File pairs.ts,.jsand.d.ts. Spell check reads JSX text. - Tests and consoles. Test runs show Node’s readable report in the Run console; a test file that fails to load shows its error; skip/todo reasons are read. The Debug console keeps the program’s output in order and in colour, folds Node’s internal frames, clears a stale stack after a step runs on, and names the file it stopped in. Run, Output and Test Results open tall enough to read. Messages name the package manager that ran.
- Debugger. js-debug runs on a new enough Node.js even when the project’s is older than 18. The attach command is Debug: Attach to Running Program… (JVM or Node.js). The Debugging card’s Install… installs vscode-js-debug alone, and its download is checked against a pinned SHA-256. Settings and Doctor show the js-debug version.
- Search and index. Find in Files no longer says “(truncated)” because a large bundle was skipped. With Respect
.gitignore off, the index keeps the project’s own files before
node_modules. The npm window’s commands, Output tab and Settings text say Package Scripts.
- Which TypeScript runs. Install now puts typescript-language-server 5.3.0 and TypeScript 5.9.3 in Editora’s
own folder instead of
-
Project Map: Emacs keys in sticky notes. A sticky note on a preview card, and a folder’s or file’s note card, now move the caret with the keymap’s keys —
C-f,C-b,C-n,C-p,C-a,C-e,M-f,M-band the rest in the Emacs keymap — as the Personal Notes box in the editor does. Only the text box’s own keys used to work there (on Windows and LinuxC-aselected all). -
Project Map: cards open the way the map flows. A new preview or declaration card opens past its row’s column the way the map flows — right of it left to right, left of it right to left, below it top to bottom, above it bottom to top. With no room there it opens beside the column, level with its row; the map never pans for it. A file card’s Structure column always stands on the card’s right, and a declaration card opened from it opens right of the file card, past the column and level with its row, so its connector line runs straight to it; the file card steps left when there is no room. It used to open in a far corner of the map, with its line hidden under the other cards.
-
Project Map: a declaration card follows the Structure column it was opened from. Clicking a method or type in a file card’s Structure column opens its own card beside that column; it used to scroll the file card instead (Shift+click or Shift+Enter still does). Clicking the same declaration in the Map’s own Structure column moves its open card beside that column, with its connector line from that row, and back again; the line used to stay on the file card’s column while the card stood elsewhere.
-
Project Map: the explore round’s features (Map review 4).
- Print or PDF with a long folder open no longer freezes Editora (27 s and 1,613 pages for a 50,000-file folder; now 10 pages in under half a second). Paint with 50,000-file folders open stays at a few milliseconds.
- Export ▸ PNG no longer has a blank band at the top or loses the bottom of the view.
- Show References / Callers as Cards: Go methods group under their method, so other types’ same-named methods are not counted as callers; the “+N more” button is no longer hidden under the result cards; a question no longer evicts its own first results when cards are pinned (places that get no card are listed under “+N more”); a failed or timed-out call hierarchy is no longer reported as “No callers found” — the name is matched instead.
- F3 / Shift+F3 in a card’s find field step through matches in every keymap (in Emacs they started a macro).
- Recent changes and Most changed follow a pull, checkout or commit made on a clean tree; files whose names hold
"or\and submodule rows show their heat; a deep folder is never hotter than its parent; edited owner files are read again; a read that timed out is tried again and the window follows the date. - Owners: an OWNERS file that names only reviewers shows them as reviewers and takes the owners from the nearest
folder above. GitLab CODEOWNERS (
.gitlab/CODEOWNERS, section default owners) is read. The Overview no longer cuts a folder name to ”…” beside a long owner list. - A card’s “Last change” no longer names a shallow clone’s single commit, and stays right for a declaration below uncommitted edits.
- Trails: stepping on or closing before a stop’s card appeared no longer leaves it open; a hand-named trail file
(
Kubelet tour.json) plays, edits and takes stops; the trail editor no longer writes over a trail changed on disk; a trail with more than 200 stops or unknown fields is read-only instead of cut; a stop past its file’s end says so; a closed stop card can be reopened from the bar; a stop’s note avoids covering the map’s columns. - A working set (and a restart) brings back its exact zoom and pan on a large project.
- Language servers: overlapping loans of one file no longer close it on the server while it is still asked about.
- A file created while the project’s file list was being built no longer goes missing from the Map search, Search Everywhere and the tree filter.
-
HTML Live Preview: a file’s old name kept serving its editor text (HTML review 3).
- After Save As, Encrypt File or a rename (tab menu or Project tree, a file or a whole folder), the preview kept serving the buffer’s text at the old address until the preview was turned off — for Encrypt File, the plaintext, including edits never saved in plaintext, and a previewed page’s open tab reloaded into it. The old address now answers from disk (404 once the old file is gone), the new name is served as any edited file is, and an encrypted file’s text is never served.
- Clients that requested a big page and stopped reading it could stall every page of every previewed site with no time limit; a page now waits at most 10 seconds for its turn and is then answered “503 Service Unavailable”.
- A browser launcher whose
TryExecis a path (typical for AppImage and/optbrowsers) was offered after the browser was removed; it is now offered only while that path is an executable file.
-
HTML editing (HTML review 3).
- Angular component templates are no longer full of false warnings: in a
*.component.html, a page below anangular.json, or one that uses Angular syntax,<app-header />closes the element, and a component’sassets/…image is found in the app’ssrc/(orpublic/) folder. A plain page still flags<my-el />. - Template syntax a page only shows — in
<pre>,<code>,<textarea>, a comment, or an Underscore<script type="text/template">— no longer switches off the page’s unclosed-element check and Format. - The missing-file check no longer accepts any file under
assets/, nor a page-relative link found underpublic/orstatic/on a plain static site: those folders count for root-relative links, or when the project has a build tool (package.json,vite.config.*,angular.json, Hugo’s config…). - Toggle Comment in a
.mustachefile makes the line an HTML comment with each tag a comment tag ({{name}}→{{!name}}), since Mustache’s{{! }}ends at the first}}; uncommenting restores it. - Toggle Comment on an ERB/EJS block that holds a comment of your own (
<%# note %>) round-trips: commenting gives it a second#, so uncommenting gives your comment back instead of turning it into code. - “Quotes after a typed or completed =” moved to Settings → Editor, beside Auto-close tags, where it can be
changed with language servers off; it says it also decides what a typed
=brings. - A typed
=after Angular’s(click),[value],[(ngModel)]or*ngIfbrings its quotes, as Vue’s@clickdoes. - Tab and Enter keep the brace rules in an inline script of more than about 250 lines, and in a script whose
strings hold
'<style>'or'<pre>'. - With the HTML server on, Format Document on a Django/Jinja/Hugo page is refused too (“Not formatted: this page uses template syntax”), as it is with the server off.
- The built-in formatter keeps an HTML template script (
text/x-template) and its<pre>exactly as written, and indents Angular@if/@for/@deferblocks instead of flattening them.
- Angular component templates are no longer full of false warnings: in a
-
Project Map: a declaration card from the last session was dropped on restart while its file’s outline was still loading; it now waits for the outline.
-
GNOME Software’s page for the installed Editora shows its version and can remove it. The AppStream listing did not name its package, so Software had no way to tie the two together.
-
Java: the last Go to Super Method and import edges. On any segment of an anonymous class’s name (
new java.util.Comparator<>() {,Mapofnew Map.Entry<>() {), and on the header of one passed as a call’s argument, Go to Super Method opens the type it instantiates; so it does for a member type the enclosing class inherits (new SimpleEntry<>("a", "b") {…}in a subclass ofAbstractMap), and for a package-qualified one found by its package. A Gradle import that fails is named with the folder that failed in its first message, not only in a later one. A library’s sources attached later reload its tabs in every window sharing the Java server. -
pom.xml hover works on the Maven server. Hovering an element the POM schema documents (and any XSD-backed element on the Java XML fallback) failed inside the server with
NoClassDefFoundError: org/jsoup/safety/Whitelist: the bundle’s remark library needs jsoup 1.14, and Editora installed 1.23.2. The pom.xml server now installs jsoup 1.14.3, pinned by version and SHA-256; an install made with the newer jsoup reads as incomplete, and Install… repairs it. -
XML and HTML: Emacs word kills on a tag name keep the caret in that tag. M-DEL or M-d in a closing tag left the caret where it was before auto-rename shortened the start tag, so the next word renamed the following element, and at the end of the file the next key threw.
-
XML and HTML: a hand-typed close tag survives every key. While
</itsteps into the existing</item>, Ctrl/Shift/Alt+Backspace, Delete, Enter, Tab, a paste and the Emacs kills now act on what you typed, as Backspace already did; they used to edit the real end tag, and auto-rename carried the change to the start tag. -
Built-in XML/HTML format: switching tabs no longer discards it. The result goes into its own tab when that file is unchanged, and Format Document in another tab runs at once instead of saying “Already formatting”. The large-file question names the file (“Format big.xml?”, not “Format ?”).
-
Settings: long server and tool commands are readable. The LSP, build, debug and tool path fields show their whole value as a tooltip and have a screen-reader name; Schema associations is as wide as XML catalogs.
-
XML: Go to Definition and schema changes (XML/pom review 4).
- A schema or DTD open in a tab and changed on disk (a pull, a checkout, a build) revalidates the files that use it, in the background and after Reload; their old errors stayed until the schema was saved in Editora.
- F12 on
schemaLocationinside an XSD (xs:include,xs:import) opens the included schema, not the cachedXMLSchema.xsd. - F12 on a link to a missing file (
xi:include,xsi:noNamespaceSchemaLocation, a DOCTYPE) says ”does not exist” instead of “Failed to open” with the full path. - In a
pom.xmlon the Maven server, F12 on the schema location or an element the Maven extension does not handle goes to the POM schema, as on the plain XML server. - Include hrefs written
file://localhost/…or with a?queryopen their file, and a>inside another attribute of the include tag no longer hides itshref. - XML: Generate Grammar… no longer offers the two XSD choices for a document whose root element is in a namespace: lemminx’s generated schema had no namespace and failed the document at once.
-
XML and pom.xml servers: install and status (XML/pom review 4).
- RELAX NG completion works on the Java lemminx (the pom.xml server, and XML’s fallback on older Linux): Eclipse’s signature on the lemminx jar kept its RELAX NG plugin from loading. Install now removes the bundle’s jar signatures, and a bundle installed earlier is fixed the next time a server starts from it.
- An XML command Editora refuses to start (it loads lemminx-maven) shows as a problem in Settings → LSP and as an
error in Doctor, not “found” and “OK”. XML’s Java fallback is named “Java lemminx
(fallback)”. - The XML command an earlier fallback install stored is treated as Editora’s own: Doctor offers Install, and a native build is installed when it can run.
- The pom.xml server is told the local Maven repository Editora reads, so Doctor’s lemminx-maven store row is
right for a
${env.…}or relative<localRepository>;${env.…}and system properties are expanded. - Updating the pom.xml server also stops XML while XML runs on its Java lemminx.
-
Project Map: search said “No files match” for files that exist. On a big repository the search stopped after 20,000 entries, so deep files (Kubernetes’
staging/modules) were never found and the notice went to the editor window’s status bar. The search now covers the whole project, and “No files match” says when it did not. -
Project Map: reading a file’s declarations from its card’s Structure column by keyboard closed every card at the eighth: the file card was evicted as least recently used, taking its column and declaration cards with it.
-
Project Map: a folder that stops answering (a hung network mount) got another stuck thread and a fresh 10-second wait on every refresh; it now shows “Not responding” at once.
-
Project Map: columns overlapped in big searches in Spring-like trees, hiding matches under another branch’s column with a stray × and lock over them.
-
Project Map: “No files match” kept naming an earlier query, and breadcrumbs dropped the first underscore of a name (
zz_generated.openapi.goreadzzgenerated.openapi.go). -
Structure: Kubernetes’
core/v1/types.gooutline stopped atNodeAddress; files past the card’s 400,000-character display limit are now outlined whole. -
HTML and the npm language servers (HTML review 3: server).
- A project’s
htmlsettings (.editora/settings.json) apply as soon as its window opens a page, and the “Not used from .editora/settings.json” notice appears then; before, both waited for some Settings change. - Go to Definition on a
/…link in a page outside the window’s project starts from that page’s own site, as its language server and the markup check do; it opened the project’s same-named file. With LSP off, the markup check of such a page uses the same root. - Format Document on an already formatted page under
insert_final_newline = truesays “Already formatted” and leaves no undo step. - A server Install put in the Settings Node.js’s own folder with
npm install -g(YAML, Pyright, Bash, TypeScript, Dockerfile, TOML, Astro) is found there: detection, Doctor, the launch and the banner look in that folder after PATH. When npm puts it somewhere Editora does not look, Install says where instead of “installed”. - Doctor’s Installer Prerequisites counts the Node.js chosen in Settings and npm beside it, named as such.
- A git push, pull or commit that fails after its window closed is said in another open window — its status line and message log, as an unread error naming the project — instead of nowhere; with no other window, the Debug Log has it.
- A project’s
-
HTML templates (HTML review 2: templates).
- The markup check no longer flags Django, Jinja, Jekyll, Hugo, Handlebars or ERB pages saved as
.html, nor header/footer partials intemplates/,_layouts/,partials/and similar folders: their branches are not checked for unclosed tags (links still are). A link to a file inpublic/,static/orassets/(Vite, Create React App, Angular, Hugo), a%PUBLIC_URL%placeholder and a.cssbuilt from.scssare no longer “File not found”.<a href=/about/>no longer reads as self-closing, and<image>counts as<img>. - Format without a language server refuses a page with template syntax (“Not formatted: this page uses template
syntax”) instead of splitting
{# #}comments and nesting{% if %}branches. On other pages it keeps<select>,<textarea>,<svg>,<video>, custom elements and a comment inside a word on their line, and moves a<style>’s or<script>’s code and end tag along with the start tag. - Toggle Comment on a template line writes the engine’s own comment, which stops the code:
{# #}(Jinja, Twig, Nunjucks, Django),{% comment %}(Liquid),<%#(ERB, EJS),{{!-- --}}(Handlebars, Mustache),{{/* */}}(Hugo). On a PHP file’s<?phpline it comments the code after the opener, never the opener itself. - Spell check skips
{{ … }},{% … %}and<% … %>intitle/altvalues and text, and tag names mentioned in comments.
- The markup check no longer flags Django, Jinja, Jekyll, Hugo, Handlebars or ERB pages saved as
-
HTML with the language server: links, Format Document and project settings.
- Go to Definition on a link resolves it the way a browser does before asking the server, so
site.css?v=3, pages that use<base href>and file names with%23open their file instead of saying “File not found”. - A link to a folder that has no
index.htmlsays so instead of “File not found”. - “File not found” marks follow the disk: creating, deleting or renaming a linked file updates them without editing the page.
- Format Document no longer adds a blank line before every
</style>. The final newline is kept as the file had it, or as EditorConfig’sinsert_final_newlinesays. - Inline
<script>code is formatted with VS Code’s spacing:function f() { return 1 }. - With LSP off, following a link no longer leaves “LSP support is disabled”. Format Document in a template file says there is no formatter.
- A project’s
.editora/settings.jsontakes VS Code’s dotted keys ("html.format.wrapAttributes"). The keys it ignores are named on the status bar.html.autoClosingTagsthere no longer overrides Editora’s own auto-close.
- Go to Definition on a link resolves it the way a browser does before asking the server, so
-
HTML typing (HTML review 2).
- Accepting a CSS property now really opens the list of its values, and a folder in
href/srcits files: the second list no longer flashes and closes, or never opens, with the real language server. - A typed
=brings the quotes Settings → LSP → HTML “Quotes for completed attributes” names (double, single or none). Typing your own'replaces the pair (class='x'no longer becomesclass="'x'"), a space or>typed straight after takes the empty pair back, and no quotes go into{% %},{{ }}or<% %>in a tag or into code in the middle of a long inline script. - Enter between
<style>|</style>or<script>|</script>puts the end tag on its own line again. - Tab in an inline
<script>or<style>re-indents by its braces, as Enter does; Tab on a line in<pre>or<textarea>keeps its whitespace and is never sent to the language server. - Colour swatches move with the text typed before them instead of landing inside the words.
- The documentation panel beside the completion list is tall enough for its text (up to its maximum) instead of showing two or three lines.
- Accepting a CSS property now really opens the list of its values, and a folder in
-
HTML, CSS, JSON and the other npm language servers (install and Node.js). A project’s
.nvmrcor.node-versionno longer picks the Node.js these servers run on, so an old pinned Node.js can no longer crash them; they use the Node.js chosen in Settings → Debugging → JavaScript, else the one on PATH (TypeScript still follows the project). Install finds npm beside that Node.js and runs with it. “Not responding” is no longer said while a server is still importing or reports work in progress. An HTML server from an earliernpm install -g, whose<script>gets no DOM completion, is offered Update once per window. In Doctor, a command field that holds the default text counts as the default (Update is offered), Editora’s own copy is shown by its program name, and the Node.js tips read right for several servers and name the Settings choice. -
HTML Live Preview (review 2). Encrypted files are never served: an encrypted page gets no globe, an unlocked encrypted buffer’s text never reaches the preview server, and
*.gpg/*.asc/*.pgpnames answer 404. Each previewed site now has its own origin (its own port and random address), so a page previewed later cannot read another site’s files or unsaved edits; certificate and password stores, Terraform state, databases,credentials*.jsonandsecrets.*are not served either. Opening a file of the site no longer reloads the page — only an edit does.href="/"and folder links (blog/) open that folder’sindex.html. Big files are streamed and at most four pages are built in memory at a time, so parallel requests cannot exhaust memory; a large-file buffer is served from disk instead of being copied on every pause. A browser you picked that is no longer installed is named in the status (“Brave wasn’t found…”) and stays your choice. On Linux only real web browsers are offered (not every app that opens links). Typing in a stylesheet no longer re-downloads CDN stylesheets./var/tmp,/dev/shm, macOS/tmpand OneDrive’s Desktop and Documents are refused as site roots like Downloads, and a page in a hidden folder (.github/) loads its own assets. The HTML language server and the preview now root a loose site at the same folder (the highest folder of a contiguous chain ofindex.htmlpages, never Downloads or the home folder), even with a dotfiles~/.gitor a stray~/package.json.