Repository navigation
Baram v0.8.0 lets scripts and AI clients read your notes: the program that opens the editor
now also answers from a terminal, and serves the same read-only commands to AI clients that
speak MCP, such as Claude Code. Plugins can put their commands in the right-click and slash
menus, draw code blocks, show a sidebar panel, mark files in the file tree and read your links,
tags and tasks, and you can give their commands keyboard shortcuts. A new Mode setting keeps
a theme that has both a light and a dark palette in the one you choose. Most of the rest are
fixes for ways Baram could lose or rewrite your text: when updating, in file windows and
Untitled tabs, when creating a file, and when saving.
If you are updating from v0.7.7, these are the changes most likely to catch you out:
- Save your open documents before you press Install & Restart. v0.7.7 runs this update
itself, and it installs and restarts without asking about unsaved changes (see Updating
at the end). - The System (Auto) theme card is now called Baram Default, and a new Mode row sits
below the gallery. - Renaming a file no longer moves it to another folder: a new name containing
/is
refused. - A front-matter tag written with
#, as intags: ["#solo"], is now the same tag as#solo
in your text, so two rows in the tag panel can become one. - In the search panel, replacement text without a regular expression is now inserted exactly
as typed:$$,$&and the rest are no longer special. With a regular expression,$&,
$`,$'and$<name>are no longer special; use$0and${name}, and write${1}a
rather than$1a, which now reads as a group named1a. - A file window's close button now closes only that window, and a tab with unsaved changes, or
an Untitled tab, can no longer be dragged out into its own window. - A trusted plugin written for the old editor calls (
getContent,setContent) stops working
until its author updates it.
New and improved
Read your notes from a terminal
baram, the program that opens the editor, now also answers questions about a vault from a
terminal. It is meant for scripts and AI agents. Nine commands — vaults, files, read,
search, tags, tag, tasks, backlinks and links — print one item per line with its
fields separated by tabs, or one JSON object with --json; read prints the file itself.
They read the files on disk, so the app does not need to be open, and edits you have not saved
in it are not seen. None of the commands changes a file in your vault or the app's settings.
- On macOS, run
/Applications/Baram.app/Contents/MacOS/baram. The Linux.debpackage puts
baramon yourPATH. On Windows the commands are built in, but it has not been confirmed
yet that their output reaches a terminal. --vaultnames the vault to read, by its path or by the name the app shows for it. Without
it, the registered vault or folder that contains the current directory is read. A vault that
cannot be found is an error; the commands never fall back to the vault that was last open in
the app.- With no arguments, or with an absolute path or a URL as its first argument,
baramopens the
app as before. Any other first argument is now read as a command:baram notes.md, which
used to open a window, now stops with a usage error and opens none.
The new Command line page of the documentation lists every command, its output and its
error codes, and has an example to paste into an agent's instructions.
Let an AI client read your notes
baram mcp serves the same nine commands as tools to an AI client that speaks the Model
Context Protocol (MCP), such as Claude Code. The client starts the server itself; you add it
to the client's settings once. The tools only read.
- You choose what the client may read. Without
--vault, every vault and folder registered
in the app is open to it. With--vault, only the vaults you name, and the first one is the
default. - The tools reach less than the commands do, because a model picks their arguments.
read_noteopens notes only —.mdand.markdownfiles, not hidden ones and none inside
node_modules— where the command line'sreadreads any text file in the vault. - Long lists and long notes come back a page at a time.
- It has been tried with Claude Code. The setup the documentation gives for Claude Desktop has
not been tried with Claude Desktop yet, and on Windows the server has not been verified yet.
The new MCP server page of the documentation shows how to add it to Claude Code and to
Claude Desktop.
Plugins can do more
- Right-click and slash menus. A plugin can add its commands to the editor's right-click
menu, where they come last, below a line, grouped by plugin and with the plugin's name beside
each item, and to the slash menu, where they come last under “Plugin ·” and the plugin's name. - Shortcuts for plugin commands. You can give a command a plugin declares a keyboard
shortcut in Settings › Keybindings, under Plugins. A plugin cannot choose a key itself,
and a key that one of Baram's own commands has on that page cannot be given to a plugin
command. A few keys Baram uses that are not listed there, such as the zoom keys, are not
checked. - Code blocks a plugin draws. A plugin can draw the fenced code blocks of the languages it
declares. Its install dialog lists them under Code blocks it draws:, and an update that
adds a language asks you again. A drawn block is labelled with the plugin's name and has a
Show source button. HTML and PDF exports use the drawing; a block that was never drawn
exports as ordinary code. - Sidebar panels for sandboxed plugins. A sandboxed plugin can have up to three sidebar
panels, which Baram draws for it. The activity bar button names the panel, then “Plugin ·”
and the plugin's name. - The file tree. A plugin with the new permission “Show icons and badges on files in the
file tree, and add items to its right-click menu” can mark a row with a badge, an icon, a
colour or a tooltip, and add items to the menu a file or folder row opens.
When this version was released (8 November 2026), none of the plugins in the marketplace used
any of these yet.
Light or dark, whatever your system uses
Settings › Appearance has a new Mode row below the theme gallery: System, Light or
Dark. It picks which palette a theme that has both a light and a dark one shows — Baram's
default palettes, or Baram Hangul from the theme registry, for example — so the editor can stay
dark while your system is light, or the other way round. System follows your system, as
before.
- The row is hidden while you use a theme that has only one mode, because that theme's mode
always applies. Your choice is kept and applies again when you switch back to a theme that
has both. - It is your setting, not an appearance dial: a theme cannot suggest it, and Export Look as
Theme... does not include it. - The System (Auto) card in the gallery is now called Baram Default, because “System”
is now a mode. It is the same theme, and it stays selected if you were using it.
Table column resizing can be turned off
Settings › Markdown has a new switch under Tables: Adjustable table column widths, on
by default. With it off, the handles on column borders go away and a click near a border is an
ordinary click, so no new width comment (<!-- colwidths:... -->) is written above a table.
Turning it off also removes the widths you set from the tables in your open tabs. Those tables
go back to widths that fit their content, and their tabs are marked unsaved; once they are
saved, the files no longer hold the width comments. The switch itself writes nothing to disk:
the active tab is saved by autosave if you use it, and another tab when you save it. A file
you open while the switch is off keeps its widths, and its comment stays when you save.
Backlinks keep up with changes made outside Baram
The link index behind the backlinks panel and the graph did not notice changes another program
made to your notes — git, a sync tool, another editor. Now, when files change in a vault Baram
is watching (the active one and any you opened this session), Baram updates its link index
within about two seconds, and the panel and the graph read it again.
The panel's Unlinked mentions are now searched again when another note's text changes,
even when its links did not, and no longer every time you save the note you are looking at —
that search reads every other note in the vault.
Rename a PDF or an image
Renaming a PDF, an image or another file that is not text failed with “Rename failed: …”. It now
renames the file and, as for a note, rewrites the wikilinks and block references that point at
it. A PDF's highlights and its companion note move with it, and a tab open on a file that moved
follows it.
When you rename a file (not a folder), some links Baram does not rewrite are now reported
instead of left to break without a word. A markdown link or image ([text](file),
) or an HTML src or poster attribute that points at the renamed file is left
as it is, and the note holding it is counted in “Renamed, but … file(s) may still link to the
old name.”
Vim moves more like Vim
With Vim Keybindings on, in the WYSIWYG editor:
jandkremember the column you started from when they pass a shorter line, an empty
line, a formula or a table row, and go back to it on a longer line. After$, they follow
the end of each line.Escout of insert mode puts the cursor on the last character you typed, and collapses a
selection you made in insert mode. The cursor no longer rests past the end of a line after
x,d$or a click there.gg,Gand:Nland on the first non-blank character of the line, as^does.dj,yjandcjon the last line, anddk,ykandckon the first, now do nothing,
as in Vim.djanddkused to delete the line.- The normal-mode cursor now shows on an empty line in front matter and between two hard line
breaks, where it was invisible.
Faster in a few places
- Find in a long document. While Find has a search in it, every keystroke searches the
document again. The step that turns the document into text for that search took time that
grew with the document's length times its number of blocks; it now grows with its length
only. Closing Find from the menu now also ends the
search and clears its highlights — before, only the bar went away and the hidden search kept
running on every edit. - AI chat. Baram saved the whole chat history for every piece of a reply as it streamed
in. It now saves at most once every 250 ms while a reply streams, and at once when the reply
ends, fails or is stopped. Text appears as fast as before. Quitting and reloading wait up to
3 seconds for the history to be saved. If Baram stops unexpectedly in the middle of a reply,
the last quarter of a second or so of it may not have been saved. - Startup. The formula fonts that HTML and PDF exports embed are no longer loaded when Baram
starts, only the first time you export a document that has a formula. journal-photosblocks draw each photo from a smaller copy, chosen by the layout and the
number of columns, instead of decoding the full photo. A photo shows as an empty square
until its smaller copy is ready, and an animated GIF or WebP larger than that copy shows its
first frame. Exporting the block to HTML or PDF now uses the same copies, in the same grid as
on screen, except that a one-row strip wraps into rows in a PDF.- Closing a tab lets go of the file's text. Baram kept the text of every file you had opened
in memory until it quit, and read a closed file again whenever it changed on disk. In AI
chat,@folder:still puts in the text of the files open in tabs and lists the rest by
path, so a file you have closed is now listed by path, where before its text went in if you
had opened it this session. Separately,@file:now reads a file that is not open in a tab
from disk, so a file you never opened goes in with its text; before, it went in as its path,
or with text Baram kept from earlier in the session.
For plugin authors
This release adds a lot to the plugin API. Set engines.baram to >=0.8.0 in a plugin that
uses any of it: v0.7.7 then refuses to install it. Without that floor, v0.7.7 still refuses a
manifest that declares the new codeblocks or filetree capability (“unknown capability”),
but installs one that uses the rest of the new API, which is not there for it to call.
- One editor API for both tiers.
context.editoris now the same asynchronous API in
trusted and sandboxed plugins:getMarkdown,getText,getSelection, which now also
returns areffor replacing exactly that range later, the newinsertMarkdown, which
inserts parsed markdown at the selection or at aref,insertTextandsetMarkdown.
Refusals come with acodeto branch on (the page names the main errors that carry none). A
trusted plugin written for the old synchronous calls breaks:getContent()and
setContent()are gone (the oldsetContentemptied the document), andinsertTextinserts
the characters as they are instead of reading them as HTML. The “Context: commands, editor,
files, events” page has a table for moving over. When this version was released, neither
plugin in the marketplace used the removed calls. - Menus and shortcuts.
contributions.menu(up to 5 items) andcontributions.slash(up to
10) put commands you declare incontributions.commandsinto the editor's right-click menu
and the slash menu. Amenuitem withwhen: "selection"shows only over selected text.
Users assign keys to your commands; a plugin cannot. - Code block renderers. With the
codeblockscapability andcontributions.codeBlocks(up
to 10 languages),context.codeBlocks.register(lang, render)draws fenced blocks of those
languages from the{ html, css? }your renderer returns, which Baram sanitizes and draws in
a shadow root. A language Baram draws itself (mermaid,query,svg,journal-…) or
already highlights cannot be declared. See “Code block renderers”. - Sidebar panels for sandboxed plugins.
contributions.panels(up to 3, withsidebar)
andcontext.ui.setPanel(id, { html, css? }), with the same sanitizing and click handling
as code blocks. A trusted manifest that declarespanelsis refused; trusted plugins keep
ui.addSidebarPanel. See “Sidebar panels”. - The file tree. With
filetree,context.ui.setFileDecorations,clearFileDecorations
anddefineFileIconput badges, icons, colours and tooltips on rows, in both tiers, and
contributions.fileMenu(up to 5) adds items to a row's right-click menu, whose command
receives the item clicked or the items selected. See “File tree decorations”. - Index reads.
context.index—backlinks,links,tags,notesWithTag,tasksand
search— reads a vault's links, tags, tasks and text as saved on disk.filesor
files:readonlyopens it. See “Context: index”. - Events.
vault:changedsays a vault's contents changed, including changes made outside
Baram, so you can read again.file:renameandfile:deletereport renames, moves and
deletions made in Baram. All three needfilesorfiles:readonly, notevents. - Editable file viewers. A trusted plugin's file viewer can now edit the file it shows:
register it witheditable: trueand agetTextfunction; the plugin needsfiles. Baram
still does the saving, the unsaved mark and autosave. See “Editable file viewers”. - New examples in the Baram repository:
link-count,backlinks-block,tree-badgesand
sketch-pad.
Fixed
Unsaved work
- Updating could discard unsaved changes. Install & Restart went straight to
installing, and installing ends Baram, so anything not yet saved was lost. Once the download
finishes, Baram now asks about unsaved documents first — Save & Install, Don't Save
or Cancel — and after Cancel, pressing the button again uses the update it already
downloaded. This check is part of v0.8.0, so it protects the updates after this one. The
update to v0.8.0 is run by v0.7.7, which does not ask. - Text in an Untitled tab did not count as unsaved, so quitting, reloading, closing the
workspace,Cmd+W/Ctrl+Wand the tab's close button discarded it without asking. They
ask now; an empty Untitled tab still closes quietly. Saving such a tab now saves what it
holds: Save As on an Untitled tab in the background used to write an empty file. - Close Other Tabs and Close Tabs to the Right closed tabs with unsaved changes without
asking. They now ask, with Save & Close Tabs. - File windows (a tab dragged out into a window of its own):
- Their close button could quit the whole app. It now closes that window only, and asks
first — Save & Close, Don't Save or Cancel — when the window has unsaved
changes. - Quitting and installing an update did not count what file windows held. They do now, and
Save & Quit or Save & Install saves in those windows too, waiting up to 10 seconds;
if one cannot save, quitting or installing stops. - Menu commands chosen in a file window acted on the main window's active tab:
Cmd+W/
Ctrl+Wclosed a tab you were not looking at, and Insert › Bold changed its
document out of sight. Save, Close Tab, Toggle Source Mode and the Insert
menu now act on the file window. Commands that cannot work there, such as Save As...,
Export..., Find & Replace and Close Workspace, say “This isn't available in a
separate window.” Others, such as New File and Settings..., bring the main window
to the front. - Closing the last main-window tab of a file you had opened on its own, while a file window
also had it open, or closing the vault a file window's file belongs to, made the file
window's saves fail until the file or its vault was opened again in the main window, or
Baram restarted. They keep working now. - A file window marked its document unsaved as soon as it opened, and autosave never cleared
the mark. It now starts clear, and autosave clears it. In source mode,Cmd+S/Ctrl+S
saved the older document; it saves what you see now. Undo right after a file window opened
no longer empties the document. - A tab with unsaved changes, or an Untitled tab, can no longer be dragged out into its own
window. The new window reads the file from disk, so the unsaved text would have been lost.
Baram says “Save this tab before moving it to its own window.”
- Their close button could quit the whole app. It now closes that window only, and asks
- Source mode. Typing and then switching to source mode within the autosave delay could
write the older document and mark the tab saved, and closing the tab then lost what you had
typed in source mode. The Insert menu no longer changes the hidden document while you are
in source mode — what it inserted was wiped when you switched back. It says “This works on
the document. Leave source mode first.” - Typing while a save was being written left the tab marked saved, so closing it then
discarded what you had just typed. The tab stays unsaved now, and the next save writes it. - Renaming a file while an autosave was waiting brought the file back under its old name.
The save now goes to the new name. - One tab's text could end up in another file. After a code or other non-markdown tab was
reloaded, typing in a tab whose file had been deleted outside Baram could save the other
file's text into it. A link that a rename rewrote in a tab waiting behind a non-markdown tab
could be lost when you saved, and reloading a large document while it was still loading
repeated some of its blocks.
Files that could be overwritten
- A journal entry Baram could not read was replaced by the template. When today's entry,
or one opened from the calendar or a date link, existed but could not be read — not valid
UTF-8, or refused by the system — Baram treated it as missing and wrote a new entry over it.
It now writes nothing unless the file is really not there. Weekly notes and the Work Log had
the same fault and are fixed too. - New File in the file tree replaced a file that already had that name with an empty one.
On a disk that ignores case, as macOS and Windows disks usually do,README.mdreplaced
readme.mdthe same way. It now changes nothing and tells you that the name already exists. - A wikilink that found no note could overwrite one.
Cmd+clicking such a link (Ctrl
on Windows and Linux), or choosingCreate "…"in the[[menu, wrote# nameover a file
already at that path. It now leaves the file alone and says that the file already exists,
but this link does not find it, and that no new note was created. The[[menu also no
longer offersCreate "…"
for a link a click would already open.
Text that changed when saved
- Brackets were saved with backslashes.
[important],[1]or[@smith2020, p. 3]in
ordinary text was saved as\[important]and so on. It is now saved as you typed it, except
where a bracket could start something, such as a footnote ([^), a task box at the start of
a line, or a link. Pandoc exports still show such brackets as text. $_GET and $_POSTin plain text was saved so that it reopened as a formula. It is saved
as text now.- Inside code and formulas, a backslash before
#was dropped (\#definebecame
#define), and at the end of a line in code, formulas and HTML blocks was removed.
Both are kept now. - Highlight, subscript and superscript (
==…==,~…~,^…^) saved their text without
escaping it, so[a](b)in a highlight reopened as a link and<b>disappeared. The text is
escaped now, so a file that has such text can change the next time it is saved
(==a*b==becomes==a\*b==) and reopens the same. Where the short form could not be read
back, Baram saves a<mark>,<sub>or<sup>tag instead. - Strikethrough with a space at either end, or with a punctuation mark at an end and a
letter right outside it, was saved in a form that did not close (a ~~e ~~f), and reopened
without the strikethrough. It now reopens as it was. - A backslash before a letter next to bold or italic text turned that letter into a
character code such asn. Fixed. - An HTML block you edited stayed one HTML block even when the file would read it back
differently: a<div>with a blank line inside reopened as three blocks. When you leave the
block, Baram now turns text that reads back as other blocks into those blocks — undo brings
the HTML block back — and otherwise keeps your text and tells you it will read differently,
or may merge with the blocks next to it, when the file is opened again. - A quote, callout or footnote whose first block was HTML lost everything inside it when
saved; a quote was left as a lone>. A paragraph or heading that started with a footnote
reference, in a file that defines the footnote, lost the text after it. Both keep their
text now. One case got worse: an<img>tag right after that footnote reference
([^1] <img src="a.png">) was kept as an image in v0.7.7, and is now not shown and is
removed when the file is saved. An<img>or<video>tag in a paragraph that also has
formatting or other inline content (bold, italic, strikethrough, code, a formula, a link, a
footnote reference, or a character reference such as&) was already not shown and
removed on save, and still is. So is a<br>, or another HTML tag Baram does not read such
as<span>, in a paragraph or heading with no<img>or<video>tag. - Clicking a table's column border without dragging wrote a column-width comment into the
file. Only a drag that changes a width does now.
Links, backlinks and renames
- References with a path —
[[./note]],[[../folder/note]],((folder/note#^id))— did
not appear in the backlinks panel, and renaming the note or a block ID missed them. They
appear and are rewritten now. - Renaming a note no longer rewrites links into another vault (
[[work::note]]), which it
used to break, and they are no longer listed as backlinks of a local note of that name. If
two registered vaults share a name, links that start with it are left alone, and renaming a
note reports the files in its vault that hold them. - Changing only the case of the letters A to Z in a name (
Note.mdtonote.md) failed
with “already exists”
on macOS and Windows, and so, on macOS, did changing only how its letters are composed in
Unicode. Both work now. A new name containing/used to move the file into
another folder and quietly break its relative links; it is refused now. - The backlinks panel lists files by path and line, instead of an order that could change
after a save. - Names stored decomposed. Some macOS tools store Korean and accented names in decomposed
Unicode (NFD), so[[회의록]]typed in a note did not find회의록.md. A link now finds such
a note when you click it, in previews and embeds, in the[[menu, the Quick Switcher, tree
search and@file:, in backlinks, the graph and unlinked mentions, and when renaming. Names
Baram writes into a link — from the[[menu, Tab completion, Copy as Wikilink in the
file tree, Copy wikilink in the graph, Copy link in the block menu or Link in
unlinked mentions — are written composed. Cmd+clicking a wikilink (Ctrl+click on Windows and Linux) could open the[[
suggestion menu instead of the note, and so could a plain click on a date link. Both go to the
note now.- A PDF's backlinks now count the links that name it with its extension —
[[Paper.pdf]],
![[Paper.pdf]], with a path, a heading or display text — and no longer[[Paper]], which
names a note called Paper. - A note's own block reference (
((#^id))) could resolve to another note of the same name.
It resolves to its own note now. - Renaming
old.mdtoold.txtleft[[old]]pointing at nothing. It becomes
[[old.txt]]. - Renaming in the file tree and pressing Enter showed “Rename failed: …” although the item
had been renamed, and pressing Esc after typing a new name renamed the item anyway. Enter
now renames once, and Esc leaves the old name. - Suggestions after
[[./or[[../were always “No matching pages” on macOS and Linux,
and on Windows[[./could offer the files of every folder in the vault. The[[menu now
lists the vault's files in the folder the prefix points to, counted from the open note's
folder. - On Windows, clicking a relative wikilink such as
[[./plan]]or[[../other/far]]did
not open the note: Baram treated it as a link that finds no note, so[[./plan]]could
create a newplan.mdat the top of the vault instead. Also on Windows, in a file opened on
its own outside a vault,[[plan]]pointed at/plan.mdinstead of the file next to it.
Both now resolve against the open note's folder, and the[[work::menu groups another
vault's notes by folder on Windows too. - More links on Windows missed what they point at: a path link that names the open vault
by its alias ([[work::skills/analyzer]]in a note ofwork) found nothing;[[plan]]in
a journal entry could open a note of the same name from another folder, and the preview or
embed of[[2026-10-06]]could show one; a markdown link to a file, such as
[text](Paper.pdf)or[text](../other/far.md), did nothing; andCtrl+clicking a path in
a Skills file did not open it. They now open what they point at. On macOS and Linux, a
folder such asnotes-old/next to a journal'snotes/no longer counts asnotes/, a
Skills path starting with../now opens its file, and one starting with./reuses the
file's open tab instead of opening a second one.
Tags and front matter
- A front-matter tag written with
#(tags: ["#solo"]) is now the tagsolo— in the
tag panel, the graph, the tag bar and the command line — and counts together with#soloin
your text. It used to be a separate tag#solo, shown as##soloin the tag bar. A colour
you gave the#solorow in the tag panel moves tosolo, unlesssoloalready had one. - A comment after a list item (
- plain # memo) was read as part of the tag, making a tag
calledplain # memo. It is the tagplainnow, as YAML reads it, and renaming the tag keeps
the comment. - Items of a
tags:list that was not indented were not counted. They are now. - Renaming a tag now changes every spelling of it in front matter, written the way you
wrote it, and nothing else. It used to miss quoted items in a block list, and could change
other fields, a list in the body or the start of a longer tag. A new name that a tag cannot
have is refused, instead of being written into front matter YAML could not read. - The tag bar, the properties panel and new Zettel notes wrote front matter YAML could not
read: addingxtotags: ["#solo"]with the tag bar wrotetags: [#solo, x], and a value
or a Zettel title such asPlan: v2was written without quotes. They write front matter YAML
reads back now. When the tag bar or the properties panel cannot change a field safely, it
leaves it alone and says so — for the tag bar, “These tags can't be changed here. Edit them in
the front matter YAML.” - Editing one value in the properties panel wrote the whole front matter again, losing
block lists, comments and nested values. Only that key's lines change now. Analiases:
block list shows as items you can edit, where it showed as""and disappeared when edited. - A tag name with a space (
my tag) is no longer accepted where you type a tag name, since
text in a note cannot spell it.
Search
- Replace in the search panel (
Cmd+Shift+F/Ctrl+Shift+F) found matches its own way,
which could differ from the list: with Match whole word, Replace All could change a
match the list did not show; a regular expression such as^xwas applied to the whole file
at once, not line by line as the list searches; and replacing the second match on a line
changed the first. It now finds matches the way the list does, line by line and with the
same whole-word rule, and a match's own button replaces that match. In a regular
expression's replacement, use$0for the match and${name}for a named group. If a
replace fails, the panel says why and searches again. - Match whole word with a regular expression put the word boundaries around the expression
without grouping it, soa|bfound text starting withaor ending withb. It now finds
the wordaor the wordb, in Find and in the search panel. - The preview of a very long match in search results is now cut at 300 characters, with
…where it is cut.
Startup
- Restoring at launch. When Baram restored your vault at launch and the journal or the
Zettel home note opened on startup, the vault tab moved to that space while the file tree
stayed on your vault. Restore last file and New file under On Launch (Settings ›
General) did the same as Restore last folder once Baram had a vault or folder to restore,
and the file recorded as last opened was often not the one you were last looking at. Now the
vault tab, the file tree and the active tab all show the restored vault, the journal entry or
home note opens behind it, Restore last file reopens the file you were last looking at,
and New file opens a new file in your last vault. - Opening a file from another vault — from a wikilink, the task panel, recent files or your
operating system — now switches the vault tab and the file tree to that vault too, not only
the editor.
Editor
- The guide line under a numbered list item, with Align numbers (the default) chosen
for List number alignment, hung to the right of the number, near the period, and further
right in deeper lists. It now hangs from the number. If you use the
Bullet Threading plugin, update it to 2.1.1, which draws its highlight on the same line; when
this version was released, the plugin registry offered 2.1.1. - Formulas in Mermaid labels (
$$…$$) showed as empty boxes. They now appear inside their
node. MathML inside an SVG's<foreignObject>, in ansvgcode block or an HTML block, now
appears too. - A table could be drawn at the column widths of another tab's table. Switching tabs, or
opening a file, could show a table that had no widths of its own at the widths of the table
in the same place in the tab you left, and dragging one of its columns could then save those
widths into the file. Each table now gets its own widths.
Accessibility
- VoiceOver read every file tree row as a group, without its file name. It now reads the
rows as items of a tree, with the file name and any plugin badge.
Plugins
- Pressing Esc to close a plugin's quick pick could put an escape control character into
the note in place of the selection, when the selection spanned paragraphs or was a whole
block. Fixed. - On macOS, a sandboxed plugin could stop running a few seconds after Baram last sent it a
message, so its own timers stopped firing. On macOS 14 and later it keeps running now, though
its repeating timers fire at most about once a second, because its window is hidden.
Updating. If you are on v0.7.7, save your open documents — in file windows too — before
you press Install & Restart: v0.7.7 runs this update itself, and it installs and restarts
without asking about unsaved changes. From v0.8.0 on, Baram asks first. Press Install &
Restart in the update dialog and Baram installs in place and restarts. If an install fails,
Baram opens the releases page instead.