Editora 0.22.0: tools on the host, wiki links and HTTP scripts
Editora 0.22.0 is out. Remote folders now work like local ones: the tools Editora drives run on the host, and a project’s tools can also run in its container or WSL distribution. Markdown gets wiki links, backlinks and a much larger lint, the HTTP Client runs scripts and asks before it sends a secret, shell scripts get a full pass from highlighting to Run, and there is a round of everyday editing commands. Download it from the 0.22.0 release page.
Remote development
Until now a remote (SFTP) folder was a place to open and save files. The first time you open a folder on a host, Editora asks once whether it may run commands there. Once you allow it, the tools Editora drives run on that host, over the same SSH connection:
- Git and GitHub: branch, change bars, log and blame, staging hunks,
commits, stashes, fetch, pull and push, using the host’s own
git, credentials andgh. Clone and Init work on the host too. - Language servers: pyright, gopls, rust-analyzer, the TypeScript server, jdtls and the rest run on the host, with completion, diagnostics, go to definition and renames that create and move files there.
- Run, builds and tests: Run, script, make and npm configurations, and Maven, Gradle, npm, Cargo and Go builds and tests. Output, input and Stop work as they do locally.
- Debugging: debugpy, vscode-js-debug and java-debug, with breakpoints, stepping and the call stack.
- Search: Find in Files uses the host’s ripgrep, and Go to File lists the project’s files there.
- Outside changes: a
git pullor a build on the host updates the Project tree, Git, the language servers and open files.
Each remote folder is a project with its own window, its own tabs and its own trust. Reopening it asks to connect, and your tabs come back once it does. Settings → Remote lists which hosts may run commands, and lets you set the command for each tool on a host whose PATH does not find the right one. It works with OpenSSH servers on Linux and macOS, and with dropbear. ed25519 keys work, remote commands get what the account’s login profile exports, and a connection that goes silent is dropped after about a minute and a half. More about remote folders.
Tools in a container or WSL
The same works for a project on this machine whose tools live somewhere else:
- In a container. If the project folder is mounted into a running Docker or Podman container, Editora can run its Git, builds, tests, Run, language servers and debuggers inside it, with the container’s PATH, environment and user, while you edit the files here. Editora finds the dev container that VS Code or the Dev Containers CLI started for the folder, or you pick one with Containers: Run This Project’s Tools in a Container…. A debugger listening on a port inside is reached whatever the container’s network, and the Java index survives a restart.
- In WSL (Windows). A project opened as
\\wsl.localhost\Ubuntu\…can run the same tools inside the distribution, with its Linux toolchain, instead of Windows tools reading across the share. Agit pullor a build there is picked up at once withinotify-tools.
Editora asks once per container or distribution, and Containers: Run This Project’s Tools Here goes back. If Editora crashes, the next launch stops what it left running there. More about containers and WSL.
File encodings
A file that is not valid UTF-8 used to open through a lossless stand-in, and you could not say what it really was. Click the encoding in the status bar:
- Reopen with Encoding… reads the file again in the encoding you pick, from Shift_JIS, GBK, Big5 and windows-1251 to every other encoding the JDK knows. If the file is not valid in it, nothing changes and the status line says where.
- Save with Encoding… writes the file in another encoding from its next save, and refuses text the encoding cannot hold instead of writing question marks.
The choice is remembered for the file, also for files on a remote host. An encoding Editora had to guess is shown in the warning colour. More about file encodings.
Editing
- Line commands that work at every cursor: Insert Line Below and Above, Delete Line, Select Line, and Indent and Outdent Lines.
- Multiple cursors: Split Selection into Lines, Add Carets to Line Ends, Skip Occurrence and Remove Last Added Caret.
- Text tools in the String Manipulation picker: encode and decode Base64, URL,
JSON, HTML and
\uXXXXtext, increment and decrement the number at each cursor, keep or remove the lines matching a pattern, and two more sorts. - Rulers at any columns, with their own set per language, and indent guides, on by default.
- Save All, Revert File and Reopen Closed Tab (
Ctrl+Shift+T). The File menu keeps its export formats under Export. - Emacs registers:
C-x r sandC-x r ifor text,C-x r SPCandC-x r jfor places.
See line commands and text tools, multiple cursors, rulers and indent guides and Emacs heritage.
Markdown
Three passes over Markdown since 0.21.0:
-
Wiki links:
[[note]],[[note|label]],[[note#heading]]and![[image.png]]resolve, complete after[[, are followed from the source and the preview, and are checked by lint. A Backlinks window lists what links to the current note. -
Links follow a renamed or moved file, kept up to date through an index of the project’s links, including files open in other windows.
-
More syntax, in the preview and in every export: GitHub alerts, emoji shortcodes, highlight, superscript and subscript, definition lists and math.
-
The preview can be selected and copied, opened to the side or in its own tab, searched with Find, and its task boxes ticked with a click.
-
Lint has 29 more rules, including checks for broken relative links and heading anchors. You can act on an issue from the editor, fix issues on save and lint the whole project.
-
Editing: Format Document, numbered headings, table and link tools, Paste as Markdown, completion of paths, anchors and emoji, and a search over every heading in the project.
-
Exports: self-contained HTML, Word documents with real heading styles and lists, and emoji in PDFs.
-
Writing: a status-bar word count with reading time, and typewriter mode.
-
Remote images can be set to Ask, which offers to load them per document, and an image you pasted that the document no longer mentions goes to the trash on save.
HTTP Client
- Scripts, as in the JetBrains client. Response handlers (
> {% … %}or> ./check.js) run on your Node.js with theclientandresponseAPI, and a Tests block lists each test’s result.# @assertand# @capturechecks need no JavaScript. - Pre-request scripts (
< {% … %}or< ./sign.js) run before a request is sent, withrequest.variables.set,cryptoandjwtfor signing. - Debug Request runs a request’s scripts under the JavaScript debugger,
with breakpoints in the
{% %}blocks. - Your secrets stay put unless you say so. A request that reads
$processEnv,$envor$dotenvin a folder you have not trusted asks first. The prompt names the variables and the hosts, never the values. - Copy as cURL is safe to paste into a shell, and reproduces uploads, forms and Digest logins.
- The response view shows what happened: status, time and size on one line, the request as it was sent, and the warnings.
- History and environments are remembered per file, with credential headers masked.
- Closer to the JetBrains format: comment lines in a body, directives, timeouts with units, and HTTP/1.1 by default.
- Keys to run a request (
C-c C-c, orCtrl+Alt+Rin the GUI keymaps), run the file and cancel, and unresolved variables are underlined as you type.
Shell scripts
A full pass over shell support, from highlighting to Run:
- Scripts run as their shebang says. A shell script runs with the default
settings, with no language server needed, using the interpreter and flags its
#!line names (#!/bin/sh,#!/usr/bin/env -S bash -e), orbashwhen there is none. A run configuration can set the interpreter instead. - The Run console shows a script’s
read -pprompts, has End Input for scripts that read until the end of input, draws colours, keeps a progress bar on one line, and links bash errors to their line. - Run with Trace runs a bash script with
-x, and each traced line links to the line that ran. Startup files such as.bashrchave no Run ▶. - ShellCheck and shfmt in one click. Settings and Doctor show whether they are installed, and Editora can download the official releases, checked against hashes built into it. The Bash card in Settings sets ShellCheck’s arguments and shfmt’s style, and Problems shows each ShellCheck rule with a link to its page.
- Highlighting stays right after
$((x << 2))and<<\EOFhere-docs;.envrc,/etc/zshrcand.kshfiles open as shell, and vim and emacs modelines set the language. - Editing:
casestatements and here-docs indent correctly, scripts fold, Toggle Comment leaves the#!line alone, spell check skips command arguments, and a script with Windows line endings gets a notice that converts it.
More about running scripts and ShellCheck and shfmt.
Also
- The Run, Output, Test Results, Debug and External Tools windows show a spinner while something runs, so a quiet build no longer looks stalled.
- Word wrap is set per kind of file: on for Markdown and plain text, off for code.
- Abbreviations show what they expand to as muted text after the caret, and Tab expands them.
LSP: Clear Java Index Cachesfrees the disk space jdtls’s per-folder indexes take.- The Recent Files dropdown fits long names and asks before removing one.
- Run configurations belong to projects: the No Project window has no run-configuration selector, and the gutter ▶ still runs a file.
- Without a project, the TODO window lists only the current tab, and hides while that tab has no TODOs.
- The installed Linux app is 22 MB smaller.
- Java scripts: an extension-less
java --source 25script gets completion, hover, the outline and syntax errors from jdtls. - Go to Definition without a language server falls back to the file and the project’s symbol index.
- Export Configuration leaves out the installed ShellCheck, shfmt and Typst CLI.
- Fixes: each project window acts on its own project, right-click menus close when you click outside them, the window drags by its title, and Java completions show the whole signature.
The full list is in the changelog.