Desktop Devlog - Markdown, Vim, local files and more

0.0.93

  • fix: sql query overflow in fullscreen mode
  • feat: support multiple sql queries in a single sql block
  • feat: add Vim support to most codemirror blocks (enable in settings, all blocks coming soon)
  • feat: add markdown exporting
  • feat: add URL copy button to top bar

Vim in code editors

We’ve added Vim mode to the core code editors - mainly the script and terminal blocks. It’ll be coming to all blocks in the next release!

Markdown export

Available via File → Export → Markdown with any runbook open. We are developing an extension to markdown that supports rich block exports, in a way that is easily human-editable. Your feedback is very much appreciated here!

An example:

# SQL
A collection of test SQL queries

Blocks are represented as code blocks, with types, and properties encoded as "front matter".

```
---
type: clickhouse
name: Clickhouse 1
uri: foo/bar
---
select * from foo
```

```
---
type: terminal
code: ls
name: Terminal 1
---
ls
```

While not part of the exporter right now, types will (optionally) be specified in the fence blocks

```sqlite
---
name: SQLite 1
uri: /Users/ellie/.local/share/atuin/history.db
---
select * from users;
```

Next: type specifiers with the fences, and figuring out how nested blocks could work

Coming up

We’ve been a little quiet on releases, but have two big new features coming soon

Offline, file backed workspaces

No sync, designate a directory as a workspace and we will load/save files from there. Perfect if you’d rather use Git to transfer runbooks, or wish to keep them alongside code in a repo.

These will work with the fully-lossless atrb files, which are essentially just a JSON representation of our runbooks.

CLI execution engine

Currently, runbook execution is tied closely with the desktop app. The goal here is to ensure the two are properly separate, and enable runbooks to be executed from the CLI.

Let us know what you think!

3 Likes