[0.22.0] - 2026-10-16
Added
-
HTTP Client: Debug Request.
HTTP: Debug Request at Caret(also Debug Request in a.httpfile’s right-click menu, and Debug on a.httpfile) sends the request with its pre-request scripts and response handlers under the JavaScript debugger. A script stops at its breakpoints, with the call stack, variables, watches and stepping of any JavaScript session, and the request goes on when you continue.- Breakpoints go on the lines of a
{% %}block in the.httpfile itself, or in a./check.jshandler file. Elsewhere in a.httpfile the toggle says why it doesn’t set one. - It needs JavaScript debugging, as for a
.jsfile: Settings → Debugging and vscode-js-debug. - A paused script is not stopped by the script timeout. A script whose debugger doesn’t attach within 30 seconds is stopped. Restart doesn’t send the request again: run Debug Request again.
- The script runs as usual — trusted folder, minimal environment, Node’s permission model — and Node’s inspector is allowed only for this, on a random port on 127.0.0.1. Letting a debugger in under the permission model needs Node.js 24.12 or later: on an older Node a debugged script runs without the permission model, and the Debug console, the status bar and the response’s warnings say so.
- Breakpoints go on the lines of a
-
HTTP Client: pre-request scripts. A
< {% … %}block or a< ./sign.jsline above a request runs on Node.js before the request is resolved and sent.request.variables.set(name, value)sets a variable for that request only. It wins over every other variable, including the file’s@name = valuelines.- The request as far as it resolves:
request.url,request.headersandrequest.body(withtryGetSubstituted()andgetRaw()), andrequest.environment.get. - Signing: the JetBrains
cryptoAPI (crypto.sha256(),crypto.hmac.sha256().withTextSecret(…), md5, sha1, sha384, sha512, sha3, thenupdateWithText/updateWithHex/updateWithBase64anddigest().toHex()/toBase64()), andjwt.sign/verify/decode(HS, RS, PS and ES algorithms with a secret or a PEM key). - Global headers:
client.global.headers.set(name, value), in a pre-request script or a response handler, adds a header to later requests (and, from a pre-request script, to its own request). A request’s own header wins, aHostheader is never set, andclear(name)removes one. - A request whose pre-request script cannot run — an untrusted folder, no Node.js, an error, a timeout — is
not sent, and says why. The rest of a Run All still runs.
client.exit()ends the script and sends the request. The script’s tests and log come first in the Tests block. - Secrets: a script’s values are sent as written, never resolved, so a script cannot make a request read
$env/$dotenv. Scripts don’t see secrets either:request.environment.getreturns environment values as written, so keep signing keys inhttp-client.private.env.json. When a request that reads a secret goes to a host made of a script’s or an earlier response’s value, the secrets prompt names “a host chosen by an earlier response or a script”.
-
Run with Trace for shell scripts.
Run: Run with Trace(palette, Run menu, and the editor’s right-click menu on a shell script) runs the script with-x, keeping its shebang’s interpreter and flags. Under bash each traced line names its file and line (+/path/deploy.sh:12: cmd) and is a link to that line;shand dash trace without locations, and zsh is not supported. Putting-xin a run configuration’s Interpreter options gives the same links. Trace lines are drawn muted, not as errors. -
Modelines set the language of a file whose name says nothing: a vim modeline (
# vim: ft=sh,vim: set filetype=bash :) in the first or last five lines, or an emacs-*- mode: sh -*-line. -
Terminal sessions in Markdown.
```consoleand```shell-sessionblocks in the preview show a muted prompt, a highlighted command and plain output.```shellscriptblocks are highlighted as shell. -
Problems rows show the rule code (
[SC2086]), with Open Rule Documentation and Copy Code in their context menu. -
Shell scripts: ShellCheck and shfmt. bash-language-server needs both for linting and formatting, and without them it silently did neither. Doctor and Settings → LSP (Bash) now show whether each one is found, with an Install button, and the palette has
Install: ShellCheck and shfmt. Editora downloads the official release binary for your platform, checks it against a SHA-256 hash built into Editora, and points the Bash server at it; a path you set yourself still wins. Opening a script without ShellCheck says so once, and Format Document without shfmt says shfmt is missing instead of “Already formatted”. The server’s own warnings now reach the Debug Log. -
bash-language-server settings. The Bash card in Settings → LSP sets ShellCheck’s path and arguments (for example
--severity=warningor-x), shfmt’s path, dialect and style switches, the number of files the server analyses in the background (500 by default), workspace-wide symbols, and an explainshell endpoint for option hovers (empty by default). A project’s.editora/settings.jsoncan override them with abashIdeobject that uses the server’s own key names; paths and the explainshell endpoint need a trusted folder. -
Shell run configurations have Interpreter and Interpreter options fields, which override the interpreter the script’s shebang names.
-
End Input for a running program. The Run console has an End Input button, and Ctrl+D on an empty input line does the same, so a
while readloop orcatcan finish without Stop. -
Folding for shell scripts: functions,
{ },if … fi, loops,case … esacand each multi-line case item, multi-line( )and$( ), and here-docs. Sticky scroll now pins shell functions and blocks too. -
A notice for shell scripts with Windows line endings or a byte-order mark, which bash cannot run, with a Convert to LF (or Remove BOM) action. Running such a script first asks whether to convert it.
-
HTTP Client: response handlers, tests and checks.
- JavaScript response handlers —
> {% … %}after a request, or> ./check.js— now run, on your own Node.js, once the response arrives. They use the JetBrains API:client.test,client.assert,client.log,client.global,client.exit,response.body(parsed JSON),response.status,response.headers.valueOf,response.contentType,response.cookies(), the request as sent (request.url,request.headers,request.body),request.environment.getandjsonPath(…). - A Tests block in the response view lists each test with ✓ or ✗ and why it failed, then the handler’s log
and any error, with its line in the
.httpfile. A✓ 3 passed · ✗ 1 failedbadge sits beside the status line, Run All’s summary counts the requests whose tests failed, and History rows carry a ✓ or ✗. Test results are kept in the saved history. - Checks without JavaScript:
# @assert status == 200,# @assert $.items[0].id == 7,# @assert header Content-Type contains json,# @assert $.token exists(also!=,<,<=,>,>=,matches,!exists, andtime/bodysubjects), and# @capture token = $.token. They need neither Node.js nor a trusted folder. - Session variables: what
client.global.setor@capturestores is used by later requests as{{name}}— after a Run All’s earlier request, or a single run of it. It wins over the environment and loses to the file’s own@name = value, is inserted as is (never resolved), and is cleared when the environment changes. The editor no longer marks{{name}}unresolved when the file sets it this way. - Safety: a handler is code from the folder, so it runs only from a trusted folder (the same trust as build
scripts and secrets), asked once per run with Cancel as the default button. Node.js is started without your
environment variables (so
process.envcannot read a token around the secrets prompt) and, on Node.js 20 or later, under its permission model: no file writes, no child processes, no workers. It is stopped after 10 seconds. A secret the request read reaches the handler masked. Handlers may make network requests. Remote.httpfiles still do not run. Import cURL writes body lines the format would not send (from a>,<>or###line on) as comments, so a pasted command can never add a handler. - Settings → Web: turn handlers off, choose the Node.js to use, and set the timeout. The Doctor has a row for it.
- JavaScript response handlers —
-
Emacs registers. In the Emacs keymap:
C-x r scopies the selection into a register; withC-u, it cuts it.C-x r iinserts a register’s text, leaving the cursor before it.C-x r SPCsaves the cursor’s file and position in a register.C-x r jjumps back to that position, opening the file if it is closed.
Each command takes the register’s name as the next key; Escape cancels. A saved position follows edits to its file while the file is open.
Edit: List Registersshows them all. Registers last for the session, one set per window, and every command is also in the palette. -
More text tools, in the String Manipulation picker and the command palette.
- Encode and decode the selected text: Base64, URL encoding, JSON string escapes, HTML entities, and
\uXXXXescapes. They work on every selection at once. A decode that cannot read one selection changes nothing. Edit: Increment Number/Edit: Decrement Number: change the number at each cursor, or the next one on its line. They handle negatives, zero padding (007→008) and hexadecimal (0x0f→0x10);C-u Nsteps by N. In Emacs they are bound toC-c =andC-c -.Edit: Keep Lines Matching…/Edit: Remove Lines Matching…: filter lines with a regular expression.- Two more sorts: case-sensitive, and natural order with duplicates removed.
- Encode and decode the selected text: Base64, URL encoding, JSON string escapes, HTML entities, and
-
Several rulers, rulers per language, and indent guides. Settings → Editor now takes a list of ruler columns (
80, 120) and, per language, lists that replace it (java: 100; python: 79, 88; a language with nothing after its colon has no rulers). The palette hasEditor: Set Rulers…andEditor: Set Rulers for This Language…. An.editorconfigmax_line_lengthstill sets the first ruler, andoffstill hides them. Indent guides — faint vertical lines at each indentation level, carried through blank lines — are on by default. Turn them off withView: Toggle Indent Guidesor in Settings → Editor. They are hidden in Zen and Simple UI and in large-file mode, follow the theme, and skip folded lines. They are placed from the text as it is laid out, so they stay on their columns when the line numbers gain a digit or are toggled, when the font changes, in a proportional font, and in a tab-indented file; scrolled sideways, they are not drawn over the line numbers. The ruler toggle is nowView: Toggle Rulers. -
Line commands, at every cursor.
Edit: Insert Line Below(Ctrl+Enter) opens a new, indented line under the current one, wherever the cursor is on it.Edit: Insert Line Above(Ctrl+Shift+Enter) opens one above.Edit: Delete Line(Ctrl+Shift+K, IntelliJ’sCtrl+Y) deletes the line or every selected line without touching the clipboard or the kill ring. Emacs’ Kill Whole Line is unchanged.Edit: Select Line(Ctrl+L) selects the line, and grows by a line each time.Edit: Indent Lines/Edit: Outdent Lines(Ctrl+]/Ctrl+[) shift the line or selection by the file’s indent unit, wherever the cursor is.
Each runs at every cursor as one undo step, opens a collapsed fold before changing it, and renumbers an ordered Markdown list it changes. Keys are in the VS Code and Sublime keymaps, partly in CUA and IntelliJ (
⌘on macOS); Delete Line is also in the Edit menu. -
More ways to place multiple cursors.
Edit: Split Selection into Linesturns each selected line into its own selection (Sublime’sCtrl+Shift+L; also in the Edit menu).Edit: Add Carets to Line Endsputs a cursor at the end of every selected line (VS Code’s and CUA’sShift+Alt+I, IntelliJ’sAlt+Shift+G).Edit: Skip Occurrencemoves the newest selection on to the next match instead of adding one, wrapping round to the start (Ctrl+K Ctrl+Din VS Code and Sublime).Edit: Remove Last Added Carettakes back the cursor added last (Ctrl+Uin VS Code and Sublime, IntelliJ’sAlt+Shift+J).
In the Sublime keymap,
Select All Occurrencesmoves to Sublime’s ownAlt+F3(Ctrl+Cmd+Gon macOS), freeingCtrl+Shift+Lfor Split into Lines. -
Save All, Revert File and Reopen Closed Tab.
File: Save Allsaves every modified file in the window, across all editor groups, then reports how many it saved, how many it could not save, and how many untitled buffers it skipped.File: Revert Filereads the file again from disk, asking first when that discards unsaved changes. The caret, scroll position and folds stay put, the file is read in the encoding chosen for it, and Local History keeps the discarded text.Buffer: Reopen Closed Tabbrings back the file whose tab you closed last, with its caret where it was. It skips files deleted since and goes to a file that is already open again. All three are in the File menu. Keys: Save All isCtrl+K S(VS Code;⌥⌘Son macOS) andC-x s(Emacs). Reopen Closed Tab isCtrl+Shift+Tin the VS Code, Sublime and CUA keymaps (⇧⌘Ton macOS). To make room, the File menu’s export formats moved into an Export submenu. -
Choose a file’s encoding. Click the encoding in the status bar, or use
Buffer: Reopen with Encoding…andBuffer: Save with Encoding…from the command palette. Reopening reads the file again in the encoding you pick — Shift_JIS, GBK, windows-1251 and about 40 other common ones are listed by script, then every encoding the runtime has — and remembers it for that file, including remote files. When the file is not valid in that encoding, nothing changes and the status line names the first line and column that could not be read. Saving with an encoding marks the tab modified until you save, wins over.editorconfig, and refuses a character the encoding cannot hold instead of switching to UTF-8. An encoding Editora could not detect is shown in the warning colour, with a tooltip that says so. The installed app now includes the JDK’s extended charsets (ISO-2022-JP, the Hebrew, Arabic, Baltic and Vietnamese Windows code pages, MacRoman…), so the list is the same on every OS. File Information shows the file’s real encoding instead of always UTF-8. -
The Run, Output, Test Results, Debug and External Tools windows show a spinner while something runs. A long script, build or test run that prints little or nothing no longer looks stalled: a small spinner beside the status turns from launch (including a run configuration’s before-launch command) until it exits, is stopped, or fails to start. In Output, each tool’s tab spins only for its own build, and a Git tab spins while a clone streams; the tab’s title spins too, so a build in a tab you are not looking at still shows it is running. In Test Results it covers the compile step before the first test reports, when the progress bar is still empty. Debug spins while the before-launch build, the session start or the program runs, and stops at a breakpoint. An external tool that writes to the console now opens it at launch with the spinner, instead of only when it finishes; a tool that writes into the editor spins the External Tools header too. The Run window’s stripe button also badges a small spinner on its icon while a program runs, so a run still shows it is alive with the Run window closed or another window open in its place.
-
Remote development is on, and set per host. The tools Editora drives — Git, gh, ripgrep, builds, tests, language servers and debuggers — run on the host of a remote folder by default. The first time you open a folder on a host, Editora asks once whether it may run commands there. Settings → Remote now shows, for each saved site, whether that host may run commands (you can withdraw it there) and the command for each tool on that host when its PATH does not find the right one: Git, GitHub CLI, ripgrep, a JDK, Node.js, debugpy’s Python, js-debug, java-debug, and any language server (
server = command, one per line). Changes reach open windows at once. The global switch is in Settings → Remote and in theRemote: Toggle Running Commands on the Hostcommand. Works with OpenSSH servers (on Linux and on macOS, where Remote Login is one) and dropbear: on a dropbear host, stopping a program also stops what it started, and a lost connection ends it, and on the older dropbear Debian 12 and Ubuntu 24.04 ship, a command no longer fails now and then with “the remote host did not start the command”. Removing a saved site keeps that host’s answer and tool commands, for when it is added back. -
Tools in a container. A project folder bind-mounted into a running container — the dev container that the Dev Containers CLI or VS Code started for it, or a container you pick with Containers: Run This Project’s Tools in a Container… — can have its git, builds, tests, language servers and debuggers run inside the container, with the container’s own PATH, environment and user, while you edit the files here. Editora asks once per container; Containers: Run This Project’s Tools Here goes back. Works with Docker and Podman (Settings → Remote → Container engine). A debugger listening on a port inside the container is reached from here, whatever the container’s network. Editora keeps its working files in
~/.cache/editorainside the container, so the Java language server’s index survives a restart, Debug works on a loose Java file and with the java-debug plugin Editora ships, and blame’s ignore-revs settings work as on an SSH host. -
Tools in WSL (Windows). A project inside a WSL distribution, opened as
\\wsl.localhost\Ubuntu\…, can have its git, builds, tests, language servers and debuggers run inside that distribution with its own Linux tools, instead of Windows ones reading the files across the share. Editora asks once per distribution; Containers: Run This Project’s Tools Here goes back. Changes made outside Editora (agit pullor a build in the distribution) now reach the Project tree, Git and the language servers: Windows cannot watch the share, so Editora watches the folder inside the distribution (withinotifywaitwheninotify-toolsis installed, else by checking every few seconds). -
Debugging in a container or WSL distribution built on Ubuntu 26.04 no longer hangs at “Connecting”. Such images (
eclipse-temurin:25among them) ship the Rust coreutils, whosecatheld the debug adapter’s replies until the connection closed; Editora’s relay to a port inside now copies withdd. Java debugging in a container is now tested end to end: jdtls and java-debug in the container, a breakpoint hit in a project’s main class and in a loose Java file. -
Programs left in a container by a crash are stopped. A language server, debugger, build or run that Editora started in a container kept running there if Editora was killed, since ending Editora’s side of the connection does not end it. The next launch now stops it, after checking it is still the same process. WSL distributions get the same check (WSL 1 already ends such programs along with Editora). On a normal quit, the last stop request is no longer lost to the exiting app.
-
Debugging in remote folders. On a host you have allowed to run commands, Debug on a remote
.pyor.jsfile runs debugpy or vscode-js-debug on the file’s host, with breakpoints, stepping and the call stack as for a local file. The host needs its own debugpy (pip install debugpy) or vscode-js-debug and node; their locations can be set per host. Breakpoints of a remote file are kept across reconnects. Java files in a Maven or Gradle project are debugged through the jdtls on the host (Debug, Debug Main Class, Attach, Debug Test and a saved configuration); Editora copies its java-debug plugin into~/.cache/editorathere. A Java file outside a project is compiled on the host for the debugger too. A makefile at a remote project’s root shows the run-configuration toolbar, as it does locally. -
Language servers for remote folders. On a host you have allowed to run commands, a file in a remote folder is served by a language server running on its host (pyright, gopls, rust-analyzer, the TypeScript server and the others), found on the host’s PATH or configured per host: completion, hover, diagnostics, go to definition and the rest work as for local files. Renames and other cross-file edits create, move and delete files on the host, and checking such an edit before it lands no longer pauses the window for a round trip per file. A file outside the project on the same host (a library source reached by Go to Definition) is served by the project’s server. Losing the connection stops the servers without reporting a crash, and reconnecting starts them again. Java works too: jdtls runs on the host with the host’s JDKs and keeps its index in
~/.cache/editorathere (the host-consent question now says so). -
Remote folders notice outside changes. On a host you have allowed to run commands, a remote project’s folder is watched on its host, so a
git pullor a build there updates the Project tree, Git, language servers and an open file that changed, as for a local folder. Hosts withinotifywaitreport at once; others are checked every few seconds. -
Run, builds and tests for remote folders. On a host you have allowed to run commands, Run on a remote file, script / make / npm run configurations in a remote project, and Maven, Gradle, npm, Cargo and Go builds and test runs start on the host, over the same SSH connection; output, input and Stop work as for local runs. The host’s own Java is used (or a JDK configured for that host). A Java project’s main class — the gutter ▶, Run Main Class or a saved configuration — runs on the host too, with the class path its jdtls or Maven gives.
-
Find in Files and Go to File for remote folders. On a host you have allowed to run commands, Find in Files in a remote (SFTP) folder is done by the host’s own ripgrep when it has one, instead of reading every file over the connection, and Go to File lists a remote project’s files on the host. Go to Symbol has no symbols for a remote project.
-
Git for remote folders. On a host you have allowed to run commands, a repository on a remote (SFTP) host works as a local one does: branch, changed files, change bars, log and blame, and staging (whole files or single hunks), committing, branches, stashes and fetch / pull / push. It is the host’s own
git, over the same SSH connection, with the host’s credentials. Editora asks once per host before running anything there. The GitHub tool window and commands use the host’s ownghfor such a repository, signed in there. Git: Clone in a remote project’s window clones on that host, by its git, into a folder next to the project (typed as the host names it,~its home), and Git: Init creates a repository there. Fetch automatically fetches a remote repository on its host too, by the host’s git, under the same rules as a local one (a trusted folder, or one you have fetched in yourself), leaving an ssh command the host’s login profile exports alone. In a remote project that holds another repository (nested, a submodule, a worktree), the Project tree’s Git actions on its files act on that repository, as they do locally. Blame of a remote file uses the repository’s.git-blame-ignore-revs, and ablame.ignoreRevsFilein the host’s global config that the repository lacks no longer stops blame there. -
Remote folders are projects with their own window. Connecting to a remote (SFTP) folder now opens it as a project in its own window, listed with your other projects, with its own tabs and trust. Reopening it later opens the window and asks to connect; while it is not connected the Project panel says so and offers Reconnect, and the tabs you had open come back when the connection does. A lost connection is shown the same way. The window you connected from is left as it was.
-
Markdown preview: text can be selected and copied. Drag, double-click a word, triple-click a block, Shift-click, Shift+arrows and Select All work across paragraphs, headings, lists, tables, code blocks and alerts; Copy puts plain text and formatted HTML on the clipboard, and
Preview: Copycopies the selection when there is one. Going to the source line is now a double-click beside the text, Ctrl/Cmd+double-click, or “Go to Source Line” in the preview’s menu. -
Markdown wiki links.
[[note]],[[note|label]],[[note#heading]]and![[image.png]]are links in the preview and in every export, resolve to the note beside the document or the one file of that name in the project, can be followed from the source and the preview, complete after[[, are rewritten when a note is renamed, and are checked by lint (LINK003). A Backlinks tool window (Markdown: Show Backlinks) lists what links to the current file.Markdown: Convert Wiki Linkturns one into a Markdown link and back. A setting switches wiki links off. -
Remote images can be asked for per document. The remote-images setting is now Always / Ask / Never; with Ask, nothing is fetched when a document opens and a bar in the preview offers to load its remote images.
-
Markdown link updates on rename now use a link index kept while the project is open, also rewrite HTML
src/hrefpaths and wiki links, record a Local History entry before changing a file that is not open, and change a file open in another window through that window (one undo step) instead of on disk. -
PDF export draws highlight, superscript and subscript, and emoji with a bundled monochrome emoji font (Noto Emoji). Alerts are coloured and titled and definition lists indented in PDF, Word and OpenDocument exports. Highlighted code in exported HTML follows the page’s light or dark scheme.
-
Markdown source: the text line of a setext heading is styled as a heading, ticked and open task boxes are told apart, and bare URLs are styled as links.
-
Unused pasted images are cleaned up. When a document is saved, an image pasted or dropped in this session that the document no longer mentions is moved to the trash (a setting, on by default); the check and the move run in the background.
-
Command palette: a command is also found by the first part of its id, so “markdown table” finds the
Table: …commands. -
Smaller Markdown additions in the preview, print, lists and paste. Smaller Markdown additions: an image or diagram in the preview can be enlarged from the keyboard and the menu; hidden front matter is also left out of print; the default view applies to untitled Markdown buffers; ordered lists are renumbered after deleting or cutting and pasting whole items; Paste as Markdown handles merged cells, nested tables and definition lists; links in the completion documentation popup can be followed; “Disable for This Project” can edit YAML and
.markdownlint-cli2configs; a changed.markdownlintfile outside a project is noticed when the window regains focus. -
Markdown: more syntax, in the preview and in every export. GitHub alerts (
> [!NOTE],[!TIP],[!IMPORTANT],[!WARNING],[!CAUTION]), emoji shortcodes (:rocket:),==highlight==,^superscript^and~subscript~, definition lists,```mathfences and\(…\)/\[…\]math. In the preview: task checkboxes can be clicked to tick the source, a double-click on a block puts the caret on its source line, the block holding the caret is marked in Split, code blocks show their language, an image or diagram enlarges on click, front matter is a table (and can be hidden), and an empty document says so. -
Markdown preview to the side or in its own tab (
Markdown: Open Preview to the Side,Markdown: Open Preview in a Tab), following the active Markdown file or locked to one. -
Markdown completion: relative paths after
](, heading anchors after#(this file andfile.md#), reference labels, emoji after:, languages after a fence, and Mermaid keywords inside a Mermaid fence. -
Markdown links follow a renamed or moved file. Renaming or moving a file in the project offers to update the Markdown links that point to it, and a moved document’s own relative links; the setting chooses ask (default), always or never.
-
Markdown navigation: the breadcrumb shows the path of headings at the caret, and
Project: Go to Markdown Heading…searches the headings of every Markdown file in the project. -
Markdown editing commands: numbered list, block quote and code block toggles, Toggle Task Done, Renumber List, Insert Footnote, Insert Date, Insert Horizontal Rule and Insert Image…; table tools to move a row or column, sort by a column, insert a row above or a column to the left, and delete the table; link tools to edit a link, remove it, or convert between inline and reference links;
Markdown: Paste as Markdownturns copied HTML or spreadsheet cells into Markdown, and an ordinary paste does the same for HTML that holds a table, link, list or heading. Tab and Shift-Tab move a list item with its children;*and_are paired like other markers. -
Markdown: Format Document / Format Selection normalises list markers and numbering, emphasis style, heading style, blank lines around blocks, table alignment and trailing whitespace, leaving code, front matter and HTML alone.
Markdown: Number HeadingsandRemove Heading Numbersadd, update and remove section numbers. -
Markdown lint: 29 more rules — MD003, MD004, MD005, MD007, MD011, MD013, MD024, MD029, MD030, MD032, MD033, MD035, MD036, MD037, MD038, MD039, MD042, MD045, MD046, MD048, MD049, MD050, MD051, MD053, MD055, MD056, MD058, and two of Editora’s own:
LINK001(a relative link or image whose file does not exist) andLINK002(a link to a heading that is not in the linked file). Eleven have fixes. MD013 (line length) and MD033 (inline HTML) are off until enabled; MD024 flags repeated headings among siblings only. Also new: a severity per rule (error, warning, hint), Fix on Save, Fix Issues in Selection, Disable for This File / This Project,Markdown Lint: Lint Projectwith results grouped by file, an issue count in the status bar, and open files are re-linted when a.markdownlintfile changes. -
Markdown settings: default view for Markdown files, preview font size and column width, scroll sync, hide front matter, smart typography (curly quotes, dashes, ellipsis), table-of-contents options (skip the title, numbered, update on save), name pattern and alt-text prompt for pasted images, lint fix-on-save and severities, link updates on rename, and for HTML export: embed images and highlight code (both on).
-
Status bar word count for Markdown and plain text, with the selection’s count and reading time; typewriter mode keeps the caret line centred while typing. Lists and block quotes fold.
-
Exported HTML is self-contained: local images are embedded, code blocks are highlighted, and Mermaid diagrams are drawn when the Mermaid CLI is available.
-
Markdown: links inside a document can be followed.
Markdown: Open Link, Ctrl/Cmd-click and a click in the preview now follow#heading,other.md#headingand reference links ([text][label]); the jump is recorded, so Back returns to the link. The table of contents Editora generates is navigable. Link destinations with parentheses or in<…>form are read correctly. -
Markdown lint: act on an issue. Next / Previous Issue, Fix This Issue, Disable for This Line, Disable Rule and Open Rule Documentation, from the palette, the editor’s right-click menu and the Lint tool window (which gained a Fix button, a row menu with Copy, and the file name). Fix Issues reports how many issues it fixed and how many need manual changes. Project configs are read as markdownlint reads them: comments, YAML,
.markdownlint-cli2files, rule aliases and tags,extends, and the options of the rules Editora implements; a rule the project switches on wins over the global “off”. Directivesdisable-file,enable-file,capture,restoreandconfigure-fileare honoured. Bare e-mail addresses are reported under MD034. -
Markdown preview: Find searches the rendered preview when only the preview is showing. A safe subset of HTML is rendered (
<br>,<kbd>,<sub>/<sup>,<b>/<i>/<em>/<strong>/<code>,<a>,<img>,<details>/<summary>,align="center"). Footnotes are numbered and linked both ways, inline footnotes (^[…]) are recognised, the right-click menu has Copy Code Block on a code block and Copy Link Address on a link, and links can be reached with Tab. The light/dark toggle can return to “follow the app theme”; zoom and the Split divider are remembered per file. -
Markdown settings: load remote images (on by default), preview theme (Follows the app theme / Light / Dark), folder for pasted images, and the heading levels listed by the table of contents.
-
Markdown editing: Tab / Shift-Tab indent and outdent a list item; Enter on an empty nested item steps out one level; Enter on an empty last table row leaves the table; an ordered list is renumbered after Enter or a moved line; bold/italic with no selection toggle the word under the caret; typing
*,_or~over a selection wraps it. The table-size picker works from the keyboard and opens at the caret. The format bar shows the current heading level and which styles are active, and names each command’s key binding when the keymap has one. -
Exports: Word documents get real heading styles, numbered and bulleted lists, table alignment, inline images, internal links for
#headingand a document title; OpenDocument gets table alignment..mdx,.Rmd,.qmd,.mdwnand.mkdnopen as Markdown. -
LSP: Clear Java Index Cachesfrees the disk space the Java language server used. It keeps an index per Java folder you have opened (in~/.editora/jdtls-workspaces, about 40 MB each and often far more), and nothing ever removed one. The command deletes every index that no running server is using and reports the space freed; jdtls rebuilds a project’s index the next time it opens. -
Abbreviations show what they expand to. With abbrev-mode on, an abbreviation typed out in full shows its expansion as muted text after the caret (
btw → by the way), as a snippet trigger does. Tab expands it now, Escape hides the hint, and typing on expands it as before.
Changed
- Run configurations belong to projects. The No Project window has no run-configuration selector, Run or Debug buttons, and its Save, Edit, Delete and Run/Debug Configuration commands say to open a project. There you run a script or a compact Java file from its gutter ▶ or with Run File. A Maven or Gradle checkout opened as loose files no longer shows the toolbar group either. Configurations the global session saved before are kept in its state, not deleted; they are just not offered.
- Without a project, the TODO window lists only the current tab. It is hidden, stripe button included, while that tab has no TODOs, and comes back by itself on a tab or edit that has some if it was open when it was hidden. It follows edits as you type. Project windows still scan the whole project.
- Go to Definition works without a language server. When LSP is off, no server handles the file, or the server finds nothing, it looks the name up in this file and then in the project’s symbol index.
- The Run console draws colours (ANSI codes become theme colours), a
\rprogress bar stays on one line, and a clear-screen code clears it. Shell runs getTERM=xterm-256colorunless the configuration sets one. - Stop says “Stopped” instead of “Process finished with exit code 143”.
- Shell snippets follow the shebang:
if,elif,whileanduntiluse[ ]in#!/bin/shand dash scripts. New triggerselifandarith($(( … )));elseifandexprstill work. Loops andfunctionare laid out the usual way and no snippet adds a blank line after itself. - File templates follow
.editorconfigindent_styleandindent_size. New ▸ Zsh starts with the same strict preamble as the Zsh Script template. - Run Configurations suits scripts: Add proposes the open shell or Python script, Save as Run Configuration saves script configurations, Script / target has a Browse button, rows a type does not use are hidden, and labels are no longer cut off.
- Language-server status messages name their server (“bash-language-server: Analyzing workspace”) instead of always saying “Java LSP”.
- Outlines from servers that send a flat symbol list (bash-language-server among them) are nested under their functions, and a variable assigned twice is listed once.
- Hints are drawn fainter than information, and code a server marks as unused is faded.
- Shell scripts run with default settings. The gutter ▶, Run File and the Run button used to appear for a shell script only when LSP support and the Bash server were both switched on, so a new user could not run one at all. Shell Run now works like Python Run, for local and remote files.
- Run uses the interpreter the shebang names, with its flags. It used to run every shell script with
bash: a#!/bin/shscript ran under bash, a.zshfile ran under bash, and a-eor-uin the shebang was dropped, so a script relying on-ekept going after a failing step.#!/usr/bin/env -S bash -eworks. With no shebang,.zshfiles run withzshand other shell files withbash. - Program arguments and environment variables are read like a shell reads them. Backslash escapes work
(
tail\ x,"say \"hi\""), an unclosed quote is reported instead of silently swallowing the rest of the line, and environment values expand$NAMEand${NAME}(PATH=/opt/x/bin:$PATH). This applies to Run, run configurations and Debug. - A relative working directory in a run configuration is relative to the project, or to the script’s folder when there is no project, never to the folder Editora was started from. A missing directory or script is named in the error.
;;in a shellcasestatement is typed at the body’s level, as shfmt and Google’s style guide place it, and the bundledcasesnippet matches.- Shell command arguments and options are plain text, no longer string-coloured or spell-checked, so
set -euo pipefailorapt-get install libssl-devno longer gets red squiggles. Quoted strings, comments and here-doc text are still checked. - Shell scripts keep LF line endings and no byte-order mark even when
.editorconfigasks for CRLF orutf-8-bom; new shell files from New ▸ and templates are written that way. - Format Document sends the file’s own indentation (from
.editorconfigor what the file uses) to the language server instead of the global tab size, so shfmt no longer re-indents a 2-space script to 4. - Recent Files dropdown fits its names and asks before removing one. The dropdown is as wide as the longest file name, up to a limit, so names are no longer cut short. The project labels line up in one column. Clicking a row’s trash icon now asks before removing that file from the list, and the question shows the full path, so two files with the same name are easy to tell apart.
- HTTP Client: what a request sends is closer to the JetBrains format. Lines starting with
#or//inside a request body are comments and are no longer sent (shell or Markdown bodies that need such lines can go in a< ./file). Directives (# @no-redirect,# @timeout) count only above the request line, and@timeout/@connection-timeouttake units (500 ms,5 s,2 m). An@varline applies to the requests below it, so a later one can redefine it.http://requests go out as HTTP/1.1, without theUpgrade: h2cheaders the JDK used to add, andHTTP/1.1orHTTP/2on the request line is honoured.>>onto a file that exists writesname-1.json,name-2.json, … instead of skipping the save, and>>paths take{{variables}}. GraphQL, WebSocket and gRPC requests are reported as not supported instead of being sent as broken GETs. - HTTP Client: the response view shows what happened. The top line reads
404 Not Found · 12 ms · 4 B, coloured by outcome, with the protocol version above the headers and a “Request” section showing the request as sent, variables filled in. A running request shows its elapsed time, Run All shows “2 of 5: GET …” and lands on the first failure with a “3 of 13 failed” summary, and one Run / Cancel button re-sends the request the selected response came from, even after the file was edited: a named response runs only the request of that name, an unnamed one the request with the same text or URL; when it is gone, the request at the caret runs and the panel says so. Warnings have their own block with a count beside the status line, and the warnings and headers get the room their text needs. A request that was never sent reads “Not sent”, and Copy as cURL is off for it. Cancelling a Run All keeps the responses that had already arrived and says how many ran; History lists a Run All’s responses newest first. The toolbar wraps instead of shrinking to ”…”. Long lines can be wrapped, one-line XML is indented, and images are shown as pictures. - HTTP Client: history and environments are remembered per file. The last 10 responses of each
.httpfile, and its environment, are kept in Editora’s config folder and come back when the file is reopened. Bodies are capped at 1 MB; credential headers (Authorization, cookies, API keys, tokens, passwords) and every value a request read from an environment variable or.envare masked, in the saved file and in History; requests marked# @no-logare never saved. A restored response still knows how its request was sent, so Copy as cURL after a restart reproduces the upload, form or Digest login. Two windows on one file keep each other’s responses, the history follows a file renamed or moved (also from the Project tree) and is removed with a deleted one, a Run pressed right after opening a file no longer wipes the saved responses, and Export Configuration includes it only when you tick “Include HTTP response history”. Environment files are found in the file’s folder or the nearest folder above it, up to the open project’s root, else the file’s repository root; outside a repository only the file’s own folder counts. Environments defined only inhttp-client.private.env.jsonare listed. Env files may hold comments, trailing commas or a byte-order mark; one that cannot be read is named in the run’s warnings and in the underline’s tooltip, numbers are sent as written, and an env file edited in another program is picked up when the window regains focus. A chained request ({{login.response.body.$.token}}) works when requests are run one at a time; the session is cleared when the environment changes. - HTTP Client: keyboard and editor. Run Request at Caret is bound to
C-c C-c(Emacs) andCtrl+Alt+R(VS Code, CUA, Sublime, IntelliJ), Run All Requests toC-c C-r(Emacs) andCtrl+Alt+Shift+Enter(Option+Cmd+Shift+Enteron macOS; GNOME keepsCtrl+Alt+Shift+Rfor screen recording), and Cancel toC-c C-k(Emacs) andCtrl+Alt+K(Option+Cmd+Kon macOS; the IntelliJ keymap on macOS keeps Control+Option); the ▶ tooltip names both run chords. While a request runs its ▶ turns into a ■ that cancels it (a folded request keeps its ▶ or ■ on its###line), and the “Running …” line shows the request with its variables filled in. Escape in the response view returns to the editor, and the response view takes the keymap’s motion and copy keys (EmacsM-w,C-n,M->). Run File and the editor’s context menu run the file’s requests..httpfiles get request folding, one Structure entry per request, completion for methods and headers, a starter request in New File, and richer highlighting (variables, directives, JSON and XML bodies, file references, scripts). - HTTP Client: unresolved variables are underlined as you type. A
{{variable}}that cannot resolve with the selected environment, the@varlines above it and the built-ins gets a warning underline; hover for the reason; with no environment selected, it names the environments that define the variable. Typing{{offers the variables available there (a nested environment member one level at a time), the dynamic built-ins,.envkeys andname.response.for each request in the file.\{{stands for a literal{{. - HTTP Client: requests from remote files don’t run yet. On a file opened from a remote folder, Run, Run All and Cancel say so instead of sending the request from this machine, and the response view’s Run is disabled with a tooltip saying why.
- HTTP Client: an untitled
.httpfile can send requests. It uses the project’s environment files, and its responses are kept when you save it. A request that needs the file’s folder (a body file, a>>target,$dotenv) is not sent and says to save the file first. - HTTP Client: Save response writes the body exactly as received (an image saves as the image), named after the URL, in the request’s folder. The status-and-headers text report is the second choice in the dialog.
- The installed Linux app is 22 MB smaller. The bundled Java runtime no longer carries the unused client and minimal JVMs beside the server one.
- Snippet words no longer expand in the middle of a sentence. In a Markdown or plain-text document, Tab after a word such
as
code,linkorboldexpands the snippet only when the word is alone on its line or is chosen from the completion popup. - A double-click in the Markdown preview selects the word instead of jumping to the source line (see the preview selection entry above for the new ways to go to the source).
- The remote-images setting is now a choice (Always / Ask / Never); a stored “off” becomes Never.
View: Toggle Markdown Remote Imagesswitches between Always and Never. - A single tilde pair attached to the word before it is a subscript in the Markdown preview (
H~2~O); standing apart,~struck~is still strikethrough, as is~~struck~~. An ordinary paste of copied HTML that holds a table, link, list or heading arrives as Markdown. Exported HTML no longer acceptsdata:URIs as link targets, and as image sources onlydata:image/. - Word wrap is now set per kind of file: on for Markdown and plain text, off for code. “Wrap long lines in code” keeps the old setting; a new “Wrap long lines in Markdown and plain text” governs them. If you had switched word wrap on, everything still wraps. Toggle Word Wrap flips the preference that governs the file in front. A buffer with a very long unbroken run of characters opens unwrapped until toggled.
- A buffer showing only the Markdown preview refuses editing commands (with a status message) instead of editing the hidden source; switch to Editor or Split to edit.
- Markdown preview: entering Preview opens at the editor’s position, and Split keeps the two panes on the same block instead of the same scroll fraction. Code blocks and wide tables scroll sideways instead of wrapping or being squeezed. The preview menu’s “Select All” selects the preview’s text instead of copying the document, “Copy” copies the selection, and the old “Copy” (the whole document) is “Copy All”.
- Markdown lint: a front-matter
title:counts as the document’s top-level heading (as in markdownlint); the search for.markdownlint.*stops at the project or Git root; with the minimap visible the scrollbar lint stripe is hidden, since the minimap shows the same marks. - Markdown editing commands keep the caret where it was instead of selecting the changed lines; promoting an H1 leaves it an H1; a heading command on a list or quote line puts the heading behind the marker; with several carets a Markdown command collapses to one and says so. When the clipboard holds both a picture and text, paste inserts the text. Pasted images get the file’s name as alt text, and an image dropped from under the document’s own folder is linked in place instead of copied.
- Export command titles are now “File: Export Preview to PDF… / Word (.docx)… / OpenDocument (.odt)… / HTML…”;
OpenDocument export is in the File menu. The HTML and office document title comes from the front matter’s
title:, then the first heading, then the file name. Exported HTML follows the reader’s light/dark preference.
Security
- An
.httpfile can no longer send your environment secrets without asking. A request that reads$processEnv,$envor$dotenvfrom a folder you have not trusted now asks first, whatever form the read takes:{{$env NAME}}or{{$env.NAME}}, through an@varline or an environment value, in a header, a<@body file or a multipart<@part. The check follows what the request actually resolves, so no spelling slips past it. The prompt names the variables as written, never their values, and the hosts the request goes to (a redirect may lead elsewhere); declining sends none of the requests that read a secret (in a Run All the others still go), and a refused secret is never shown or saved. A request that is never sent (GraphQL, a missing body file) asks nothing and shows or saves no secret; a host chosen by an earlier response is named as such; Enter in the prompt cancels it..envis read only when it is a regular file inside the folder, up to 1 MB. It uses the same trust as build scripts, so a trusted project is asked once, and the check runs off the UI thread, so a malformed{{cannot freeze the window. Before, a request in a cloned repository could send, say,AWS_SECRET_ACCESS_KEYto any host on one click. - HTTP Client: Copy as cURL is safe to paste into bash or zsh. The URL and header names were put in the shell command
unquoted, so a crafted URL ran commands when the copied cURL was pasted into a terminal, and a body starting
with
@made curl upload a local file. Every word is quoted now, and the command reproduces what was sent:--data-binary @filefor file bodies,-Ffor forms (with their parts’ types and file names),--digest,-Land the HTTP version (--http1.0and--http2-prior-knowledgetoo). A redirected POST turns into a GET as it did in the run, and noContent-Typeis added that was not sent. Import cURL writes an imported{{as\{{, so text from a copied command never turns into a variable, and says when it did.
Fixed
- Java scripts get Java editing. A file without the
.javaname that is Java — an extensionless#!/usr/bin/env -S java --source 25script, or a file set to Java in the status bar — now gets completion (with imports, added below the shebang line), hover, the outline and syntax errors from jdtls. jdtls works only on files named.java, so it used to ignore such a script, and its test-gutter check logged a stack trace in the Debug Log on every switch to the tab. Like any.javafile outside a project, it gets syntax errors only, not type errors. Debugging such a script is unchanged. - Highlights and markers drawn over the text no longer lag the text by a frame. Find matches, symbol occurrences, whitespace markers, TODO highlights, spelling and LSP squiggles, Markdown and Mermaid lint, log levels, inline debug values, snippet fields and AceJump labels are painted after the text is laid out, like the Personal Notes indicators and the indent guides. When the line numbers gained a digit at the 1,000th line, or were toggled, one frame showed them where the text had been (8 px off in a headless probe).
- Personal Notes indicators stay on the note’s text, and cost less.
- The highlight and its corner marker are painted after the text is laid out, so they no longer sit where the text was for a frame (or more) when the line numbers gain a digit or are toggled, or the font changes.
- A note that runs onto the next row of a wrapped line paints only its own text on each row, not both rows in full. A note on a folded line is not painted, and scrolled sideways no highlight covers the line numbers.
- Typing in a file with notes no longer rebuilds the gutter of each note’s line: an Enter above 200 notes queued 400 gutter rebuilds (41 s of work in a headless probe, now 0.1 s). Opening a file and turning the indicators on or off no longer rebuild the whole gutter either (12 ms to 1.5 ms per open).
- Opening a file while you have notes on other files no longer reads and hashes the whole file (up to 5 MB) to look for a renamed file’s notes; it is hashed only when a note’s file is gone and had the same size.
- Moving the pointer over a buffer without notes no longer hit-tests it, and a click checks only the markers on screen.
- HTTP Client: a failing pre-request script is named as one. Its Tests block read “Response handler error” and its badge ”✗ handler error”; they now say “Pre-request script error” and ”✗ pre-request error”. A Tests block with only log lines is titled “Script output”, since either kind of script may have written them, and a script that runs out of time “did not finish”, not “the handler did not finish”.
- HTTP Client: a
{{name}}set by a script file is not underlined. A name a< ./pre.jsor> ./check.jsfile sets withrequest.variables.setorclient.global.setwas marked as unresolved, because only inline scripts were read. The check now reads the script files a.httpfile names (as a run finds them, up to 1 MB; reading one to find names runs nothing). An edit to a script file shows on the next check of the.httpfile. - Export Configuration leaves out the installed ShellCheck and shfmt (
plugins/tools/) and the Typst CLI (plugins/typst/), as it already did language servers and debug adapters. The zip no longer carries about 20 MB of executables built for this machine’s OS. A plugin can no longer take the idtools, so installing or removing one cannot overwrite or delete those tools. - Startup files have no Run ▶:
.bashrc,.profile,.zshrc,.xinitrc,.bash_logout,.envrcand the other rc, profile, login and session files. One stray click no longer runs them. - Debug on a shell script says it cannot be debugged and points to Run with Trace, instead of sending you to Settings. An untitled buffer no debugger handles is told so before any Save As prompt.
- Bash and dash error lines in the Run console are links (
deploy.sh: line 12: …). - Rerun and run configurations save the script they run, not whichever tab is in front.
- Shebangs with
env -u NAME,env -C DIR,-Sbash,--split-string=…or#!/bin/busybox share recognised and run correctly. - More shell files are recognised:
.bats,.commandand bash-completion scripts. - Shell highlighting:
$?and$#look like other variables;${x:+y},${x^^}and${x,,}operators are coloured; the command in${x:-$(cmd)}and the regex after=~are coloured;&>is a redirection;for i in {1..10},select … inandcoprocare right; zsh{ cmd }groups close. Function bodies now highlight as in VS Code, which also tidies C++, GraphQL, Groovy and Markdown. - Tab icons follow the file’s detected language, for shebang scripts and languages picked in the status bar.
- The symbol index for shell finds
pkg::fnandlib.fnfunctions and top-levelreadonly/declare/exportvariables, ignores text inside here-docs and multi-line strings, and indexes extension-less#!scripts. - Double-click in a shell script selects
--long-flag,a-b.shormy-funcwhole. - Toggle Comment leaves here-doc text alone when a selection reaches into a here-doc without its first line.
- A script whose workspace is the home folder, the temp folder or a filesystem root (
~/.bashrc,/tmp/x.sh) no longer makes bash-language-server scan that whole tree. - Shell scripts are opened on the language server as
shellscript, the standard language id. - Creating a script where the executable bit cannot be set (Windows, FAT drives) now says so and how to fix it.
- Shell highlighting no longer runs to the end of the file after
$((x << 2))or a<<\EOFhere-doc.$(( … ))is now coloured as arithmetic. Two tests now guard the bundled grammars. - More files are recognised as shell scripts, everywhere at once:
.envrc,/etc/bashrc,/etc/zshrcand the other system zsh files,/etc/profile,.ksh,*.bashrc,*.profile(so/etc/bash.bashrc),.mkshrc,PKGBUILD,APKBUILD,.ebuildand.eclass. Some used to open as INI, where every;started a comment; others were coloured as shell but had no comment toggling, Run or language server. - A language picked in the status bar, or a shebang typed into a new file, reaches the language server and Run straight away, and the status bar shows it. Before, only the colours changed.
- zsh startup files (
.zshrc,.zprofile,/etc/zsh/zshenv…) are no longer checked as bash, which showed false errors on valid zsh. casepatterns no longer upset bracket-pair colours (the pattern’s)showed as unmatched and threw off the enclosing function’s braces).- Typing shell code indents correctly: the body of a
caseitem is indented under its pattern,esac,fianddoneline up with the line that opened them, and a here-doc’s closing delimiter is no longer indented (bash did not recognise it, so the rest of the script became here-doc text). Nothing re-indents inside a here-doc, anddone=falseis no longer taken fordone. - Toggle Comment never comments out or breaks a script’s
#!line. - A
# regionmarker no longer empties the Structure panel for shell, Python, Ruby and other languages without block folding. - Enter after
elseorbreakin a shell script types a new line instead of expanding the snippet of the same name. Tab still expands it. - Long hovers scroll. A man page shown for a shell command made a popup thousands of pixels tall; the popup is now capped at about half the window and scrolls.
- The status bar’s LSP segment and the Problems button appear as soon as a file is opened on a server, not only after switching tabs.
read -pprompts show in the Run console. Bash prints them only to a terminal, so a script waiting for an answer showed nothing.- Windows: Run finds Git Bash and no longer picks WSL’s
bash.exe, which cannot open a Windows path. Typed input reaches a shell with Unix line endings. - Personal Notes colours match Bookmarks. Project headers in the Personal Notes tree are accent-coloured again and file headers are muted, as in Bookmarks. The two panels now share one set of style rules.
- Java completions show the whole signature. The completion list now grows to 1100 px instead of 760 px, so
long method signatures such as
Files.find(…)orMap.merge(…)are no longer cut off. It still sizes itself to the widest row, so short lists stay narrow. - A program written a moment ago no longer fails to start with “Text file busy”. On Linux, running a script
you had just saved could fail when Editora happened to be starting another process while the file was being
written. The Run tool window then showed
error: 26 (Text file busy), and the Doctor and the tool checks reported such a program as not installed. The same could stop a build through a wrapper script that had just changed (./gradlew,./mvnw), or a language server, debug adapter or AI agent that had just been installed. Editora now waits briefly and tries again. - Tabs keep their theme colours when the minimap redraws. Redrawing the minimap made JavaFX restyle the
whole window outside its normal frame. Just after a tab was opened or marked modified, that restyle could fail
to find the theme’s colours: the debug log filled with
Could not resolve '-color-fg-default'warnings, and the selected tab’s title could stay black instead of the theme’s colour until something restyled it again. The minimap now draws off screen and leaves the window alone. A redraw also costs less, roughly a third as much when the window has pending style changes. - A language server that fails to start no longer leaves its tabs looking served. When a server could not be started (its command cannot be run, or a remote connection broke while it was starting), its tabs stayed marked as served and the status bar could keep naming it until the tab was synced again. They now go quiet at once, as after a lost connection, and the server is not restarted in a loop. While Editora was finding out which servers are installed, such a server was also tried again once for every other server it checked (up to 22 failed starts at launch); now only its own check, a settings change, Restart Servers or a reconnect tries it again.
- Right-click menus close when you click outside them. A click anywhere else in the tree, list, editor or panel the menu was opened on used to leave it open, and right-clicking another row opened a second menu beside the first. Now any click outside a right-click menu closes it, in every panel, and the click still does what it would have done (selects the row, moves the caret, opens that row’s menu).
- The window moves when you drag its title. With the menu bar merged into the title bar, dragging the file name in the middle did nothing; only the empty parts of the bar moved the window.
- HTTP Client: timestamps are right outside UTC.
$timestamp,$isoTimestampand$datetime iso8601were off by the local UTC offset (six hours early in Mexico City). Day.js formats ("DD-MM-YYYY") no longer give wrong dates, and$env.NAMEand{{$randomInt 1 10}}work. - HTTP Client: nothing goes out silently wrong. A
{{variable}}that cannot be resolved (a typo, no environment selected, an earlier request not run yet, a missing.envkey) is still sent empty but is now named in the response’s warnings, as are skipped JetBrains> {% %}/< {% %}scripts. A pre-request script above a request no longer turns into the request line.{{$dotenv X}}works in@varlines. - HTTP Client: a request that fails unexpectedly reports it. An internal error or running out of memory left the view on “Running…” for good and dropped the rest of a Run All; it now shows as that request’s failure. The response history keeps at most 100 MB of bodies per file.
- HTTP Client: large multipart uploads are streamed from disk instead of read into memory, also for Digest
auth-int, and Copy as cURL fills in variables in multipart file paths. - HTTP Client: responses and requests are byte-correct. gzip and deflate responses are decoded (a browser’s
“Copy as cURL” with
accept-encodingshowed garbage), the charset of an HTML<meta>or XML prolog is used, and octet-stream, images, PDFs and archives count as binary. Request bodies use the charsetContent-Typedeclares. Emoji in URLs are encoded correctly, a stray%is escaped, and non-ASCII host names work. Multipart parts fill in variables and lose the stray trailing newline. - HTTP Client: more requests work.
GET /pathwith aHost:header, a customHost, lowercase and custom methods (PROPFIND,QUERY), a URL withouthttp://, indented headers, and the caret on a request’s###,# @nameor directive line. Digest answers SHA-256 and other RFC 7616 challenges, and Basic/Digest shorthand passwords may contain spaces.@timeoutalso stops a body that stalls. Import cURL handles browser and Windows copies (Chrome’s cmd copies with multi-line bodies included),curl.exe,$ curland/usr/bin/curl,-Fwith typed parts,--json,-d @file,-G,-I,--url-query,-H 'Name:',--http2-prior-knowledgeand options with arguments, works outside a.httpfile, and warns when body lines would be read as comments or scripts. - HTTP Client: smaller fixes.
$datetimewrites full month and weekday names (MMMM,dddd), Day.js formats such asDo,Q,d,[W]wwandGGGGcome out right, a letter Day.js does not format (outside[brackets]) is reported instead of being sent as text, and a huge date offset gives a warning instead of an error.< ./body-{{v}}.jsonpaths take variables, and an infinite$random.floatrange is reported. Indented (YAML) bodies keep their first line’s indentation. A nested environment object merges across both env files, and.envacceptsexport<TAB>and multi-line quoted values. Copy as cURL of a multipart upload imports back, and curl import keeps--http1.1/--http2and turns-T fileinto a PUT. More credential headers are masked in the saved history (X-Auth-Key,…-Key, session and signature headers). Cancelling an upload releases the file at once, and a cancelled re-run of a login no longer empties the token later requests use. Messages about headers, body files,>>saves and stalled responses are translated, the elapsed time uses your language’s decimal separator, and Escape in Preview goes back to the editor.@varlines fold with their request, browser multipart boundaries are coloured, and a Save As from.httpto.mdswaps the variable underlines for Markdown lint. - HTTP Client: saved responses are not lost, and Run on one sends the right request. A Clear keeps a
response that arrives after it, quitting waits for the last save, and a damaged entry is kept in a
.corrupt.bakcopy that the message names. Run on a History entry no longer freezes on a long URL, and a single cancelled request whose answer had already arrived says so. - HTTP Client: no file work on the UI thread. Environment files are read in the background (and by the run itself as it starts, so it sends what they hold then), and Save response writes in the background, so a slow disk or a 50 MB response no longer holds up the window.
- HTTP Client: clearer messages. “Connection refused — is a server listening on …?”, “Host not found”,
untrusted certificates and timeouts read as sentences instead of
ConnectException; failures no longer read “exit 404” or “exit 5”. A redirect to another host names the custom headers that went along, and a redirect loop or an HTTPS→HTTP redirect says why it stopped. Environment merging follows JetBrains (a private$sharedvalue no longer beats a public environment’s), nested environment objects are reachable as{{a.b}}, and an environment value may refer to another. Run File on a.httpfile no longer launchesjava api.http, and the “feature disabled” message names the right Settings page. Remote.httpfiles no longer regain the ▶ after a settings change. - Stopping a debug session can no longer hold the window on a debugger connection that is slow to close. The connection is half-closed first, so the adapter ends it, and the close itself no longer runs on the thread that pressed Stop. A close that never returned held two test runs on macOS for half an hour.
- Remote commands get what the account’s login profile sets. Only
PATHand the locale were carried over, so aJAVA_HOME,MAVEN_OPTS,GOPATHor version-manager variable exported in~/.bash_profile(or~/.zprofile,~/.profile) was missing from builds, runs, Git and language servers on the host. Every variable the profile adds is now passed on, except the session’s own (prompt, history,SSH_*, display). - Each project window acts on its own project. Back in a project’s window after opening another project, several
things used the other one: a Typst file’s
#importroot, where the Markdown lint configuration andhttp-client.env.jsonare looked up, Project: Edit Settings, the Project tree put back after Remote: Disconnect, exporting or importing run configurations, a template’s${projectName}, the folder a new file or a new project is offered, the file finder’s starting folder, and where a stack trace’s or a CI log’s files are found. A recent file of another project opened in this window after focusing that project’s; it now opens in that project’s window, where it was last left. - Snippets:
$WORKSPACE_FOLDERand$WORKSPACE_NAMEnamed the project of the window opened last, not the one the snippet was typed in: back in a project’s window after opening another project, they expanded to the other one. - The AI agent works in its own window’s project. Started in a project’s window after another project had been opened, it worked in the other project: that was its working folder and the boundary of the files it could read and write.
- ed25519 keys work for remote folders. A login whose only key is ed25519 — what
ssh-keygenmakes by default — failed with “No more authentication methods available”, and a server offering only an ed25519 host key could not be reached at all. Editora now ships Bouncy Castle, which the SSH library needs for them. - A remote connection that goes silent is noticed. Editora asks the server “are you there?” every 30 s and now gives up after three unanswered asks (about a minute and a half), so a network that drops packets instead of refusing them no longer leaves a window holding a dead folder until TCP times out.
- Starting a program on a host right after stopping another is no longer refused. The place the stopped one held is freed a moment after the stop; a start waits up to 5 s for it instead of reporting that too many programs are running.
- Git in a project window with no file open followed the project of the last window focused, not its own: once another project’s window had been used, closing this window’s last tab made it say “Not a Git repository” and refuse every Git command.
- Remote: trusting a folder on a server no longer also trusts the local folder with the same path (and the
other way round).
Remote: Disconnectnow closes the SSH connection, not only its file channel. - Previews: the floating Editor / Split / Preview toggle covered the right end of the HTTP response panel’s toolbar (hiding Clear and Save response), the CSV grid’s toolbar and the first row of the JSON / YAML / XML tree. Those previews now start below the toggle, as the Markdown preview already did.
- Settings ▸ Sync: the reason Connect was refused (no repository or branch, an unreachable repository, a GitHub error) could be replaced by “Not connected.” a moment later, when the GitHub sign-in check finished. It now stays until the repository is edited, Connect is tried again, or sync is disconnected.
- Markdown Lint: Lint Project showed no results when the Lint tool window was closed: opening the window
cancelled the scan it was opened for. A
.markdownlintfile saved twice in quick succession could be read from a stale cache. A lint squiggle could be left where the text used to start when the gutter was sized after the first paint. - Word and OpenDocument and PDF exports dropped the text of a wiki link; it is now written as a link.
- Markdown Lint: Fix Issues no longer rewrites code. Indented code blocks, fences nested in lists and block quotes, HTML blocks and comments, and YAML or TOML front matter are left exactly as written, by lint and by Fix. A closing fence with an info string no longer flips code and prose for the rest of the file. MD026 no longer cuts an HTML entity; a directive that names a rule by its alias no longer disables every rule; a config file with a comment is no longer ignored. Fix keeps the caret and scroll position. The Lint tool window follows the active tab. Squiggles are drawn on empty lines and on each row of a wrapped line. Lint messages are translated.
- Math is recognised when the document is parsed, in the preview and in the HTML, clipboard, Word,
OpenDocument and PDF outputs alike:
\,,\\,\{and*inside a formula survive, multi-line$$blocks render everywhere, shell variables in prose ($HOME/bin:$PATH) and$…$inside code are no longer taken for formulas. Math and Mermaid diagrams are drawn for the preview’s own theme. - The Markdown preview no longer rebuilds the whole document on every edit. An edit rebuilds the block it
touches; a long document is built a slice at a time. Long inline code wraps instead of being clipped; a missing
image shows its alt text; a changed local image is reloaded; image paths with
%20,?raw=trueor a leading/resolve; a document with one very long line keeps its live preview. Right-clicking a link no longer opens it. Remote images are fetched from the address that was checked. - Word and OpenDocument exports write a soft line break as a space, so paragraphs reflow. File: Open Last Exported File opens office and HTML exports. Exported HTML forbids scripts.
- Markdown source: front matter and inline HTML are highlighted; strikethrough, quotes, list markers and table
pipes are styled; Kotlin, TOML and Mermaid fences are highlighted. Folding, the outline, spell check and list and
table editing share one reading of code fences, front matter and HTML blocks, so
~~~fences, nested fences and commented-out headings are handled the same everywhere. The outline and table of contents show a heading’s text without its markup, and their anchors match the exports. Spell check covers link text and image alt text and skips front matter. - Markdown editing: line-wise commands stop at the selection’s last line and skip blank lines; inline toggles
no longer produce markup that does not render; Enter in the middle of a table no longer splits the row; table
keys leave code blocks alone and work in block-quoted tables; columns align for CJK text; dragging a web link
onto a document inserts a link instead of saving the page as an image; block snippets (
note,tip, …) expand only at the start of a line; table commands say why they cannot apply.