What changed in every version

1.135.0 The canvas opens up: link and image cards

September 14, 2026

The previous version brought shapes, groups and a shared stacking order to the surface. This version delivers the second half of what was announced with the canvas: a card no longer carries only its own text, it can also show the content of another document or an image from your area. And because such a link is a link like any other, it appears in the target's backlinks, in the document's outgoing links and in the link graph. What is still missing and will follow: operation without a mouse, a portable export of the surface and exchange with other tools.

• Instead of its own text, a card can take a target and show that content on the surface — the whole document or, with an anchor, exactly the heading or the block. The content cannot be edited there and is not copied into the surface; if it is longer than the card, the card scrolls. The header shows the card's label, and if you gave none, the target together with its anchor. Such a card is created through 'Add link card to canvas' in the View menu, through the command palette or through the canvas context menu; you enter the target in a field that suggests names from your area. On the selected card the same entry appears in a small bar with the field 'Link target', 'Open target' and 'Remove link' — that is how a text card becomes a link card and turns back again, and its text stays where it was. A double click on the displayed content opens the document at the place referred to; a double click on the header still edits the label. If the target changes in another open document, the card refreshes itself.
• The same card also takes an image instead of a document. It is fitted into the card and keeps its aspect ratio — it is neither distorted nor cropped — and follows the card when you change its size; an image card never scrolls. The image reaches the display by the same route as an image in running text, and the input field 'Image' suggests the image names of your area. A double click on the image opens the file the way you open any attachment. If the image is missing, too large for display, or the extension names no image at all, the card says so in a message of its own instead of staying empty.
• A target on a canvas is from now on a link like any other. The referenced document names the canvas in its backlinks, with line, anchor and a short excerpt marked 'on a canvas'; the document holding the canvas names the target in its outgoing links as 'Link card on a canvas'; and the link graph gains the corresponding line. If you rename the target or move it to another folder, the cards follow just like links in running text, and the rest of the surface stays intact character for character. An image still creates neither a line nor a backlink, and a link you write into the card's own text stays outside the network as before.
• The manual page 'Canvas surface' has gained three new chapters in all five languages: link cards, image cards and links in the network of the area. The chapter on the storage format describes the two new card entries and says what happens on an empty, duplicate or invalid value; the limits of the surface are stated anew — the displayed content cannot be edited in the card, embeds inside that content are not resolved any further, a change to a target file that is open nowhere appears the next time the surface is drawn, and a connection still runs between cards only. The feature overview lists link and image cards as entries of their own, and the bundled demo stop '12 Canvas' shows both: a card pointing to a page of the collection and a card with a bundled image.

1.134.0 The canvas grows: shapes, groups and stacking order

September 12, 2026

The previous version brought the canvas: cards with their own text, freely arranged and joined by labelled, coloured lines. This version delivers the first half of what was announced there. The surface now takes geometric shapes in six types and group rectangles that carry their members along when moved; and all elements share one stacking order that you change with four commands. What is still missing and will follow: link and image cards as well as operation without a mouse.

• Alongside the cards there are now rectangle, rounded rectangle, ellipse, triangle, diamond and star. They are created through 'Insert shape' in the canvas context menu or through 'Add shape to canvas' in the View menu. The selected shape shows a small bar: it changes the type, sets outline and fill colour from the same eight colours the lines use, leaves the fill out entirely and takes a label. The label is simple, centred text and not Markdown, which remains the difference from a card. What you grab is always the drawn figure and not the rectangle around it: a click in the empty corner beside a triangle hits whatever lies behind. And the outline does not keep the aspect ratio, an ellipse pulled wide stays wide.
• A group is a labelled, tinted rectangle around other elements. It appears at the very back so that it covers nothing, and its interior stays transparent to the pointer: a double click in the middle of it still creates a card, while the group itself is grabbed by its edge, its label or its handle. A member is anything that lies entirely inside its rectangle, the edges counting as inside; a line is never a member, and a group inside a group comes along. Moving takes the members with it, resizing moves nothing, deleting leaves them where they are. Who is a member is settled when the drag begins, and the whole drag is exactly one undo step. The group's bar carries the eight colours, the way back to the default colour and the label.
• Cards, shapes and groups sit in one shared layer, and their order in the document is their order in the picture; a card therefore no longer sits above a shape as a matter of course. Four commands arrange them: bring to front, bring forward, send backward and send to back. They are reachable at the selected element through the context menu, through the 'Canvas stacking order' submenu in the View menu and through the command palette. A new card and a new shape appear at the front, a new group at the back; the connecting lines stay in a layer of their own and are not affected.
• The manual page 'Canvas surface' has gained three new chapters in all five languages: shapes, groups together with their membership, and the stacking order on the surface. The chapter on the storage format describes the two new building blocks with their values, their defaults and the behaviour on an unknown entry, and the limits of the surface are stated anew: shapes and groups now belong to it, free drawing still does not exist, and a line still runs between cards only. The feature overview lists shapes, groups and the stacking order as entries of their own, and the bundled demo stop '12 Canvas' shows a group with two cards inside it as well as two shapes, one with fill and label and one without either.

1.133.0 Your setup, your language, your overview

September 12, 2026

Anyone who uses an application for long enough sets it up to their liking: colors, shortcuts, buttons, templates, bookmarks — and sometimes the language itself. Until now that work was tied to one computer. From this version on it can be written into a readable file and read back in elsewhere — in full or in part, and with a preview that says beforehand what will happen. Anyone who needs a sixth language translates the interface themselves. And anyone who has gathered many areas, books and bookshelves finally sees them all on one page.

• What you have set up can now be written into a file and read back in elsewhere — on a second computer, after a fresh installation, or as a safeguard before a larger rebuild. What can travel along: behaviour and appearance, your color schemes, the keyboard shortcuts, the layout of the format toolbar, your own buttons together with their macros, the sidebar arrangement, template folder and rules, the bookmarks and the on/off state of the extensions. Before writing you choose what goes along; every line says how many entries lie behind it. The routes are in the menu under “File → Settings”.
• The file is ordinary Markdown and no black box: at the top stand version, time and origin, and below them one named section of its own for each kind of data. You can open it in this application, read it in any editor, compare two states and keep it under version control. No person can be read out of it — it names the program and its version, not you and not your computer.
• Reading a file in writes nothing before you have confirmed it. A preview tells you, for each kind of data, what will be added, what replaced, what renamed and what skipped, and if you wish a button backs up your current state beforehand into a file of its own. Behind it stands a single rule: what you yourself created as a named object is added to, what is a setting or an arrangement is replaced. If something read in carries the name of something already there, the existing one stays unchanged and the new one comes alongside it with a distinguishing suffix.
• Calendar systems belong to their area and until now travelled only with its folder. Now a single one of them can be written out and read into another area instead of being built up there a second time: in the selection, under the calendar systems, every block stands on a line of its own. The calendar holdings of the other area are kept in full, and a system whose definition is incomplete is rejected and named rather than arriving by halves.
• What an external extension has deposited in its own storage space never goes along — precisely because the application does not know that material and an access key may lie there. Whether an extension is switched on or off does travel along; that is setup, not a secret. Also left out are the session state with its paths, the workspaces and areas you have set up, and your decision which external extension you trust on this computer — that belongs to each computer individually.
• The interface comes in five supplied languages. If you need a sixth — a regional language, a language no other program serves, or simply your own choice of words in your own field —, you can now translate it yourself. The route has three steps: download the template, translate it in your own editor, load it in. What your language is called you enter into the file itself, not into its name. When it is loaded in, everything is checked before anything is taken over: if something is wrong, the message names the entry it hangs on, and what you already have stays untouched. Your language then stands in the language selection of the status bar next to the supplied ones and takes effect in the window, in the menus and in the dialogs of the operating system — after a restart as well. The routes are in the menu under “File → Your own language”.
• Your translation does not have to be finished in order to work. Whatever is still missing from your language file appears in English — entry by entry, not page by page or dialog by dialog. So you can start with what you have in front of you every day and catch up with the rest in stages. English labels next to your own are therefore not a program error but the visible gaps in your translation; they close as soon as the passages concerned stand in the file and it has been loaded in again.
• An application that grows brings in texts that a file translated earlier cannot know. The application tells you so: after a new program version, a note in the status bar names your language and how much is still missing — once per state and not at every start. “Update…” in the same submenu provides the means: it saves your language file at the level of the running version, with your naming and your translations, and the missing passages stand in their place in English. You translate what is still English and load the file in again.
• Workspaces, areas, books and bookshelves lie scattered across your disk, and until now the overview existed only in your head. “View → My Extended Memory” opens a page on which everything you have added there stands side by side. Adding is done by hand: an expandable suggestion names the containers you opened most recently and your workspaces, “Choose folder…” takes in every other one, and which kind of container a folder is, the application recognises by itself. Nothing is searched for: no drive is scanned, and nothing appears on the page that you did not put there yourself. An entry can just as easily be removed again — only the entry disappears, your files remain untouched. From every row you open the container, and the page also carries the way to export and import your settings. Anyone who does not need it switches it off among the extensions.
• For every added container the page shows key figures: how many Markdown files it holds, how many other files and folders, how much storage they occupy, for a book the chapters, for a bookshelf the books. Next to them it always says when those figures were collected — because they age. They are collected when the container is added, and after that only when you ask for it; nothing runs in the background. That has an advantage: a container on a disconnected drive or a detached network share does not vanish from the list but stays there with its last known figures, marked as unreachable. For an area that is not currently open, tags, tasks and files without an incoming link stay open instead of showing zero: the page builds no index for that, and a zero would be a statement nobody collected. “Details” on each row fans out all the figures and, for an area, leads on to the full area statistics.

1.132.0 The canvas: a surface for arranging

September 11, 2026

Until now, everything EM4me showed was ordered from top to bottom. With this version an ordinary Markdown file can carry a surface: cards with their own text, freely arranged and joined by labelled, coloured lines. Unlike the graph view the surface computes nothing, it keeps what you have laid out, and because it sits as plain text inside the document, the card texts stay readable without EM4me too. This is the first stage: shapes, groups, link and image cards as well as operation without a mouse will follow.

• The canvas sits in an ordinary code block of the document and therefore needs neither a new file type nor a new format. The file stays a Markdown file, is found by the full-text search, returns with the session and can be opened in any other text program; there the canvas appears as readable plain text, card by card. Anything EM4me does not know when saving is left untouched, and an unchanged canvas is written back character for character exactly as it was.
• Alongside the rendered view, the source, the split view, the live mode and the mind map there is now the canvas. A keystroke (Ctrl+6), a menu entry or the status bar button leads into it, and switching does not change the file; the view can be panned, zoomed and fitted to its contents. It is only offered for a document that actually holds a canvas. Otherwise button and menu entry stay visible but dimmed, and their title gives the reason.
• A double click on the empty surface creates a card, a double click inside the card opens its text, a click beside it accepts the text and Escape discards it. Cards can be dragged, resized and deleted with Del. Card text is ordinary Markdown and is shown as such, with headings, lists and emphasis; if it does not fit the card, the card scrolls instead of growing by itself. Every action on the canvas is exactly one undo step, and for each there are three ways: mouse, context menu and command palette.
• A selected card shows connection handles on its four sides; dragging from a handle onto another card creates the connection. A small bar appears at the selected line. It toggles the direction (an arrow at one end, at both ends or none at all), reverses the line, colours it in one of eight colours, the same ones the tab groups use, lets it be labelled and deleted again. The connection sides can be chosen as well: while dragging, through zones at the edge of the target card, afterwards through two select fields on the line. The lines follow their cards while these are being dragged, and deleting a card takes its lines with it.
• If a document holds more than one canvas, a narrow bar above it names them all; a click switches. The label is derived from the first card, so nothing additional has to be written into the file, and the chosen canvas stays chosen while you keep writing.
• In the rendered view, in print and in the PDF a block stands in place of the canvas: it names kind and size, previews the first card texts and leads with a button into exactly that canvas; it can be collapsed. In live mode it unfolds to plain text as soon as the cursor touches it, so a card text can be changed without switching to the canvas view. In the mind map a short note gives kind and size.
• The command 'Canvas' is in the Insert submenu of the editor context menu and in the command palette, where table, footnote and code block are too. It places the empty canvas at the cursor; the canvas view is then available for this document.
• The switch 'Canvas view' is in the settings under Extensions, in the 'Appearance' group. When it is off, view, button, menu entries and commands disappear, and the canvas appears as an ordinary code block: the document stays readable, the card texts stay visible, nothing is lost. If it is switched off while a canvas is open, the document moves to the rendered view instead of being stuck in a view without an exit.
• As long as a document is not opened for editing, the canvas offers no handles, no dragging, no creating and no input. Viewing, panning, zooming and selecting an element remain possible as before.
• The view switch buttons in the status bar were already disabled when they did not apply, for instance on the program's own pages such as the settings, but they still looked unchanged. The difference is now visible, in the light as well as in the dark appearance.
• The new manual page 'Canvas surface' describes operation, storage format and limits in all five languages and carries a real canvas to try out; it deliberately sets the canvas apart from the graph view, because both show boxes and lines and mean different things. The bundled demo workspace has a new stop on the guided tour, '12 Canvas'.

1.131.1 Availability, up-to-date views and access paths

September 11, 2026

The menu and the command palette now follow the same rule for deciding what is applicable in the current situation — anything that cannot do anything right now is recognisable as such in both places, no longer only in the menu. When an open file is changed outside the program, the new state reaches every view again and not only the open document itself, and a panel that appears in the sidebar while you work now also comes to the front instead of staying hidden behind a neighbouring tab. Tables in documents exported in portable form also stay readable for screen readers: every cell is assigned to its column or its row again.

• Six entries could be triggered from the command palette in any situation so far and then did nothing: “Close Area”, “Close Book”, “Close Bookshelf”, “Move chapter file”, “Rejoin parts” and the mind map view. They now appear dimmed as long as the matching context is missing — without an open area, without an active book, without an active bookshelf, without an open document of your own, or on a page of the program itself; “Close Area” also stays dimmed in a book or bookshelf window. It is the same rule the menu has been using to grey these entries out all along. No entry has disappeared, and the availability of every other command is unchanged.
• If you have a file open and change it outside the program — or switch a status straight from a query — the new state now also appears in result lists, in embedded documents, in the reference views and in the graph, and no longer only in the open document itself. Until now those views quietly stayed on the earlier state: the checkmark set by a click in a query did not appear there, and a second click took it back again. The document you are working in behaves as before.
• Adding a bookmark, clicking a tag in the text and the first bookmark of a section now always bring the matching panel to the front. Until now it could be shown and still stay hidden behind a neighbouring tab: the input field for the name of the new bookmark was then invisible, and whatever you typed went into it unseen; the filtered tag list and the newly shown bookmark section stayed covered in the same way.
• If you export a document in portable form and read it with a screen reader, every table cell is assigned to its column or its row again. Until now that assignment was lost when the exported document was displayed, so a data table was read out as a plain sequence of values. Nothing changes visually.

1.131.0 Area-wide editing and output polish

September 8, 2026

Whatever can be found in an area can now also be replaced there — in a single run across all files, including the ones that were never opened. The familiar results list becomes the preview, and every changed file keeps its previous version.

• Search and replace now works across a whole area instead of just the open file. The run also covers files that were never opened. Regular expressions with backreferences work as usual, and writing stays strictly inside the area.
• There is a checkbox in front of every match and every file; everything is selected to begin with. Whatever stays ticked gets replaced. A file shows whether it is fully, partly or not selected at all, and the selection survives collapsing a group or repeating the same search.
• Before anything is written, the previous version goes into the document history — even when history is switched off. If the previous version cannot be secured, the file is not written. The history view of the file in question leads back to the version from before the run.
• A file that is open with unsaved changes is replaced in its tab and stays unsaved; nothing is saved without your doing, and a single undo takes the whole run back there. After the run a report names the changed files, the skipped ones with their reason, and those that have changed since the search.
• Once an area is open, the search reaches it — even when no file is open at the moment. This used to require an open tab; the bound area is now enough. With a file open, everything works as before.
• The arrow keys moved the selection in the results list exactly once, after which it stopped responding and the Enter key found no target. Both work again. Stepping on with F3 from the search bar behaves unchanged.
• A task in a query result list now runs as continuous text: checkbox, description and markers in one sequence, just as the same task looks in the document. With a long description the entry used to break into three stacked lines; now the text wraps within itself, and its continuation sits indented below its start. This applies to the rendered view, the live view and PDF output.
• Below the period label, the navigation block of every journal entry now states how that entry relates to now: “Today” as before, otherwise “yesterday”, “3 weeks ago”, “in 2 years”. It counts in the unit of the entry — a weekly entry speaks of weeks, a yearly one of years. Until now the line stayed empty for everything but the running period.
• The arrows to the previous and next entry are buttons with an area of their own instead of bare characters, and beside each one stands the name of the period it leads to. When the block gets narrow the name gives way and the button stays; its tooltip still carries the full name.
• In the navigation block every period whose entry already exists carries a dot — the parent ones above, the current one and both neighbours. It is the same dot as in the calendar and the timeline. So before clicking you can see whether it opens an existing entry or creates a new one.
• Right-clicking a tag in the sidebar renames it across all its occurrences in the area — in body text as well as in the tag field, in every file, including the ones that are not currently open. Sub-tags come along: “project” becomes “work”, and “project/alpha” becomes “work/alpha”. A tag that merely starts with the same word stays untouched.
• Before renaming, the familiar results list shows every occurrence with its line and marks the sub-tags that come along. Individual occurrences can be deselected; nothing is written until you confirm. The previous state of every changed file goes into the version history, and cancelling leaves everything as it was.
• Until now the anchor part of a web address counted as a tag: “https://example.org/#section” produced the tag “section”. Such entries now disappear from the tag overview, from autocompletion and from queries. They were never meant to be there — and when renaming, writing would have destroyed the address. A genuine tag in the same paragraph is still recognised.

1.130.0 Areas that know about each other

September 7, 2026

An area used to be a self-contained workspace: whatever lay outside stayed outside. That remains true — with one exception that you set yourself. You can link two areas and then refer from one to the other using a short prefix. Knowledge grows beyond a single folder; references between bodies of notes are the rule, not the exception.

• An area can now know about other areas. You enter where the other area is stored and give it a short prefix to address it by — set up under Settings, "Current area", section "Area links". Each direction is set up on its own and may use its own prefix. The entry belongs to the area and travels with its folder. A folder that is currently unreachable may be entered all the same.
• Put the prefix in front of the file name and the link points into the other area: [[File]] becomes [[@prefix:File]]. Path, anchor and your own display text all still work, and the form works as an embed too. The search runs in two steps: first where the path points inside the other area, and if nothing is there, by name across its whole set of files. The area boundary otherwise stays hard — only what one of your own entries covers is ever opened.
• When an area opens, the application checks whether the linked areas are still there, and it tells two cases apart. If the folder is gone while the place above it is reachable, it has evidently been moved: you are asked where it is now, and until you say so the affected links count as invalid. If the place above it is already unreachable — a drive is disconnected, a network share is signed out — the area only counts as absent, and your links are left alone. So a link is never doubted merely because a drive happens to be unplugged.
• A link to a prefix that does not exist is marked in the text, and so is one to a file that cannot be found in the other area. Links into an absent area stay unmarked.
• For each link you can tick a box that adds the templates of the other area. Your own templates always come first, the added ones behind them; the list names the origin of every template. Without the tick nothing changes.
• The whole feature can be switched off under Settings, "Extensions". After that, prefixed links are ordinary text, the check on opening does not run, and templates come from your own folder alone.
• You know a file’s name and want to open it — until now that meant unfolding the folder tree or going by way of a full-text hit. Now Ctrl+T is enough. Type part of the name, choose with the arrow keys, Enter opens it. The search covers file names and frontmatter aliases; with no input, what you worked on last is on top. The search space is your open area, and without an area the neighbourhood of the file currently open.
• Area statistics has always given the number of files nothing links to — which files those were, it did not say. Notable files now carries a fourth list that names them; a click opens the file. That list is complete and not capped at ten entries, because a shortened answer to the question of what is left dangling in your material would be no answer. The value of the figure itself now leads there too, by mouse and by keyboard. A defined start page stays out of it: it is the entry point of your area and needs no link pointing to it. The number therefore comes out one lower than before.
• The graph view shows your material as a network: what is connected to what. What it does not show is the order — seen from an entry point, at what depth. There is now a second presentation for that in the same tab: the tree. It starts at a document of your choice, by default the start page of the area, and expands from there. Every file appears in it exactly once, on its shortest path to the root; if two equally long paths lead there, the name decides. So a file you do not find where you expect it is further up. You change the root via its name in the toolbar or via the context menu of a file in the area panel. A footer says how many files cannot be reached from this root at all — the tree shows what hangs below it, not the whole area.

1.129.1 Process quality

September 6, 2026

Seven places work the way the application promises again: an unresponsive window can be closed without costing you the work in the others. Embedded documents, script output and the notes preview show their diagrams and queries. A very large file no longer slows down search across the whole area. And backlinks, the graph view and suggestions see what you are currently typing, not just the last saved state.

• If a window's display stopped responding, the hint with «Close anyway» appeared but the window stayed open. It now closes, and tab order and window position are back after a restart. What stays unchanged matters just as much: a slow but responsive window is never torn away, and an open save prompt may stand for as long as you need.
• A Mermaid diagram inside an embedded document, in the output of a script block or in the notes preview stayed source text, and a query stayed empty. Where content comes from is invisible while reading — so was the fact that the same construct worked in one place and stayed silent in another. The same processing now applies everywhere. Embedded content still cannot be edited: it is a view, and a click inside it would write to a file that is not even open.
• An area's search space keeps its texts in memory and gives that up beyond a limit. Until now that limit counted across the whole area: a single very large file used it up, and search across every other document became noticeably slower. Now only the large file stays outside, and the rest keeps its speed.
• When editing an event from the overview, the application detected an intervening external change by the file's modification time. But that also changes when a sync or backup tool rewrites a file unchanged. It now compares the values it read.
• Fourteen manual pages still used the Windows product name in English, Spanish, French and Italian, even though the application also runs on Linux.
• A link you are just placing in another open document only appeared in its target’s backlinks after saving. Freshly drawn connections were likewise missing from the graph, and a heading you had just typed could not be offered as a jump target. All three now work on the written state — you see what is taking shape as you write, without saving in between.
• An area’s key figures show the saved state. That stays, because text not yet saved has neither a file size nor a modification time, and half-overlaid numbers would be harder to read than clear ones. What is new is that the page says so: above the figures it states that they show the saved state, and how many of your open documents currently carry unsaved changes.

1.129.0 Working closer to the document

September 6, 2026

This release takes on the places where working on a document still required a detour: tables can be typed into as tables in the live view, folders and files are managed in the area panel itself, printing no longer goes through a PDF file, and what you embed or pass on actually arrives at the other end.

• In the live view a table stayed a typeset grid only as long as you left it alone; the moment the caret reached it, it unfolded into its pipe characters. That is over. You click into a cell, type there, and move on with the tab key or the arrow keys — and the table keeps looking the way it will look in the end. If you do need the raw syntax, for instance the colons that align a column, switch to the source or the split view.
• A block anchor makes a single spot in your text addressable — and for that it used to sit as ^id in the middle of the running text, even in the live view, which otherwise shows everything typeset. Now a small, discreet marker sits at the end of the line. Point at it and it names the identifier; click it and the caret jumps there, with the anchor open for editing. Unlike the rendered view, which hides the anchor completely, the live view deliberately keeps it visible: while restructuring a document you should see which paragraphs are pointed at from elsewhere, instead of deleting a link target unnoticed.
• When you passed a file on as portable Markdown, the diagram in it used to be the one thing the recipient could do nothing with: they received the source text from which the application draws the picture — and the application was precisely what they did not have. Now the finished picture is in the file. It is always drawn light, so it does not depend on the colour scheme you work in. Only a diagram whose source is faulty stays behind as a code block — then at least you hold the source rather than an error message.
• The area panel used to only display your area. Anyone wanting to create a folder or get rid of a file went to the file manager and came back. Now a right-click does it on the spot: on a folder a subfolder or a new file, on a file rename and delete. Renaming carries the references to that file along, just as you know it from the menu — only now for every file in the area and not just the one currently open. Deleting moves the file to your operating system's recycle bin, not permanently: you are asked first, the question names the file, and you restore it where you are used to doing so. Only references to a deleted file stay as they are and become broken links — when deleting there is no replacement target, and a broken link at least shows you that something used to be there.
• Until now the way to paper went through three steps: export as PDF, open the file in another program, print from there — and what remained was a file nobody wanted to keep. Now «Print» sits in the file menu, on Ctrl+P as everywhere else. Your operating system's print dialog opens, where you choose printer, pages and copies the way you are used to. What ends up on paper is exactly what the PDF would show — the same rendering, always printed light, and the source view still prints the source.
• When you embed an image, the application used to look for it only exactly where the path pointed — while it had long found an embedded document by its name anywhere in the area. The same notation, two behaviours, and nothing about it was visible: all you saw was the missing image, although the file sits two folders away. Now the same route applies to every kind — first the path next to your file, then the subpage notation, finally the bare name within the area. The search stays inside your area; anything outside is not embedded. And what you see on screen is now also in the printout: output waits until the embeddings are complete instead of printing an empty spot.

1.128.0 Safe saving and traceable changes

September 6, 2026

An interrupted save can no longer damage a file: after every save the file holds either the complete old content or the complete new content, never half of either. On network drives and in synchronisation folders, saving is also more reliable than before. And document history now records who made a change, and on which machine.

• Document history now records, for every change, the login name and the machine it was made on, and shows both in two separate columns. If you work on several devices you can see where a change was made; once you share documents with others, also by whom. The entry is a statement of fact at the time of the change, not a user account: it is read, never altered afterwards, and where nothing could be determined the column stays empty. It only arises where history is switched on, and it travels with a document you pass on — the manual explains what that means.
• When saving, EM4me first writes the new content next to the file and only then puts it in its place. If the machine crashes mid-save or the power fails, the document survives intact in its last complete state. Previously a half-written content could remain at that moment, and the larger the file, the wider that window was.
• On a network drive or in a synchronised folder, other programs sometimes hold a file for a moment — a virus scanner or the synchronisation service, for instance. In such a case EM4me now retries for several seconds instead of giving up straight away. Only where waiting demonstrably does not help does it report the failure at once, with its reason.

1.127.2 Complete journal properties

September 4, 2026

Journal entries now carry the same complete set of frontmatter properties for every period length, and existing entries can be brought up to that state. A query across journals therefore finds every entry without having to distinguish between day, week, month, quarter and year.

• Previously an entry carried either the period date or its start and end, never both. Now every entry carries both, and the period date is always the first day of the period. For daily entries the three values therefore coincide.
• The property was intended and its field name configurable per journal, but the program never wrote it. Every entry now names the journal it belongs to in its frontmatter. You can see which series a document comes from without reading the folder path.
• If an existing entry is missing properties, they are added silently when it is opened. For a whole collection there is the command “Add journal properties…”, which states beforehand how many entries it will check and asks for confirmation. In both cases only what is missing is added: a value you set yourself stays untouched.

1.127.1 Technical maintenance release

September 2, 2026

This is a purely technical maintenance release with no change to the feature set. It widens the internal numbering space of the project documentation so that it lasts for the years ahead; the behaviour of the application does not change.

• The internal identifiers of the project documentation now carry longer numbers and will last for the remaining life of the project. Nothing changes for your work with the application; upgrading to this release is not required.

1.127.0 An area opens at its first page

September 2, 2026

An area can now carry a fixed entry page. It opens by itself, the way a book falls open at its first page. If you keep an overview, a table of contents or your running notes there, you find them without a detour — and if you designate nothing, everything works as before.

• In the area panel, a right-click on a file is enough to make it the start page of the area. It is then marked in the list with a leading symbol and bold type. For that file the entry reads 'Remove start page', for every other one 'Set as start page' — so you cannot remove anything where there is nothing to remove. The designation belongs to the area and travels with its folder.
• Restoring your last session takes precedence. If an area comes back at program start with the documents you had open, the start page stays closed — you should continue where you left off instead of dismissing a tab first. The start page then opens when there is nothing to restore: when you open an area while the program is running, or at start-up when no documents are stored for that area.
• If you rename or move the designated file inside the application, the designation follows. If the file leaves the area, the designation is dropped. And if it ever points nowhere because the file was deleted from outside, the area still opens normally and merely tells you about it.
• The bundled demo area carries its welcome page as the start page. Create and open it, and you land on that page straight away — seeing the feature in use rather than only described.

1.126.0 Documents without a size limit

September 2, 2026

Very large documents eventually became hard to edit smoothly. This version takes the effect out of document size without imposing a limit on you: when a document grows too large, the application splits it into several files when saving and joins them back into one when opening. In the tab you work as always.

• When a document exceeds about one megabyte on saving, the application spreads it across several files in the same folder. On opening you see one continuous text again: undo runs across the boundaries, search finds the document as a whole, and renaming takes all parts along. Cuts are made only before a heading of the top two levels, so that no table, list or code block is ever torn apart. If no such heading exists, the document stays undivided and you are told why. Every part file is an ordinary Markdown file, readable without the application.
• Before a document is split for the first time, the application says so and leaves you the choice: split it, or leave the file untouched and only read it in this tab. Further parts are added silently later, because the decision has been made. If automatic saving runs in the background, nothing is ever split unasked — the question comes when you save yourself.
• Via “File → More file functions → Rejoin parts…” the parts become a single file again. This only happens on your explicit request, never on its own. If the result is larger than the threshold, the application points out beforehand that the next save would split it again.
• If one of the files was deleted or moved outside the application, or has not been synchronised yet, the document opens read only and names the missing place. Nothing is saved, because writing from the incomplete text would lose the missing part for good. Put the file back and the document is complete and writable again the next time you open it — without you having to reset anything.
• Renaming a split document in the file manager used to make it impossible to open at all. Now the application recognises that the opened file is itself the beginning of the document, and opens it.

1.125.1 Task lines look the way they are meant to again

September 1, 2026

Two display faults in task lists are fixed: the completion date appeared inside the text instead of behind it, and a status character sat next to its box instead of inside it. Both came from the same cause — the hanging indent for wrapped lines, which unintentionally passed its effect on to the elements embedded in a line. The indent itself is fully preserved.

• When you tick a task off, EM4me appends the date as a badge at the end of the line. In the editing view with preview, that badge recently appeared in the middle of a word, and the text underneath was no longer readable. It now sits where it belongs again: behind the text of the task. This applies to every badge on a task line, including due dates, priorities, recurrences and identifiers.
• When a task carries its own status character instead of a tick — the slash for «in progress», for instance — that character belongs inside the coloured box. Recently it stood to the left of it and the box stayed empty, which meant the colour no longer showed the very thing it is there for. The character now sits in its box again, in numbered lists as well as in bulleted ones.
• When a long list line wraps, its continuation is indented to line up — that is unchanged. What is new is that elements embedded in a line no longer inherit that indent. This fixes not only the two reported cases but also prevents the same shift for anything embedded in a line in the future.

1.125.0 Suggestions that reach the list

September 1, 2026

The suggestion lists while writing now sort the way they were meant to: after `[[` the most recently edited files appear at the top, after `#` the tags you use most often. Both were built in but never arrived. Plus two new things: property fields suggest the values already used in the area, and switching to edit mode takes you to the view you choose for it.

• Clicking a property value field shows which values are already used for that field in the area — in alphabetical order, and shorter with every character you type. That saves looking them up and prevents the second spelling of the same value, which is something different in every query. A value of your own remains freely typable at any time. Where a property profile defines a value range, you see both origins side by side and can tell them apart. If the field occurs nowhere else, no list appears at all rather than an empty one. If you would rather not have the suggestions, switch them off under Extensions.
• Clicking the pencil in reading view used to switch to the split view, fixed. Anyone working mostly in live view had to switch on every time. Now you set in the settings which view the switch leads to: split, source or live. Split remains the default, so nothing changes unless you change it.
• After `#`, the tags you use most often in the area appear at the top; the number behind each one states how often. As soon as you type something, match quality leads again. A tag collection grows over time and holds one-offs that were used once and never again — in alphabetical order they stood on equal footing with the ones that carry your work.
• After `[[`, the most recently edited files were meant to appear at the top since two releases ago. The order was built correctly but then re-sorted alphabetically by the suggestion display — the promise came to nothing. This is fixed.
• The suggestion list shows at most 30 entries. While typing, only those 30 were searched: a file that was not among the most recently edited could no longer be reached through the suggestions. The list now searches the whole area while you type.

1.124.0 Date values on the line holding the cursor

September 1, 2026

A date in your text can be edited by clicking it — but until now not on the line the cursor was on, which is precisely when you are already working on that line. This release closes the gap without sacrificing the ability to place the cursor inside the value: there, Ctrl-click opens the picker while a plain click still places the cursor.

• When the cursor sat on a line, the date value there was not clickable; the picker stayed out of reach until you left the line. Now a click with the Ctrl key held opens the picker pre-filled with the existing value, and confirming replaces it in place. A plain click keeps its original job and places the cursor, including in the middle of the number. The two gestures no longer get in each other's way. This applies to date and time values as well as to the values of your own calendar systems.
• On the line holding the cursor the value stays discreet at first: no underline, ordinary text cursor. Only when you press Ctrl does the dotted underline appear and the pointer turn into a hand. That way you can see when a click will open the picker — and the value promises nothing that a plain click would not deliver.

1.123.0 Reliable journal blocks

August 31, 2026

This release fixes a bug that could show wrong dates in journal entries, and adds a check to the journal blocks that makes such a case visible in the future instead of letting it look plausible. If you work with journals, you should update soon.

• With several documents open in tabs, the navigation block of a journal entry could show the data of a different open entry after switching tabs: a wrong date, a wrong calendar week, even the «Today» line on the wrong day — and the display looked perfectly normal. The same silently affected other building blocks of the live view, such as the timeline and relative image paths in tables. The cause is fixed: all these blocks are now firmly bound to the document they appear in.
• The navigation and timeline blocks now verify, before displaying anything, that they actually refer to the entry shown and that this entry still exists. If something is off, a clear error message appears instead of the display. The idea behind it: a wrong date is not recognizable as wrong, an error message is. In the normal case nothing changes — the message only appears when something is actually wrong.

1.122.0 Polish for everyday use

August 30, 2026

Eight small things that got in the way of working with EM4me day to day. None of them is a failure, and none alone would have carried a release; together they are the places where a route took one step too many or a rendering did not show what the text means. If you write a lot, this one is worth the update.

• Clicking «previous» or «next» used to open another tab, and the new entry started from the defaults. Now the previous entry gives way to the new one: the tab keeps its view, its edit mode, its zoom, line wrapping and line numbers, its group and its place in the row. You page through your journal instead of stacking it up. If the neighbouring entry is already open, its tab is activated; if you have unsaved changes, you get the same prompt as when closing. The links to week, month or year still open a tab of their own, because they change level instead of paging.
• When you type «[[», the files you worked on most recently come first. Match quality remains the primary criterion and modification time the second — what you are writing right now is usually what you want to point at. Accepting a suggestion also writes the closing brackets and puts the cursor behind them, instead of leaving that to you.
• Until now colour schemes set only body text and muted text; headings, list markers, links, code and quotations had their own fixed colour and stayed the same in every scheme. A new group, «Editor text colours», makes eleven of them adjustable. Every bundled scheme apart from the two standard ones has been given a palette that matches its character — sepia now reads as sepia throughout instead of carrying blue headings. A check keeps every colour at a readable contrast against its background.
• When a bullet or a numbered line grows too long for the width, its continuation now starts under the text rather than under the list marker. This applies in source view, in split view and in edit mode, for bullets, numbered lists, task lines and indented sub-items. The indent is measured in character widths and therefore follows your font size and zoom.
• A column's name has to stay short, because the aggregate row and computed columns address it — which often makes it too terse as a heading. You can now put the text your readers should see in double quotes behind it: «Qty "Number of items":number». The identifier stays the one that formulas use and appears as a hint when you hover over the heading. The new header line «types: hidden» additionally drops the type line under the headings, for tables meant for readers rather than for yourself.
• The list that appears when you hover over a collapsed group used to allow only switching. Every entry now carries a close cross on the right. The list stays open afterwards and shows the remaining files, so you can close several in a row without expanding the group; unsaved changes bring up the usual prompt.
• Next to the button for the simple table grid there is now a second one for the table block with multi-line cells. It deliberately has no grid to drag out, because neither the number of rows nor of columns is known in advance; one click inserts a skeleton with a header row and a data row and puts the cursor in the first header cell. The same insert is available from the command palette and the context menu, and a single undo takes it back.
• In edit mode the folded blocks sat in conspicuously large gaps: several line heights went unused above and below the frontmatter line and around the journal block. The cause was extra spacing the editor created around every block rendering. The gap now matches the one between two paragraphs and grows with your font size. The same cause affected all block renderings, so tables, code blocks and diagrams benefit too.

1.121.3 The same behaviour on both systems

August 30, 2026

The first Linux release brought the full range of functions — and in doing so revealed four assumptions EM4me had quietly been making about its operating system. On Windows they had no consequences; on Linux they did. This release clears them out. If you use EM4me on Linux, the update is worth it.

• EM4me treated two files whose names differ only in upper and lower case as one and the same. On Windows that holds true, on Linux it does not: there, «Part 1/Departure.md» and «part 1/departure.md» are two different files. The consequences ranged from a chapter that could not be added to a book because EM4me considered it a duplicate, to a book that silently vanished from its shelf. EM4me now settles the question in a single place, and settles it the way the system in use does. It deliberately stays generous about file extensions, wiki links, tags and recognising the companion files of books and shelves — so a book that reaches you from another system is still recognised as a book on Linux.
• The button for the Gantt view would not accept a click: sitting on top of it was the filter toggle, which only becomes visible once you move the pointer across the area — invisible, it was in the way all the same. The two areas overlapped on both systems; that it only showed on Linux was down to the slightly wider font there, which pushed the Gantt button to the right and thus underneath the filter. The filter toggle now sits at the end of the row of buttons instead of above them. It can no longer cover a neighbour, whatever the font, window width or system.
• The short form «[[/Name]]», which addresses a subpage of the current page, counted on Linux as a link leading out of your area and was marked accordingly — in the editor as well as in the reading view. The link itself always worked; only the marking was wrong. EM4me now recognises the short form for what it is: the abbreviation for a subpage, which cannot leave the area at all. Links that genuinely lead out are still marked.
• Two entries in the feature overview referred to the Windows file manager by its product name. On Linux the program is called something else, and anyone looking for it there found nothing — even though the described route was correct. Both texts now speak of the file manager, in all five languages. Where a function really is tied to a particular system, EM4me still says so.
• Above a table view, the filter toggle was set in a different typeface from the table below it, because a fallback chain did not apply to this one button. It now adopts the typeface of its surroundings.

1.121.2 Smooth work in large areas

August 30, 2026

Opening a large collection of many thousands of files as an area could slow the application down: with the backlinks panel visible, every input waited several seconds, in every window. This release fixes the cause. Nothing changes about how the functions behave, only how fast they respond.

• When gathering backlinks, EM4me resolves all wiki links of the area. Links that name a folder path (say, to a file in a particular subfolder) used to be checked one by one against every file of the area. In small collections this went unnoticed; in an area with several thousand files and many such links it added up to seconds per file switch, and the delay hit every input in every window. EM4me now looks these links up in a prepared directory. The result is the same, the way there is shorter by orders of magnitude: switching files, folding, scrolling and changing modes stay instantly fluid even with the backlinks panel visible.

1.121.1 Messages that apply to every system

August 27, 2026

The Linux release brought the full range of functions to both systems, but not every text: in a few places EM4me still spoke as if it ran on Windows only. This release puts that right. Nothing about the program's behaviour changes.

• When a name contains characters EM4me does not accept, the message used to say those characters were «not allowed on Windows». That was misleading, because the check applies equally on every system — deliberately so: it is what keeps a file you create on Linux readable on Windows. The message now says as much and speaks of characters that are not allowed on all systems. It appears when creating a subpage, when creating a file from a template and when renaming.
• The feature overview stated that the light/dark default follows the «Windows system theme». It follows the theme of the operating system, on Linux just as on Windows, and the text now says so. That brings it in line with the manual, which has described it correctly for some time.

1.121.0 EM4me for Linux

August 27, 2026

Until now the program ran on Windows only. With this release EM4me is available for Linux as well, in two forms: as a self-contained application image that starts without installation, and as a package for regular installation on Debian and Ubuntu systems. Nothing changes for the Windows edition.

• You can choose between two ways. The application image is a single program file: make it executable, start it, done — nothing is installed, just like the portable edition on Windows. The package sets EM4me up in the regular way, with everything that belongs to it. Both forms are intended for 64-bit systems and, like the Windows files, carry a checksum with which their integrity can be verified.
• EM4me appears in the application menu with its icon, and your Markdown files are associated with it: a double click in the file manager opens the file in EM4me. If the program is already running, the file arrives in the running application instead of starting a second one. These are the same four file extensions as on Windows.
• On Linux, two folder or file names that differ only in capitalisation are two different places — unlike on Windows. EM4me now decides according to the system it runs on: where capitalisation counts, it keeps two similarly named files properly apart, and the boundaries of an area decide accordingly. Links you wrote on Windows keep working after a move. On Windows itself everything stays as it was.

1.120.0 Reliable even when the display stops responding

August 26, 2026

This release fixes two shortcomings that showed up when a window's display stopped responding. Such a window could no longer be closed, and a failure of the display went unreported. In both situations the application now speaks up and leaves the choice of how to proceed to you.

• When a window's display stops responding, closing no longer waits forever. After twenty seconds without a sign of life a notice appears, offering the choice between «Close anyway» and «Keep waiting»; if the display comes back, the familiar path including the prompt about unsaved content continues unchanged. Your work in other windows and tabs is preserved either way, and the tab arrangement of the closed window is saved for the next session. Previously the only remedy in this situation was to terminate the application through the operating system, which cost you the work in every window. A slow operation does not trigger the notice, because what is measured is not the duration of the operation but the silence of the display.
• When a window's interface disappears, the application no longer stays silent. It reports the failure and offers to reload the window, which brings its tabs back. If the display is only temporarily unresponsive, the application waits half a minute before speaking up, so that a longer computation does not trigger an unnecessary message. Should the same window fail again shortly afterwards, it offers only to close the window, and tells you why.

1.119.0 Technical groundwork release

August 26, 2026

This release is a purely technical one with no change to the feature set. Internally it frees the application from the assumption that Windows is the only operating system, laying the groundwork for a later edition for further operating systems; the behaviour on Windows does not change.

• System-level functions, path comparison and the build chain now ask which operating system they are running on instead of taking it for granted. Nothing changes for your work on Windows; updating to this release is not required. A working edition for further operating systems does not yet come with it, this release prepares the ground for it.

1.118.0 Fields that calculate, and fields that carry a structure

August 25, 2026

This release completes the metadata model. Until now a field held exactly one value, and it held it itself. Two kinds now join that no longer do: fields that calculate their value when you look at them or gather it from other documents — and fields that carry a whole structure, such as the participants of a meeting with name and role. A profile describes both centrally, just like any other field.

• A profile can declare a field that calculates: from the other fields of the same document, with the same language and functions as a query — summing amounts, deriving deadlines from a date, composing texts. A second one gathers the documents pointing to this one, for instance all tasks of this project. Neither value is ever in the file: they come into being when you look, and are therefore always current. Opening a document does not change it — browsing a folder does not rewrite it. In the properties such fields appear as not editable. If one stays empty, a note says why: two fields refer to each other in a circle, or the calculation rule names a field that does not exist here. Nothing is ever blocked. Because the value is not in the file, a query cannot filter on it; the query can, however, do the same calculation itself.
• Until now a meeting with three participants needed three parallel lists — one for the names, one for the roles, one for the companies — whose connection lay solely in their order. Now one field is enough: it holds either an object with named subfields or a list of similar objects, and the profile describes the subfields with type and permitted values like any other field. The properties show them stacked: the subfields indented under their field, each list entry as its own group with buttons to add and remove. A subfield not filled in yet stays visibly empty instead of being prefilled. In the file the whole thing appears as an ordinary, indented structure and thus stays readable without this program. The same applies to the properties of a single paragraph.

1.117.0 Every field of a document in one place

August 24, 2026

The more property profiles can do, the more often the same question comes up at a document: which fields actually apply here, and why? This release answers it in one place. On request the properties area shows every field that applies to this document — including those not filled in yet — along with the profiles they come from. And in the other direction, a single command now writes the list of a profile's documents into your document.

• Below the fields you have filled in, an area can be expanded that shows all the other fields applying to this document. Above them stand the profiles they come from: with symbol, name and what makes the profile apply — an entry in the document, a tag, the folder, or being the area's default. Inherited profiles are indented and marked as inherited. Every single field carries the symbol of the profile its description comes from. If you need the fields of one of those levels, one click adopts them in a single step; expanding the area writes nothing, and values already filled in stay untouched. The form can be reached from the area itself, from the command palette and from an entry in the tab context menu.
• The question of which documents belong to a profile is a query — and the application has been able to run queries all along. What is new is the shortcut: a command writes the finished query at the cursor position. It takes into account every path by which a document reaches that profile: the entry in the document, the bound tags and the bound folders together with their subfolders. For an area's default profile it produces a query over all documents. The result appears in the document like any other query and stays current; the inserted text itself is ordinary content that you can edit afterwards, extend with columns or sort. A document holding such a query is therefore also a saved view that can be named, linked and passed on.

1.116.0 Profiles that find their documents themselves

August 24, 2026

This release makes the property profiles felt in everyday work. A document no longer has to state which profile applies to it — a tag or its folder is enough, and the symbol in the properties section shows which profile is currently in force. Value lists can come from an ordinary note or from a query, and thus maintain themselves. And the set of field types grows by links to other documents and by times of day, with settings per type. Existing profile files remain valid unchanged; without new entries nothing changes.

• Until now, every document had to state which profile applies to it. Now a tag or the folder it sits in is enough: the settings record, per profile, which tags and which folders point to it — a folder takes its subfolders along. The paths add to each other rather than replacing one another, and the order is fixed: first the field in the document, then tag, then folder, and finally the default profile. So that it also stays visible why a document has its fields, the header of the properties section now shows the symbol of the applying profile; a profile receives one via the icon entry in its file.
• The permitted values of a choice field used to live in the profile file and had to be maintained there by hand. Now an ordinary note can carry the list — one value per line — and changes to it take effect immediately, even when they come from outside. That turns the value list into perfectly normal content you can link, comment on and pass along. Alternatively a query delivers the values from your collection, such as all documents in a folder; it is evaluated only once a field needs it. If a source is missing, the field stays usable and simply says so.
• A field can now hold a link to another document instead of carrying its name as text: with completion while typing, a note when the target does not exist, and an arrow that opens it. A link field can also carry several targets, and the suggestions can be limited to a folder. Added to this is the time of day as a type of its own. Number and date have new settings (step size, limits, a suggestion shifted by days), and a choice can be presented as a button that switches to the next value on click.

1.115.0 Profiles that build on each other

August 23, 2026

This release expands the property profiles an area uses to describe its document fields centrally. Profiles can now inherit from each other, so shared fields are stated once and each document kind only adds its own share. A definition can carry more properties than before, and anyone who slips while writing a definition gets the mistake named precisely: which definition, which property, and what is expected instead.

• A profile can take over the fields of another one: it names a parent profile, excludes individual inherited fields where needed, and replaces an inherited field with an own field of the same name. Chains across several levels are possible. This way a base profile describes what applies to all documents, and a document kind such as article or meeting only adds its own fields. The familiar assignment rules remain unchanged.
• A field definition can now carry type-specific options, a source for its value pool and nested subordinate fields. These properties are reserved for the upcoming expansion stages and have no effect yet in this version; a file already using them is valid, though, and stays that way. In addition, a field may now take several values without requiring a fixed value list.
• The profile list in the settings now shows hints about faulty definitions written out directly under the affected profile instead of merely counting them. Each message names the affected definition, the faulty property and what is expected in its place; for subordinate fields also the path to them. A click on the profile name opens the file for fixing, and after saving the hint disappears without a restart. As before, no hint blocks anything.

1.114.1 Technical maintenance release

August 22, 2026

This release is a purely technical maintenance release with no change to the feature set. It unifies the internal identifiers of the project documentation; the behaviour of the application does not change.

• The internal identifiers of the project documentation now follow a unified scheme. Nothing changes for your work with the application; updating to this release is not required.

1.114.0 A tour through the program

August 19, 2026

This release is aimed at everyone opening the application for the first time. A guided tour starts by itself on the first launch and shows in ten stations what sets the program apart from an ordinary editor, doing so in the running program rather than in a description. The bundled example collection grows along with it: it now holds a topic area whose pages nest across four levels, and it brings two ready-made workspaces.

• On the first launch of the application, a tour with ten stations begins. Each station overlays the interface and points at the control currently under discussion: the views, the tabs and their groups, the sidebars, windows and applications, areas, subpages as well as tasks and queries. One station explains the files that appear next to your documents without you having created them. You can close the tour at any time; it then no longer starts by itself, but remains available at any time through Help and Product Tour.
• The bundled example collection now holds an astronomy topic area whose pages nest across four levels, from the galaxy through the star and the planet down to the moon. The hierarchy lives in the file name alone and not in folders, exactly as with your own subpages. Alongside it come pages on light speed, distances and ages that reference one another and the topic area.
• Creating the example collection also yields two named workspaces: one with two windows and two coloured tab groups, and one for getting started. They do not open by themselves but wait under File and Workspaces until you call them up. This way the collection also shows how windows and tab groups can be arranged, which a single folder could never demonstrate.

1.113.0 Queries with self-reference

August 18, 2026

This release lets a query know where it sits. With the this. prefix it reads the properties of its own page, and an empty link target collects everything pointing to that page. So you write a query once and drop it into every note of the same kind. Five small building blocks join in for result columns: the date from the file name, the days up to today, numbers and amounts in local form, a folder filter for link lists and a highlight.

• The this. prefix refers to the page holding the query rather than to the individual hit: this.file.link yields its link, this. followed by a property name its frontmatter value. An empty link target as a source collects every page pointing to it, and in the other direction every page it points to. The page itself never shows up among its own hits. On a person, project or topic page the same query can therefore sit everywhere and still show what belongs there.
• When a file name starts with a date in the form 2026-04-18, the field file.day reads it as a real date. You can sort by it, compare it and calculate with it without writing it into the frontmatter as well. The days function turns a time span into a number of whole days, properly rounded so a clock change does not swallow a day.
• The plus sign now also joins date, duration, number and link values with text where an empty cell used to appear. Several pieces of information thus become one readable column such as 2026-04-18 — 48 days. The bold function highlights a part of it rather than the whole cell; sorting and grouping keep working on the plain text, so the highlight changes nothing about them.
• The functions numberformat and currencyformat present numbers and amounts of money the way your language does it, with thousands separators and the currency symbol in the right place. Without a currency given, currencyformat uses euros. A typo in the currency code does not leave the cell empty but shows the bare number.
• The infolder function keeps only those entries of a link list whose target sits in a given folder or below it. Together with the length function this finds the pages nobody in a folder links to, that is the loose ends of a structure.
• The three formatters of the query now follow the language you set in the program rather than the one of the operating system. This also covers month and weekday names in date formats: in a program set to English they appear in English from now on, even on a German system. Inside calculations in running text and in computed columns of datatables the language of the environment still applies, because no document stands behind them there.

1.112.0 Benefits and ways of working

August 18, 2026

This release brings no new feature, but an answer to the question of what the existing ones are good for. A new page in the manual and a new page on the website tell in ten sections which ways of working the app opens up and what a Markdown file can express beyond the Markdown standard.

• The first half leads in five steps from one document in five views through tabs, groups and sidebar panels to several windows and applications, and from there to the two forms of order: the area that binds an application to a folder, and the workspace that keeps a whole working state under one name. The book closes the sequence, turning many files into a declared reading order.
• The second half gives each of the four large constructs its own section: the Perspective Table with whole blocks in a cell, the data table with value types, aggregates and computed columns, the query that keeps itself current with the file collection, and script blocks for evaluations that cannot be phrased as a condition. The rest of the language follows, with more than fifty individually switchable extensions.
• In the app the page sits in the manual as the first entry under «Reference», on the website under «Benefits» as the first item in the navigation. Both versions exist in all five interface languages and share the same structure; the manual version links at the end of every section to the topic page that covers the subject in detail.

1.111.0 Journal timeline

August 17, 2026

This release brings the calendar into your journal entries. A new block shows the period overview as a week row, a month calendar, a quarter or a whole year, with dots on the days you have already written on. Every day, week and month in it can be clicked and opens the matching entry, creating it if it does not exist yet.

• The block shows either the entry's week as a single row, a month calendar, a quarter of three months or a whole year of twelve months. Which period appears follows the entry the block sits in, not today: inside the weekly note of a past week you see that week's month, not the current one.
• Days with an existing entry carry a dot, today is highlighted. In the year calendar you can see at a glance where the gaps in your series are. The marking keeps up as entries appear or disappear.
• Clicking a day opens the daily entry, clicking the calendar week the weekly one, clicking the month name the monthly one. If the entry does not exist yet, it is created. What counts are the journals of the shelf the entry belongs to; where a level has no journal, the label is display only.
• The PDF export prints the calendar as it appears on screen. Exporting as a standalone Markdown file turns it into one table per month, with a dot on the days that have an entry, so recipients without the application keep the overview.

1.110.0 Date formats with names

August 17, 2026

This release teaches your dates to speak. Templates, journals and queries can now render a date with month and weekday names, such as "Monday, 17 August 2026", plus day and month without a leading zero. And so that plain text may live inside a format string, square brackets keep it literal.

• The format tokens MMMM and MMM produce the month name in long and short form, EEEE and EEE the weekday name. In templates and journal entries the names follow your interface language; journal entries created retroactively keep showing the date of their period, not today's.
• The new tokens d and M write day and month as single digits where that reads better: 05.03. becomes 5.3. Together with the names this yields natural headings like "Thursday, 5 March 2026".
• Square brackets keep text literal: in "EEEE[, the] d MMMM yyyy" the word "the" stays untouched even though d and M are now tokens of their own. Format strings may carry whole phrases without single letters being replaced.

1.109.0 The mind map view

August 16, 2026

This release gives your documents a second way of reading. Next to source, split, rendered and live, there is now the mind map: headings and list items become branches of a tree, and the body text below them becomes a note on the node. You see the structure of a long text at a glance, fold away what does not interest you right now, and jump from any node to its place in the document. You still write in the text; the map is a view of it and changes nothing.

• The mind map is another view of your open document, available from the status bar, the View menu or Ctrl+5. Headings and list items form the tree; paragraphs, tables, code and images become the note of their node and open with a click on the sheet symbol. Subtrees fold away, singly or with everything below them, and the surface can be zoomed and panned. A click on a node text takes you to the matching place in the text. The map follows the document while you write.
• You decide where the root sits: on the left with branches to the right, on the right with branches to the left, at the top or bottom for a tree growing vertically, or in the centre with branches on both sides. A deep tree usually reads better horizontally, a flat and wide one vertically, and the central position makes the best use of a wide screen. The labels stay horizontal in every direction, and the same document always yields the same picture.
• In the settings you decide how your maps look: root position, curved or straight lines, from which level a branch passes its colour on to everything below it, how deep the map starts open, and the width at which a long title wraps. Any single document may deviate from this by noting the values it wants in its YAML header; all other documents keep your default. If a value there is not understood, the default quietly applies and the file stays readable.
• The middle of the status bar carries two different things side by side: the three switches for the display inside the editor, and the switches for the view of the tab. There is now a clear gap between them so they can be told apart.
• On startup the window title briefly showed an internal key instead of the translated suffix. The suffix now appears only once its translation is ready.

1.108.0 Shelves reachable again, errors caught

August 14, 2026

A small release with two improvements to reliability. One fixes a fault you could notice: a closed bookshelf could not be opened again in the same session. The other you will ideally never notice, because it only takes effect when something unexpected goes wrong, and then makes sure your unsaved work is kept instead of lost.

• If you opened a bookshelf, closed its window and then wanted to open the same shelf again, nothing happened: no window and no message. The shelf was only reachable after a restart. Opening now works as expected again; the case occurred when another window was open besides the shelf.
• When an unexpected error occurs, the application now follows a fixed rule instead of leaving it to chance. In the window, unsaved texts are kept and you carry on working. If the error affects the core of the application, your session is saved and the program shuts down in an orderly way so that it comes back cleanly on the next start. In undisturbed operation nothing changes for you.

1.107.0 Tidied up for what comes next

August 13, 2026

A release without any new or changed function. It reorganises the inner structure of the application: a few very large building blocks have become many small ones with clear responsibilities. Nothing changes about how you work, about your files or about your settings. The benefit shows in the releases to come, because what is well ordered can be extended faster and checked more thoroughly.

• This version deliberately brings no new function and changes none of the existing ones. You see and operate the application exactly as before; your files, areas and settings remain untouched.
• The structure of the application had grown over more than a hundred releases, and individual parts had become very large along the way. They are now split into manageable units, each with one clear task, and grouped by subject. That shortens the path from an idea to a finished function and makes faults easier to pin down.
• A rebuild of this size must not rely on assurances. Every single step had to pass the same checks as the state before it, and at the most delicate places a machine additionally counted that nothing was lost or duplicated.

1.106.0 Version 1: what you typed is what counts

August 11, 2026

The first major version. Over more than a hundred releases, a simple viewer has grown into a workplace for text: areas, links, tasks, books and your own extensions. This release completes the promise that shapes daily work the most: every function uses what you have written, without saving first. It also protects your files when several people work on the same storage.

• Embedded documents, query lists, the tag list, the area search and the reminders all use the state currently in the editor. Type a note and search for it right away, and you will find it; delete a paragraph and it is gone from the results. Saving is a matter of storage again, not a condition for the application to do the right thing.
• If a file was changed from outside in the meantime, the application says so when you save instead of silently overwriting the other version. If you choose your version, the overwritten one is backed up first. This is aimed at shared storage.
• When someone else changes a file on a network share, the application now picks it up, just as it always did on the local disk.
• The active tab of a panel group now belongs to the column and window you work in. Previously it switched everywhere at once. The arrangement of the panels remains shared across columns.
• In a task line, every date value now opens the date picker, not just the reminder.
• Leaving the search open while typing could make the cursor jump to the match, with the text ending up there. That no longer happens.
• The search reliably marks its active match inside an open area, hints in the status bar no longer push their neighbours aside, and the entries in the About dialog stay together again.

0.105.0 Tidied menus and settings

August 6, 2026

The File and View menus are newly organised, the settings are arranged in four blocks, and the manual has a new overview plus a new page. In addition there are lists of recently opened books and bookshelves.

• The "Book and bookshelf" submenu now carries two lists of recently opened books and bookshelves, just like the ones for files and areas: most recent first, reopened with one click, cleared on request via "Clear list". Both lists survive a restart.
• Four functions that used to be reachable only through the command palette now have fixed places: calendar value and event block sit in the insert part of the editor context menu, "Select subtree" in its list part, "Move chapter file" in the book submenu. The portable export is now a full command as well, reachable through the palette and assignable to a shortcut of its own.
• The File menu shows the four core entries for creating, opening and saving at the top. Everything else is bundled into submenus: "More file functions", "Area", "Book and bookshelf" and "Workspaces". At the bottom sit the entries about the application itself, among them the settings. All functions remain; only their place is clearer.
• The View menu starts with the view modes and bundles the toggles into three submenus: "Editor display" (outline, line numbers, line wrap, scroll sync, typewriter scroll), "Sidebar" (panels, arrangements, columns) and "Appearance" (focus mode and theme). The editor toggles now also show their assigned shortcuts in the menu.
• The navigation of the settings page is organised by scope and origin: "General" carries the core sections and ends with the two management entries for extensions, "Current area" remains the context-dependent group, "Extensions (internal)" collects the sections of the bundled extensions alphabetically, and "Extensions (external)" appears only when external extensions are installed. That makes it clear at a glance what applies everywhere and where a setting comes from.
• In the portable export, the place of an embedded file used to remain empty. Now it shows a reference to the target file, the way a wiki link would; images were not affected and stay embedded. Opened again in the application, the exported file shows the embed fully resolved as before.
• In the panels submenu of the View menu, the search results panel never showed a check mark, and for a few other panels the check mark could go stale. Both are fixed; the check marks now follow the actual state in all cases.

0.104.0 Bookshelves

August 4, 2026

Books can be grouped into bookshelves, with a view of tiles or rows. And a book is now a working space of its own: it opens in its own window, showing only its chapters.

• A bookshelf is a folder above book folders. It holds a shelf file with a description text, cover image and further details, plus a companion file listing the assigned books in their order. Shelves can be created and opened, through the menu or by opening the shelf file; an open shelf returns on the next start.
• The open shelf appears as a page of its own. The tile view shows the cover images as a grid; a book without an image gets a placeholder tile carrying its title. The row view adds chapter count, author and description. The chosen mode is remembered per shelf.
• Book folders that sit inside the shelf folder but do not yet belong to the shelf appear in a section of their own and are added with one click. An assignment can be released again just as easily, without touching the book folder.
• A book now opens in a window of its own, just like an area: the window title carries the book name, and what is visible is exactly the book folder. A second book opens a second window; a book that is already open is brought to the front. That way the chapters in one window always belong to a single book. Images and attachments of a book therefore belong inside the book folder.
• A shelf opens as its own window too, with the shelf name in the title. The shelf window stays the overview: opening a book or a chapter from it switches to that book's window, and the shelf stays behind.
• The search inside the settings used to miss the names and descriptions of the extensions as well as some group headings. It now searches those texts too and jumps to the place it found.

0.103.0 Books

August 3, 2026

Several Markdown files become a book with a fixed table of contents. The chapters stay ordinary files and remain readable on their own; the book defines the order in which they are read, and a panel guides you through.

• A book is a folder with a book file and a companion file carrying the table of contents. The chapters are ordinary Markdown files in the folder or any subfolder; where a file lies says nothing about its place in the book. Details such as author or ISBN and a cover image belong to the book file. Books work on their own, inside an area or inside a workspace.
• A side panel shows all chapters and subchapters in reading order and highlights where you are. Chapters are dragged by their handle and take their subchapters along, within the same level or into another; the same works with Alt and the arrow keys. New chapters are created right from the panel, and files not yet attached to any chapter are collected below.
• Two commands page to the next and the previous chapter, across file boundaries and in the order of the book. At the beginning and the end, the status bar reports the boundary.
• A chapter file can be moved within the book folder; references from other documents and the table of contents follow automatically, as they do on renaming. If a chapter file is renamed outside the program, the panel marks the entry as missing, suggests a file of the same name and repairs the book on a click.
• The whole book block is an internal extension and can be switched off in the settings. Files remain untouched, and after switching back on everything is as before.
• When panels in the sidebar are dragged so tall that space runs out, the column can now be scrolled vertically. No panel disappears from view any more: each keeps at least its header and stays reachable. Without a lack of space, nothing changes.
• A new setting chooses what the height of a panel block depends on: either each panel keeps its own height as before, or a tab group gets a fixed shared height. With a fixed group height, everything stays in place while paging through a group; the drag handle then sets the height of the whole group. Both variants remember their heights separately.

0.102.0 Extension API and reference example

August 2, 2026

This version is aimed at everyone who wants to extend the program with functions of their own. Extensions can now read along with the displayed document, and a complete example is included that can be copied as a template. If you do not write extensions yourself, you will notice nothing of this version.

• The example extension «Note markers» is included in full in the published source code. It marks passages as markers, collects them in a bar at the side, jumps there on a click or a keyboard shortcut, and brings its own settings section. Everything the interface offers appears in it once, and the parts belong together instead of standing side by side.
• An extension can now access the displayed version of a document and is told when it has changed. Until now, a bar of your own at the side could not be connected meaningfully to the document being worked on.
• The interface grows without taking anything away. A package built against the previous version keeps working unchanged; only those using the new possibilities declare the new version.

0.101.0 Spell checking

August 2, 2026

Misspelled words are marked in the editor, and a right-click offers the correction. Checking uses the checker that already sits on your computer: the program brings no dictionary of its own, and it downloads none.

• Typing errors appear underlined in the editor, in the source view as well as in the live view. The notes field follows the same switch. Without a network connection the check works exactly the same, because nothing is downloaded.
• A right-click on a marked word shows up to five suggestions at the top of the context menu; clicking one inserts it. Below them sits «Add to dictionary» for names and technical terms that should count as correct permanently.
• Whatever you added to the dictionary is listed in the settings and can be removed there one by one. A word added by mistake is therefore not a permanent state.
• Checking starts switched off, because marks in Markdown text can be distracting: syntax, paths and source code are checked along with the rest. It is switched on in the settings, and anyone who does not need it at all can switch off the whole extension.

0.100.0 Attachments

July 29, 2026

A file that belongs to a document reaches its place in one move: paste it or drag it in, and the program takes care of storing and linking it.

• An image from the clipboard is inserted with «Ctrl+V»; a file can be dragged in from the file manager. Either way the file is stored and the reference appears where you are writing. Images show as images, other files as links. Where you drop decides: on the text the file becomes an attachment, on the tab bar it opens as before.
• Four storage locations are available: next to the document, in a fixed subfolder, in a folder named after the document, or, while an area is open, in a central folder for the whole area. The default is the folder named after the document. The choice applies generally and can differ for an individual area.
• If an attachment carries the same name as an existing file, it receives a counter instead of replacing the other one. A screenshot without a name of its own is named after the document and the moment, which makes it recognisable later.
• Clicking the reference opens the attachment in the program your system assigns to it. For images a single click suffices in reading view; in the editor it takes a double click, so that the single click still places the cursor. Only targets inside the area or the document folder are opened, and for files that could launch programs, you are asked first.
• While an area is open, images from anywhere in that area are shown, even when they sit above the folder holding the document. That is what makes a shared attachment folder for the whole area usable. Without an area, behaviour is unchanged.

0.99.0 Area search

July 29, 2026

An open area can be searched as a whole: whatever sits in any of its files is one keystroke away, even when that file is not open.

• With an area open, Ctrl+F in one of its files covers every Markdown file of that area instead of just the open one. Matches appear grouped by file in the «Search results» panel, with a count per file; a click opens the file at the match, and F3 carries on across the file boundary. The scope in effect is shown at the left of the search bar.
• The file the search was opened in leads the list, and with its unsaved state: whatever is in the editor right now is found, even before it is saved. For all other files the saved state on disk applies. The order stays put while you search, so the counter runs through all matches of the area.
• Nothing familiar is lost. Matches in the open file are still highlighted in the text; the list comes in addition, it does not replace the highlighting. Search and replace stays bound to the single file: opening the replace row returns the search to the current document. And a file without an area behaves exactly as before.
• Large areas stay responsive. The area's texts are held while the search bar is open and cached between sessions; that cache sits with the program data rather than in the area itself, so it neither doubles your own files nor travels through folder synchronisation. For an exceptionally large area the files are re-read on every search instead, and the status line says so.

0.98.0 Area statistics

July 28, 2026

An area can now show what it holds: file and storage counts, how much use properties and tags are getting, how many tasks are still open, and which files stand out.

• "View → Area statistics" opens an overview of the open area as its own tab; the same entry point sits in the context menu of the area panel. Six sections answer the questions about the holdings: files and storage used, the properties and the tags together with the number of files using them, the companion files of the documents, the content with tasks, links and aliases, and finally the notable files — the largest, the most recently changed and the most linked ones.
• The property and tag lists can be sorted by name or by count and start with 25 rows, expanding to the full set on request. In the three lists of notable files, clicking the file name opens that file directly. The page itself is read-only; it shows, it does not edit.
• The figures carry the time of their collection at the top and are only recalculated on request, via the "Refresh" button or by opening the page again. That is deliberate: collecting them walks the entire area, and a body of files changes slowly enough that continuous recalculation would be work without insight. Anyone who does not need the overview can switch it off entirely under "Tools" in the settings.

0.97.0 Renaming and detaching subpages

July 28, 2026

Renaming a subpage now only touches its own part of the name. And a subpage can be detached from its parent page, turning it into a standalone page.

• In the line above the document, the parent part of a subpage now sits dimmed in front of the name and can no longer be changed by accident; only the page's own name is edited. Previously the whole name was editable, and a change to the leading part silently moved the page, and everything below it, to a different place in the hierarchy. The rename dialog already behaved this way; now both routes do.
• Changing the whole name of a subpage is available as an explicit option in the rename dialog. It is deliberately off by default, and the dialog states beforehand what a change there does: the page ends up under a different parent page, and all of its subpages move along.
• «File → Detach from parent page…» or the tab context menu turns a subpage into a standalone page. Its own subpages move along in full, and links pointing to it stay valid. A dialog states the new name and the number of pages that move with it beforehand; if the name is already taken, it can be changed on the spot, with nothing renamed in the meantime.

0.96.0 Moving tabs in sets

July 28, 2026

Several tabs can now be selected and moved in a single step. And a collapsed group stays usable even when the file you are working on sits inside it.

• Ctrl and click adds individual tabs to the selection and removes them again, Shift and click selects a whole span. Selected tabs are highlighted. Clicking a single tab changes nothing about the familiar behaviour of the tab bar.
• Bringing five tabs into another group used to mean five drags. One drag or one context-menu entry now covers the whole selection: into a group, over to another one, or out without a group. The tabs keep their order.
• Collapsing used to fail for exactly the group you were working in: the active tab had to stay visible, so the application switched to another file. The file now stays open and its content visible while the group is collapsed, and the group header is marked as active.
• Resting the pointer briefly on the header of a collapsed group brings up its tabs as a list. A click switches to that file without expanding the group. The active file is marked in the list, and unsaved ones carry their dot.
• Closing with the middle mouse button still hits exactly the clicked tab, even when several are selected. Rename, bookmark and moving to another window likewise stay with the single tab. Only the group entries of the context menu and dragging act on the selection.

0.95.0 Searching the manual and the settings

July 27, 2026

The search now also works where you look things up: in the manual it covers every page, in the settings every area. Which scope applies follows from the tab the search is opened in.

• Opening the search inside a manual page now searches every page of the manual, including those that are not open. You no longer need to know which page covers a topic; the two generated pages listing functions and keyboard shortcuts are included.
• In the settings the search previously found nothing at all. It now covers every area of both navigation groups, including areas never opened in this session. Knowing the name of a setting is enough to find its area, without clicking through the navigation.
• Matches appear in the new «Search results» panel, grouped by page or area and with a count per group, so you can see at a glance where a term mainly occurs. A click opens the page or switches the area and highlights the match. The panel can be shown and hidden from the status bar and the view menu like every other panel.
• The familiar key for the next match continues past the end of a page to the first match of the next one, opening it on the way. The counter in the search bar now counts across the whole scope instead of the open page only.
• Inside a document the search behaves exactly as before. The source view of a manual page also keeps searching that single page, because there the point is usually the Markdown notation itself. Replacing stays disabled in the manual and in the settings, since both are for reading only.

0.94.0 Gantt view for events

July 27, 2026

Events can now be viewed as a Gantt chart: appointments with a start and an end become bars on a shared time axis, and anyone who has chained events as predecessors and successors sees those dependencies as lines.

• The toggle above an event block has gained a sixth view. Every event gets a row: those with an end show a bar across the whole duration, all others a diamond at their date, both in the colour of their category. A vertical line marks today, dashed lines connect chained events from the end of one to the start of the next. Next to the name, a star appears once an event has reached a round mark, along with a chain sign carrying the number of its links. The chosen view stays saved in the document.
• The time axis follows what is on display: short periods appear in days, medium ones in weeks, long ones in months. For a finer resolution, narrow the period with the existing filter; the axis then recalculates for the remaining events.
• An event that recurs yearly appears in the chart at its next occurrence and is marked with a circular arrow. That way a birthday from the last century does not stretch the axis across decades and the other bars stay readable.
• A click on a bar or a diamond switches to the table and highlights the matching row, where editing, linking, duplicating and deleting are at hand. Bars cannot be moved with the mouse; dates are still changed in the table.

0.93.0 Shipping defaults and month calendar

July 27, 2026

Freshly set up, the application now starts in English and in amber. On top of that comes a month calendar: the clock in the sidebar can show a whole month and page all the way into distant years.

• The clock in the sidebar has gained a fifth view. It shows a month as a table with weekdays, highlights the current day and adds the calendar weeks if you want them. Single arrows page one month, double ones a whole year, and clicking the month name opens the year entry, which reaches even a distant year directly. A button returns to the current month. The days are display only: the calendar answers the question which weekday a date falls on and leaves journals and appointments untouched.
• A newly set up installation starts with an English interface instead of taking the language from the operating system. That fits the largest group of first-time users, and switching to one of the five included languages sits near the top of the settings. Anyone already using the application keeps their familiar language.
• The shipping state now shows Amber Light and Amber Dark, a warm pair from the included colour schemes. The application falls back to the same pair when a stored scheme can no longer be found. An existing installation keeps its previous appearance.

0.92.0 Time reckonings with a zero point of your own

July 26, 2026

A time reckoning can now rest on an existing one and state only its own zero point. Its values then appear as a span from that point, for instance as a countdown to a date or as a count since an event.

• In the settings you can create a time reckoning that needs no definition of its own: choose a reference time reckoning, set a zero point, done. Everything else, meaning units, names and rules, comes from the reference. The zero point is day 1; the boundaries of the units move with it, so a count starting on the 23rd keeps starting its months on the 23rd, and its weeks start on the weekday of the zero point.
• A value of such a time reckoning appears in the document not as a date but as a span, for example as 1 month, 2 weeks and 4 days. How finely it is broken down is up to you, from plain days up to years, half-years and quarters; parts of length zero are left out. Counting runs in both directions, with a label of your choice for the time before. Hovering additionally shows the corresponding point of the reference time reckoning.
• Besides a self-defined calendar, the built-in standard time reckoning can serve as the reference. Counting down to a date, or recording how long ago something was, therefore no longer requires building a calendar first. Setting the point works through the familiar date selection: you pick a date, and the count is entered.
• If a time reckoning that carries counts is changed, the settings page points this out and asks before applying. It can only be deleted once the time reckonings derived from it have been removed or based on something else.

0.91.0 Bookmarks for the area

July 24, 2026

The bookmark panel is now split in two: alongside the general bookmarks there are bookmarks that belong to the currently opened area, are stored inside it and keep working when the area folder is moved or renamed.

• The bookmark panel now has two sections. Alongside the general bookmarks, which apply everywhere, there are area bookmarks that belong to the currently opened area. They are stored inside the area itself and remember their target relative to the area folder, so they keep working even when that folder is moved or renamed. Only files that lie inside the area can become area bookmarks. Without an opened area the familiar single-section view remains.
• When an area is open and the file lies within it, Ctrl+D asks through a small menu whether the bookmark should be general or area-bound; the menu appears at the top near the menu bar. An area bookmark can also be created directly from the context menu of a file in the area panel and from the context menu of a tab. An existing bookmark can be converted to the other kind at any time through its context menu, including a whole folder with everything beneath it.
• A setting in the Behavior section decides whether the area bookmarks sit above or below the general ones; by default they are on top, and the change takes effect immediately. Reordering by dragging stays within a section. When a file or folder inside the area is renamed, the affected bookmarks follow along automatically.
• If you use the application in several windows, a newly set general bookmark previously appeared only in the window where it was created. Now it shows up immediately in all open windows.
• When opening a window bound to an area, the folder overview of the area panel could briefly appear twice. It is now built in one pass, so the list always stands exactly once.

0.90.0 The manual on the web

July 24, 2026

The application's full manual is now also available as a web version at em4me.ch/manual, in all five languages, with the same rendering as in the application and a full-text search across all pages.

• The complete manual of the application is now reachable on the web as well, at em4me.ch/manual and in all five languages. You no longer need to open the application for a question about how something works. Every page has its own address, and there is a sidebar listing all pages, a table of contents per page and paging to the previous and next page. Access is available from the menu and the footer of the website.
• The web version looks like the manual inside the application, because both are produced through the same rendering. Formulas appear fully typeset, and diagrams are provided as crisp graphics in a light and a dark variant that match the chosen appearance. No extra script runs in the background for this, and nothing is loaded from foreign servers.
• A search covers the entire manual of the respective language. It ignores accents, so that 'Übersicht' and 'Ubersicht' match alike, and it shows the page, the section and a text excerpt for each hit; a click leads straight to the location. The search is only loaded once you use it.
• The manual's two overview pages are on the web as well: the list of all functions and the keyboard-shortcut reference. They show the default keyboard shortcuts and the full range of functions, so you can check what the application offers even before installing it.

0.89.0 Collapsing the sidebar at the edge

July 23, 2026

The left and right sidebar column can now be collapsed as a whole with a click at the inner edge, and expanded again, without losing how the panels were arranged.

• When you briefly need more room to write, you can now fold away a whole sidebar column with one click instead of switching off each panel individually. A small icon sits in the top header at the inner edge of each column, where it meets the text; a click collapses the column. A collapsed column stays as a thin strip at the window edge that reveals the icon on hover and expands again on click. Collapsing is lossless: whichever panels were visible before are exactly back afterwards. The left and right columns switch separately, in split view even each editor column on its own, and the state survives a restart. Besides the edge icon there are two entries under View and two in the command palette, which you can assign your own keyboard shortcut to. The whole feature is an extension you can switch off.
• From this version the project is licensed under the Apache License 2.0 instead of the MIT License; the rights holder is Stumm-Consulting GmbH. As before, the code may be used, modified, distributed and reused commercially. The Apache License additionally grants an explicit patent licence and requires that the licence text, the accompanying notice file and change markers be kept when passing the code on. For everyday use of the application nothing changes.

0.88.0 The clock in three sizes

July 22, 2026

The clock's size setting now scales dial and text together, and the bottom panel of the sidebar finally uses the space it is given.

• Until now the size setting of the clock panel only affected the dial. Setting it to large gave you a large clock and, below it, an unchanged small time. Now time, date line and calendar week follow the same step and keep their proportions, so the panel reads as one image. The small step matches the previous text exactly; anyone on the default step "medium" will therefore see a larger time from this version on.
• The setting used to sit in the "Analogue clock" block and was thus invisible to anyone running the clock without a dial. It now sits in the "Display" block, behind the four switches for dial, digital readout, date and calendar week, and applies to the digital readout as well.
• The large step is meant for a sidebar dragged wide and deliberately does not follow the narrowest column. If a line does not fit the column it is not wrapped onto two lines but clipped left and right; the middle stays readable. To see all of it, drag the column wider or choose a smaller step.
• The drag handle between two panels always sets the height of the panel above it, so the bottom panel of a side has none. It nevertheless got a fixed height whenever any other handle was dragged, and was stuck with it afterwards with no way to change it. It showed a scrollbar even with plenty of space below. It now always follows the height of its content, and a scrollbar appears there only when the space really is not enough.

0.87.0 New tabs beside where they came from

July 22, 2026

A tab arising out of another one no longer opens at the end of the strip, but right beside the one it came from.

• Every click inside the content of a document, be it a wiki link, a result of a query, the source of an event, the journal navigation or a link in a diagram, opens the target immediately to the right of the tab it was clicked from. Where one action opens several files, they follow in their order.
• Openings with no origin, that is from the file dialog, the command palette, the bookmarks, the panels, the manual or the settings, still go to the end of the strip. A file already open is still only activated, without changing the order.
• Inside a tab group, a file opened this way used to join at the end of the group and thus sat far from where it came from. Now it joins beside its origin, and the block of the group stays together.
• The document history appears beside the tab of the document it belongs to, and moves along as soon as it is opened for another document.

0.86.0 Lists as an outline

July 21, 2026

Lists can be edited structurally instead of line by line: move, indent and outdent items together with everything hanging below them.

• Move list items along with their sub-items: Alt and an arrow key move an item with its whole branch. The jump always clears the entire neighbouring branch, and the level stays as it was.
• Indenting and outdenting takes the subtree along, with the cursor in a single line just as with a selection spanning several.
• A new command selects an item with everything hanging below it. Whole branches can be copied or cut that way.
• Numbered lists renumber themselves in the source as soon as you work in them. The starting number of a list is kept, and merely opening a file changes nothing.
• Enter on an empty item at the top level ends the list instead of leaving behind a blank line and one more empty item.
• The Tab key outside lists can be set: it inserts an indent, or it moves the input focus onwards as before.
• A blank line now separates two numbered lists, and the second one starts again at its own number. This deliberately departs from the usual reading, in which the count runs on across the blank line; a document written this way therefore looks different in other Markdown programs. If you would rather not have that, switch the extension off.
• Indenting goes to the content column of the item above instead of using a fixed step.
• Fixed: indenting numbered lists had no effect in the rendered view. Indenting used a flat two characters; below a numbered item that is not enough, so the source looked indented while the rendered view showed the list flat.
• Fixed: outdenting an item tore apart the sub-structure that remained. The siblings left behind were pulled into the item above as continuation text and shown on a single line.
• The new “List structure” extension bundles all of this. Switched off, the application behaves as it did before.

0.85.1 A fix in row editing

July 20, 2026

A follow-up to the previous version.

• Fixed: in the split view, a row edit that had just been opened could disappear together with what had already been typed. Confirming an event row set off a delayed rebuild of the preview which, moments later, took the next edit with it. Event tables and data tables were affected alike.

0.85.0 A new name: EM4me

July 20, 2026

The product is now called EM4me, with an icon of its own and the claim “extended memory for me”. Existing installations keep working in full.

• The product name appears as EM4me throughout: window title, About dialog and menus in all five languages, along with the names of the program files.
• A new icon: a golden tile with a large four, surrounded by the letters E, M, m and e. At small sizes the application icon shows a compact mark, because the letters would dissolve into grey at 16 pixels; from 48 pixels the full mark appears.
• Fixed: parts of the user data were lost when the product was renamed. The folder for user data is tied to the product name, and until now the handover copied the settings only. Drafts of tabs never saved and installed extensions stayed behind. All three are carried over now, and the old data is left untouched where it is.
• The function names around “Perspective” stay as they are, because they are part of existing documents. Product name and function name are two different things from this version on.

0.84.0 Alarms, timers and a stopwatch

July 20, 2026

The clock grows into a complete set of time tools. Plus three points about handling.

• A bar above the clock panel switches between clock, alarms, timers and stopwatch. The choice applies per sidebar column and survives a restart; the clock on the left and a timer on the right are possible at the same time.
• Alarms: as many as you like, with time, label and repeat pattern, each armed separately. The time comes from a digit picker, which makes an invalid entry impossible. An alarm that goes off can be acknowledged or snoozed for an adjustable period; while the window is not in front, a system notification is added.
• Timers: as many counting down as you like, with remaining time and a progress bar. Three quick buttons start one right away, custom durations come from a control for hours, minutes and seconds. The remaining time stays correct across background, sleep and restart.
• Stopwatch: counts upwards, with hundredths, pause and lap times.
• Panel headings can be shown as an icon instead of text, in the section heads as well as in the tabs of grouped panels.
• Changed: the date entry is now triggered with two semicolons instead of two backslashes. The earlier choice collided with the meaning of the backslash as an escape character. The trigger also works inside the cells of Perspective tables.
• Fixed: Enter at the end of a numbered list created a new line with the next number in the pure reading mode and marked the document as changed.

0.83.0 Four points about appearance

July 19, 2026

Small changes to how things look, each of them switchable on its own.

• Document tabs are either square or have rounded top corners, taking effect immediately in every open window.
• The line holding the cursor is given a discreet background in editing mode, in the source view as well as the live view and including the line-number column. In the pure reading view it stays unmarked, because there is no cursor there.
• Four new colour scheme pairs, each in a light and a dark variant: steel blue, forest green, amber and graphite. Like the existing templates they are meant as a starting point to copy for schemes of your own.
• The three editor switches and the four view switches now form one group in the middle of the status bar. On narrow windows it gives way instead of being overlapped by the panel buttons.

0.82.0 Two input helpers

July 19, 2026

Recurring manual steps take care of themselves.

• If text is selected and the clipboard holds a single address, pasting builds a link from the selection and the address instead of replacing the selection. Addresses containing spaces go into angle brackets, addresses starting with www. are given the prefix. Without a selection and inside source-code areas the ordinary paste applies; Ctrl+Shift+V always pastes unchanged.
• The times of creation and last change can look after themselves on saving. Both fields can be switched on independently, their names are free to choose, the format is either the date alone or date and time. An existing time of creation is never overwritten, and without the option to add it a document stays unchanged.

0.81.0 Calculating inside running text

July 18, 2026

Expressions can be written in the middle of the text; what is shown is the result.

• An expression between the markers {= and =} is replaced by its result in the rendered view, in the live view and in the exports; the source keeps the expression, which stays visible as a tooltip on the result.
• It calculates with numbers, brackets and operator precedence, comparisons and logic, character strings as well as date and duration values, plus a catalogue of common functions. No second formula language appears: it is the same one as in the Perspective query.
• An expression that cannot be evaluated shows a discreet error mark with a note, without changing the source.
• In the live view the cursor line uncovers the expression for editing; clicking a result puts the cursor inside it.

0.80.0 Editing tables from the context menu

July 18, 2026

A new submenu offers one consistent set of operations for both kinds of table.

• Twelve operations: column alignment, moving, inserting and deleting rows and columns, and transposing. The submenu appears only with the cursor inside a table.
• Every operation is a single undo step, and the cursor follows its cell. Targets that are not possible appear greyed out.
• All operations are available from the command palette as well and can be given shortcuts of their own.
• Pipe tables are written back neatly aligned after every operation. Borderless tables deliberately gain border bars, and a missing separator row is added.
• In Perspective tables the content of the cells is kept byte for byte. Column operations are available only where no cells are merged; with merged cells the operation declines with a note instead of quietly rebuilding it wrongly.

0.79.0 The file name as a title line

July 18, 2026

The file name sits above the document and can be changed right there.

• The file name without its extension appears in heading style above the first line, without a line number and fixed against scrolling, exactly once in every view. Sub-pages show their full name in slash notation.
• A click on the title makes it editable, Enter confirms and Esc discards. Confirming renames the file with everything that belongs to it: links in other files are adjusted, the companion file moves along, and a page with sub-pages takes its sub-page tree with it.
• Invalid names and name collisions appear as a note right at the title line, without a dialog; the file then stays unchanged.
• The title line can be edited regardless of the editing mode, because renaming is an operation on the file and not on its content.

0.78.0 A formatting bar above the editor

July 17, 2026

A bar of buttons for the frequent editing functions, visible only in editing mode.

• Character formats, headings, lists, quote, links and tables as buttons. In the reading view and in focus mode the bar stays out of sight.
• Pressed buttons show the state at the cursor position; clicking again removes the format. The tooltips give the name and the shortcut currently in effect.
• The table button opens a grid: sweeping across it picks rows by columns with a live label, a click inserts the empty table at the cursor.
• Which buttons appear is freely configurable, with commands, icons, display names and separators of your own, plus a reset to the default.
• On narrow editor columns the trailing entries move into a more menu.

0.77.0 Saving sidebar arrangements

July 17, 2026

The arrangement of the sidebar can be filed away under a name and brought back at any time.

• The current arrangement of both columns is saved as a named variant, including which panels are visible. Applying it replaces the arrangement at once; later rearranging does not change the saved variant, “Overwrite” is the deliberate way back.
• Variants apply either everywhere or only in the area currently open. Area variants live with that area’s data, travel with the folder and appear only while it is open.
• They are managed in the settings, and applied from a submenu in the view menu as well, which also offers the arrangement shipped as the default.
• Two commands for the command palette and shortcuts of your own: save the arrangement, and apply a variant.
• Old variants survive panels arriving or disappearing: applying one reconciles it with what exists now, and no panel is lost.
• Fixed: dragging the height handle did not move a panel exactly with the mouse, and its neighbours changed height along with it. Now only the panel being dragged follows, the others stay where they are.

0.76.0 Your own ways to reach commands

July 17, 2026

Commands can be put where you need them: as a button in the status bar, as an entry in the context menu, or bundled into a macro.

• Your own buttons in the status bar, created in three steps: find the command, pick a symbol from a set of thirty, optionally give it a name of your own. When space runs short the trailing ones move into a more menu.
• Standard elements of the status bar can be hidden one by one; only the notice line always stays visible. Hidden functions remain reachable from the menu, from commands and from shortcuts, and one button restores the standard bar.
• Your own entries in the editor context menu, as a section of their own at the end. Anything not executable in the current situation appears greyed out rather than disappearing.
• Macros: named sequences of commands with a symbol of their own, with optional waits of up to ten seconds in between. A step that fails stops the sequence with a notice naming the macro and the number of the step.
• Every macro is itself a command: findable in the command palette, bindable to a shortcut, and placeable as a button. Starting one automatically on opening is deliberately not offered.
• All of this together forms the “Command placement” extension, which can be switched off. Switched off, the application shows the standard status bar; your setup stays saved and returns when you switch it back on.

0.75.0 Editor view per document

July 17, 2026

Folding, line numbers and line wrapping are remembered by the document itself, instead of being kept by the machine.

• The three switches are stored in the document’s front matter and travel with the file, onto another machine as well. Switching from the status bar or the view menu writes the value into the file and thereby marks it as needing to be saved.
• A general default settles what applies to documents that say nothing themselves. The order is: the document’s own entry before the default before the built-in setting.
• In manual pages, with broken front matter and in documents never yet saved, the switch applies for the session only. On the first save, values differing from the default are carried into the new file.
• Changed: the earlier storage per file path in the application settings is gone. It was capped at five hundred entries and stayed behind whenever a file was copied. Existing entries are deleted at startup rather than converted, because converting them would have changed other people’s files unasked.

0.74.0 One consistent way to every panel

July 17, 2026

All thirteen sidebar panels are reachable in the same way at both places, in the menu and in the status bar.

• A new “Panels” submenu in the view menu holds all thirteen, which makes that menu considerably shorter. Area and calendar appear there for the first time.
• Sub-pages and the file graph now have buttons of their own in the status bar, area and calendar have commands of their own for the palette and for shortcuts. Every panel now has both ways in.
• The order of these entries can be sorted freely and applies to the menu and the status bar at the same time, immediately in every window.
• Fixed: four check marks in the view menu (notes, block properties, file graph, reminders) never showed the actual state of their panel.
• Fixed: the way to the sub-pages was offered even with the linking extension switched off, although the panel was locked.
• Fixed: with the reminders extension switched off, its button stayed visible as the only one, and did nothing.

0.73.0 Four things on the surface

July 16, 2026

Coloured window titles, a new default arrangement of the sidebar, follow-on files joining the tab group, and a sample set of documents that ships with the program.

• Windows belonging to an open workspace carry its colour in the window title bar, strong in the light appearance and muted in the dark one. On systems that do not offer this, the usual title bar stays.
• When a click inside a document opens another file, the new tab joins the same group. Openings from outside the document content, from the file list, the panels, the bookmarks or the palette, stay ungrouped.
• “File → Create demo area” copies a sample collection that ships with the program into an empty folder and opens it as an area: twelve self-explaining pages from the basics through to queries, plus a template and an image and a PDF as attachments. A folder that is not empty is declined, and nothing is ever overwritten. The collection is in English throughout.
• Changed: the default arrangement of the sidebar spreads the panels across both sides in thematic groups instead of stacking them all on the left. It applies to a fresh installation and to resetting to the default; arrangements you saved yourself are left untouched.
• Fixed: the dialog for renaming and colouring a workspace appeared underneath the management dialog and could only be reached after closing that one.

0.72.0 The settings page tidied up

July 16, 2026

Two improvements to handling the settings.

• “Apply” and “OK” are highlighted only while there are unsaved changes; with nothing to save, “Apply” is disabled. The state follows immediately, including changes made in a colour picker or a folder dialog.
• The navigation is divided into two groups: “General” applies to the whole application, “Current area” appears only while an area is open and holds everything tied to it, that is journals, calendar systems, property profiles, document history and templates.
• Fixed: applying immediately after opening the page could silently lose changes to three appearance switches.

0.71.0 Calendar systems of your own

July 16, 2026

An area can keep time-reckonings of its own, for invented worlds as much as for real calendars outside the Gregorian one.

• A calendar is built from levels, day, month and year for instance, with five possible relations between them: a fixed factor, a table of lengths with names, a leap rule, a cycle of its own, and a derived grouping. Add to that epochs with seamless boundaries, which may fall in the middle of a year.
• Several calendars in one block can be converted into one another. The Gregorian calendar ships as a complete template and can be inserted at the press of a button.
• Calendars are maintained in the settings of the area, in two stages from the overview down to the single calendar, with a running preview of a sample value you choose.
• In a document a date is written as @{calendar name: value} and appears as a badge in that calendar’s own notation, in the rendered view, the live view and the exports. Unknown calendars and invalid values are marked visibly and are kept exactly as they are.
• Clicking a value opens a picker built out of the calendar’s own structure, showing the same moment in every parallel calendar of the block. A command of its own inserts a calendar date at the cursor.
• The standard functions around tasks, journals, queries and data tables deliberately stay Gregorian.

0.70.0 Workspaces

July 15, 2026

A whole landscape of windows can be saved under a name and restored later exactly as it was.

• A workspace holds every window with its size and position, every tab with its view settings, the tab groups, the binding to an area and the unsaved drafts. Opening it restores the last state; a workspace already open is brought to the front rather than duplicated.
• An open workspace keeps itself up to date as you work. Workspaces still open when you quit come back at the next start.
• A submenu in the file menu lists all workspaces; a coloured dot shows which of them are open. Along with it a management dialog and four commands for the palette and for shortcuts.
• Every workspace carries a name and one of eight colours. The name appears in the window title, with a bound area alongside it.
• Unsaved documents belong to the workspace: they move into its store on closing without asking, and return with it. If a workspace is deleted, they pass into the general draft store, so nothing is lost.
• The upper part of the file menu is divided into four blocks: files, areas, application, workspaces.
• Fixed: switching an extension exactly while a window was starting up lost that switch in this window.

0.69.0 Events inside the document

July 15, 2026

Appointments, birthdays, anniversaries and project dates live right inside the document, with a table, a calendar and a timeline.

• An event block carries its own data rows. The table shows category badges and the distance from today in years, months, weeks and days, along with milestones such as a full thousand days or a round year, the next recurrence with a countdown, and the length of spans.
• Adding, editing, duplicating and deleting all happen right in the table, with a calendar picker for the date, in the split view, the live view and the reading view alike. Every entry taken over is a single undo step.
• Sorting is a click on a column heading. A filter bar offers text search, categories, periods and traits such as “recurring only”; named filters are stored inside the block.
• Four further views of the same block: an overview with upcoming events and milestones, a month and a week calendar, and a timeline. Clicking an event jumps to its row in the table.
• Instead of carrying rows of its own, a block can collect the events from every file in the area whose front matter says so. Edits are written back into the source file, even one that is not open; clicking the row opens the source.
• Events can be chained as predecessor and successor, with a jump to the target and the opposite direction kept up automatically.
• Event handling is an extension that can be switched off. Switched off, the block stays an ordinary code block and its content is left untouched.

0.68.0 Colour schemes

July 13, 2026

The colours of the application can be set, separately for the light and the dark appearance.

• A colour scheme fills fourteen named colour slots in five groups: surfaces, text, accent and borders, tabs, content. The rendered content follows along by itself, with links carrying the accent, headings the text colour and quotation bars the strong border.
• One scheme is active per appearance; the existing switch between light and dark moves between the two. Changes take effect immediately in every window.
• Schemes of your own start as a copy of one that ships with the program: standard light and dark, high contrast light and dark, and sepia. Those templates themselves stay unchangeable, and every slot has a reset of its own.
• Changed: printing to PDF stays light, but now takes the colours of the active light scheme instead of a fixed palette. Dark schemes never reach the PDF.

0.67.0 Numbering headings automatically

July 12, 2026

Headings can be given outline numbers without those numbers appearing in the source.

• The numbers show in the rendered view, the live view, the outline and the PDF export. The source stays ordinary Markdown; nothing is written into the file.
• It is switched at three levels, the more specific one winning: single heading, document, application. The settings also choose whether counting starts at the first or the second heading level.
• Single headings can be excluded or brought back in with a marker at the end of the line. Excluded ones do not count, and a level skipped counts as one.
• The markers themselves appear in no view and no export; exporting to Markdown keeps the headings without numbers burnt into them.
• The numbering is an extension that can be switched off. Switched off, the markers stay ordinary text.

0.66.0 Reminders

July 11, 2026

Tasks can announce themselves at a chosen moment, independently of when they are due.

• A marker of its own at the end of the task line holds the moment, with a date and optionally a time. Without a time it announces itself at a default hour you can set.
• A reminder falling due appears as a dialog with the description and a link to the file. “Done” moves the task on, “Remind me later” pushes the moment by ten minutes, an hour, four hours, a day, a week or to a date of your choosing, and writes it into the source file.
• At startup a catch-up dialog collects everything missed. A notification from the operating system can be switched on as well, appearing while the window is not in front.
• A panel of its own gathers every reminder in the area, grouped into overdue, today, tomorrow and later, with finishing and postponing right at the entry. A click opens the source file at the right line.
• A reminder is set from a command, from the auto-completion, in the task dialog, or by clicking a value already there. All of them open the same date picker.
• The limit is drawn deliberately: announcements happen only while the application is running and the area is open. Whatever falls due meanwhile is caught up by the dialog at the next start.
• Fixed: the menu for postponing opened behind the reminder dialog and could not be clicked. Context menus now appear above dialogs and pickers.

0.65.0 Every field of a profile at once

July 11, 2026

The fields still missing from a property profile can be added in one step instead of one by one.

• The suggestion menu of the add button is grouped by profile; clicking the profile name adds every field of that profile that is still missing, all at once.
• Each field takes its default value, or else an empty value suited to its type. Values already there and the order of the fields are left untouched, and nothing is duplicated.
• The whole addition is a single undo step. It works in the properties editor just as in the block properties panel.

0.64.0 Querying tasks and editing them from the results

July 11, 2026

Tasks from every file in an area can be queried, and the list of results is a working surface in itself.

• A query returns either files or individual task lines. Filtering and sorting reach every trait of a task: the six dates, priority, kind of status, description, the heading it sits under, tags, recurrence and dependencies.
• Dates understand relative words such as tomorrow and yesterday, and the start and end of week, month and year.
• Results can be grouped on several levels, individual display elements hidden or shown, and the whole switched to a short form showing only the symbols. A counter gives the number of results.
• Every task in the list can be worked on: the status box moves on, a menu pushes the date to tomorrow, a week later or a day you choose, and a button opens the edit dialog. Writing goes line by line into the source file, even one that is not open at all, and is guarded against changes made in the meantime.
• An urgency value weighs the due date, how overdue it is, the priority and the start date, and sorts task lists sensibly without any manual work. It can be shown as a figure and filtered on.
• An edit dialog brings every field of a task together in one place. It edits an existing line, and on an empty line it creates a new task.
• On task lines the auto-completion suggests dates, priorities, recurrences and status changes; nobody has to know the symbols by heart.
• Tasks can depend on one another: a task with a predecessor still open counts as blocked and is marked as such. Identifiers are handed out automatically on request and checked for uniqueness.
• A general preliminary query in the settings applies to every task query, so recurring restrictions are written only once.

0.63.0 Inserting a date and a time

July 10, 2026

A picker anchored at the cursor inserts a date and a time instead of you typing them.

• The picker shows a month calendar with week numbers and a today button, and beside it a time entry made of four digits you set individually. An invalid time cannot be entered at all.
• Date and time can be switched on separately. Three commands cover both together, the date alone and the time alone, each with a shortcut you can rebind.
• Fully usable from the keyboard: arrows move by days and weeks, page up and page down by months, Enter accepts, Esc cancels.
• Dates and times already written are underlined discreetly in the editor and can be changed with a click; accepting replaces exactly that value in a single undo step. Values typed by hand in the same format can be clicked too.
• In code, formulas and front matter nothing happens, and neither does it in the pure reading views.
• Two backslashes in the editor open the picker straight away as well.
• The whole of it is an extension that can be switched off.

0.62.0 Dates and priorities on tasks

July 10, 2026

Task lines carry symbols at the end of the line for dates, priority and recurrence.

• Six kinds of date: due, scheduled and start entered by hand, plus created, done and cancelled written automatically. Each with a date and optionally a time.
• Six levels of priority and a rule for recurrence. In the rendered view, the live view and the exports the symbols appear as badges; a date overdue turns red, an invalid value is struck through.
• Existing files work without conversion. The text is kept character for character on reading and writing, including markers unknown to the program and unusual orderings.
• Every task status now has a kind (open, in progress, waiting, done, cancelled, not a task) and a successor. Clicking the status box follows that chain instead of jumping straight to done. Without a chain of your own, things behave as they did.
• Finishing a recurring task creates the next instance. The rule covers daily, weekly, monthly and yearly patterns, lists of weekdays, the last day of the month, and counting from the moment of completion instead of from the date set. The intervals between several dates are preserved.
• Three automatic entries write the created, done and cancelled dates by themselves, each one switchable on its own.
• A filter text decides which checkbox lines count as tasks at all. Empty means all of them.
• All of this together forms the “Tasks” extension, which can be switched off. Switched off, the markers stay plain text and nothing is written automatically.

0.61.0 A notice about a comment left open

July 10, 2026

A comment without a closing marker swallows the rest of the document. The editor now points that out.

• The opening marker of a comment that is never closed before the end of the document is given a discreet wavy underline. The notice explains that the text behind it appears in no view and no export, and names both ways out: close the comment, or escape the marker.
• The rule applies only while the comment extension is switched on.

0.60.0 Private comments and the command palette

July 10, 2026

Two conveniences: text only the author sees, and a window that puts every command within reach of the keyboard.

• Text between two pairs of percent signs is a private comment. It stays in the source but appears in no view and no export, not in the PDF either.
• Comments work within a line and across several lines. Inside code the pair stays ordinary text, an escaped marker writes it literally, and a comment never closed reaches to the end of the document.
• The editor tints comments discreetly. In the live view they are hidden on every line except the one holding the cursor.
• The command palette opens with Ctrl+K, a filterable window over every command. Typing narrows it down, arrow keys choose, Enter runs, Esc closes.
• The palette shows the shortcuts currently bound, including ones you changed yourself. Commands not executable at that moment appear dimmed, commands of extensions switched off do not appear at all.
• The comments are an extension that can be switched off; the palette belongs to the core.

0.59.0 Four smaller corrections

July 10, 2026

Adjustable panel heights, spaces in file names, the name of a menu entry, and a fault in undo.

• Between two stacked panels of the sidebar sits a drag handle: the height of the upper one can be set with the mouse and is kept. A double click on the handle restores the automatic height.
• Markdown and image links now reach files with spaces in their names through the angle bracket notation as well, not only through percent encoding. The backlink index, the outgoing links panel, the linter and the adjustment on renaming all take in such targets now. Wiki links always could.
• Changed: the menu entry “Recent” is now called “Recent files”, in all five languages.
• Changed: in the default arrangement the bookmarks panel comes before the table of contents. Arrangements you adjusted yourself are left alone.
• Fixed: clicking a link written in angle brackets went nowhere in the live view.
• Fixed: an undo straight after clicking a checkbox or status box emptied the whole document instead of taking back that one click. The same applied to creating and renaming anchors and to search and replace.
• Fixed: a panel saved as visible stayed hidden after startup until its switch had been pressed once.

0.58.0 Tab groups

July 10, 2026

Tabs can be gathered into named, coloured groups.

• The members of a group sit together behind a coloured group head, and their tabs carry an underline in the group’s colour. A click on the head folds the group away and open again; folded away, only the head remains, with the number of its members.
• They are managed from the context menus of a tab and of the group head: new group, add to a group, remove from it, rename and recolour, dissolve, close the whole group.
• Dragging knows about groups too: dropping inside or onto the head joins, dragging out leaves, and dragging the head moves the whole group. Another group is never torn apart in the process.
• Eight colours are available, tuned to the light and the dark appearance.
• Name, colour, members and folded state survive quitting the application.
• The groups are an extension that can be switched off. Switched off, the tab strip shows flat, but the groups stay saved and return unchanged when it is switched on again.

0.57.0 The web of links as a graph

July 10, 2026

The links between documents become visible as a graph you can move around.

• Every file is a node, every link an edge with an arrow from the linking to the linked document. Where two documents point at each other, the edge carries two arrowheads.
• Two forms: the area graph as a tab of its own across every file in the area, and the file graph as a panel for the surroundings of the current file, with a depth from one to five.
• The mouse wheel zooms, the surface can be moved, and single nodes can be dragged into place. Pointing at a node lifts it and its neighbours out and holds the rest back; a click opens the file.
• A direction filter shows only what can be reached from the current file, incoming or outgoing.
• The arrangement is computed rather than random: the same graph looks the same every time, and on refreshing, nodes already there keep their place.
• With very large holdings the graph shows the most connected files and says so.
• Fixed: where two system pages shared a column, the graph and the settings for instance, switching tabs kept showing the other one.

0.56.0 Property profiles

July 9, 2026

Properties can be defined centrally, with a type, a fixed set of values and a default.

• A profile is an ordinary Markdown file in the area’s profile folder. Its front matter sets, for each field, the name, the type, optionally a fixed list of values to choose one or several from, and a default value.
• Documents assign themselves to one or more profiles through a field in their front matter; a default profile applies to every file in the area. With several assignments the one named first wins, and an assigned profile comes before the default profile.
• The properties editor and the block properties panel suggest the defined fields, offer sets of values as a list to choose from, and take the type from the definition.
• Where a value departs from the definition, a notice appears. Nothing is blocked and nothing is changed, and a faulty field in a definition only suspends itself.
• A settings section of its own holds the profile folder, the assigning field and the default profile, along with the list of profiles found, the number of their definitions and any notices. Changes take effect at once.
• Without such a configuration everything behaves as it did.
• Changed: in multiple-choice fields a value from the suggestion list is taken over straight away, and the same value can no longer be entered twice.

0.55.0 Journals

July 9, 2026

Periodic documents, that is daily, weekly, monthly, quarterly and yearly entries, with a calendar panel and a navigation block.

• A journal is a series of documents of one period, with a folder and naming scheme built from date parts, optionally a template, and date properties written automatically. Shelves gather several journals together.
• Two commands open today’s entry or the entry for a date you choose. If the file is missing, it is created along with its chain of folders and a filled-in template.
• A calendar panel shows the month with week numbers, marks the days that have an entry, and opens the daily or the weekly entry with a click.
• A navigation block inside an entry shows the current period, the periods above it on the same shelf, and arrows to the previous and the next period.
• Weeks are counted by the international rule with Monday as the first day. The parts for week number, week-numbering year and quarter are available to the templates and the query language as well.
• Journals are maintained in the settings of the area, in two stages across the shelves and the single journals, with a preview of the resolved example path. Changing a scheme raises a warning; files already there are not renamed.

0.54.0 Templates

July 9, 2026

Templates are ordinary Markdown files; applying one fills in its placeholders.

• The template folder can be set per area and, on top of that, for the whole application, the area’s entry taking precedence. Subfolders are carried along.
• There are placeholders for date and time with an offset and a format, for the title and folder of the target file, for input and choice questions, for the clipboard, and for where the cursor should land afterwards. The same question is asked only once.
• Two ways lead to the goal: create a new file from a template, or insert a template at the cursor. Inserting is a single undo step.
• Folder rules assign a template to a target folder: every file newly created in the application then gets it automatically. The deepest match wins, and the template folder itself is exempt.
• If one of the questions is cancelled, no half-filled file comes into being.
• A settings section of its own holds folders and rules, for the whole application and per area.

0.53.0 Script blocks

July 9, 2026

A block can hold a small program whose result appears inside the document.

• The block runs JavaScript and embeds the result into the rendered document. A read-only interface opens up the same data as the query does: files, front matter and block properties.
• Running it is fenced in: no access to files, to the network or to the application, and every block runs in a sealed environment of its own.
• A limit of five seconds stops it. A script running forever blocks neither the application nor the other blocks.
• Output goes through given building functions for text, lists, tables and links; raw HTML is ruled out. Links can be clicked like anywhere else, including the jump to a block.
• Switched off by default, with a permanent warning in the settings. Switched off, the block simply shows its source. The reason: scripts come from documents, not from the application.
• Errors appear with their original message and the line concerned, right at the block.

0.52.0 Queries at block level

July 9, 2026

A query now finds single blocks as well, not only whole files.

• An addition to the output type switches the query to blocks; every other part goes on working unchanged.
• A field name reaches the properties of the block first and falls back to the front matter of its file: a block inherits the context it sits in.
• Results appear as a file with an anchor; a click opens the file and jumps to the block.
• Only blocks with an anchor still present count. Properties whose anchor has disappeared from the text are not a result.
• Fixed: clicks on query results in the live view had done nothing since they were introduced.

0.51.0 A data table with fixed column types

July 9, 2026

A block brings a table with typed columns, a calculating row and editing right in the grid.

• Columns have a type (text, number, date, time, true or false) and optionally a display format. The data sits as readable text inside the document, not in a database.
• A calculating row forms the sum, the average, the smallest and the largest value and the count per column, several of them at once if you like.
• Calculated columns carry a formula and work it out per row, in the same expression language as the query. Results are never stored, but they do feed the calculating row, the sorting, the filters and the exports.
• Editing happens right in the grid: a click or Enter opens the cell, an invalid value is declined with a notice, Tab moves on. Rows can be appended and deleted, and every entry taken over writes the block back neatly aligned.
• A click on a column heading sorts, and a filter row that can be shown searches per column. Both are view only: the source stays unchanged character for character.
• From a thousand rows on, only the head and the calculating row appear, with a notice.
• The data table is an extension that can be switched off. Switched off, the block stays an ordinary code block.

0.50.0 Multiple columns and an adjustable text width

July 8, 2026

Two changes to the rendered view.

• A block sets the content it encloses in two to five columns. The text flows evenly across them, and a marker line of its own forces a column break. An invalid number of columns falls back to a neutral box.
• The width used for the content can be set as a percentage between twenty and a hundred, taking effect immediately in every window; the default is eighty percent. Anything below a hundred stays centred.
• Changed: the fixed width limit used until now is thereby gone. The PDF export uses the full printing width regardless.

0.49.0 Properties per block

July 8, 2026

What front matter does for a whole document is now available for single blocks as well.

• A block with an anchor can carry any number of properties with a fixed type, stored in the companion file next to the history and the note.
• A new panel follows the cursor and shows the properties of the block it currently sits in. It is maintained like the properties editor, with text, list, number, true or false, date and multi-line text; saving happens by itself, without marking the document as changed.
• Blocks without an anchor get one at the press of a button. Renaming carries the anchor in the text, the stored properties and the references within the same document along together.
• If an anchor has disappeared from the text, its data is kept and can be reassigned or deleted in the panel.
• Blocks with properties carry a discreet marker in the rendered and the live view; pointing at it lists the values, a click opens the panel. In the exports the marker does not appear.

0.48.0 The filter becomes a query language

July 8, 2026

The plain filter over front matter grows into a full query with sources, fields, functions, sorting and table output. Queries written earlier stay valid.

• Clauses for source, condition, sorting, limit and number of columns, in any order and at most one of each.
• Conditions know comparisons of magnitude, arithmetic with operator precedence, calls to functions, and values for dates and durations.
• Every file brings fields of its own: name, folder, path, extension, link, size, times of creation and change, tags, aliases, and incoming and outgoing links.
• Comparisons suit the type: numbers numerically, dates chronologically, text without regard to capitals. Along with that, a catalogue of common functions for text, numbers, dates and lists.
• Sources can be folders, tags, a particular file or the links leading out of it, combined with and, or, brackets and exclusion.
• Sorting on several levels, ascending or descending; missing values always come last, whichever the direction. A limit cuts in afterwards.
• A table output with columns of your choosing and headings of your own, the file column clickable and switchable off.
• Lists of results can be made to flow across up to eight columns.
• Syntax errors appear as readable text at the block, in the language of the interface.
• The function is now called “Perspective query” for the user.

0.47.0 Documents never saved survive quitting

July 8, 2026

A new document that has never been saved is no longer lost when the application quits.

• On quitting, untitled documents holding content move into a store without any question asked, and come back at the next start as changed tabs, still untitled.
• A draft returns to where it came from, that is to its application and, if there was one, its area.
• Saving properly or discarding deliberately clears the draft from the store; an empty untitled tab leaves nothing behind.
• The function can be switched off. While it is on, quitting no longer asks about untitled documents; changed existing files still ask, and so does closing a single untitled tab.

0.46.0 One note per document

July 8, 2026

Every document can carry a note of its own, kept apart from its content.

• The note lives in the companion file next to the history, not inside the document. The document itself is untouched by it.
• A panel of its own shows the note for the current file; a switch moves between writing and a rendered preview. Which of the two applies on opening can be set.
• Saving happens by itself, shortly after typing and whenever the file, the focus or the window changes. There is no save button, and the tab is not marked as changed.
• Inside the note field the context menu and the shortcuts of the main editor apply, that is bold, italic, timestamp and the other formatting actions.
• Where the same document is edited in several windows, a change made elsewhere is taken over quietly; an unsaved state of your own raises a conflict notice.
• Unlike the history, the note keeps no revisions: the new state replaces the old one.

0.45.0 Living lists of files inside a document

July 7, 2026

A block filters over the front matter of every file in the search space and shows what matches as a list.

• The block takes a logical expression over front matter fields, with equality and inequality, set comparisons, and and, or, not and brackets.
• Capitals do not matter in field names or values; list fields are checked as membership or as an intersection.
• Rendered, an alphabetically sorted, clickable list of every matching file appears. A click opens the file like a wiki link.
• Files added, changed or deleted reach visible lists without anything being done.
• An empty result, a syntax error with its position, and the states of the index appear as a notice at the block.
• The PDF export prints the state of that moment; the Markdown export leaves the block as source.

0.44.0 A context menu in the editor

July 6, 2026

A right click in the editor opens a menu with actions for links, character formats, paragraphs and insertions.

• The clipboard actions carry the right enabled states; in a read-only editor only copy and select all remain.
• Character formats as toggles: bold, italic, struck through, highlighted, code, formula and comment, plus removing the formatting. They apply to the selection, to the word under the cursor, or set an empty pair of markers.
• Wiki link and external link likewise. Inside a link target and inside code the formatting actions deliberately do nothing.
• Paragraph actions as line-by-line toggles: bullet list, numbered list, task list, headings of levels one to six, no heading, and quotation. A check mark shows the state of the line the cursor sits in.
• Insertion patterns for a footnote with a running number, a table, a callout, a rule and a code block, each leaving the cursor in a sensible place.
• Bold and italic carry the usual shortcuts, and every other action can be bound freely.

0.43.0 Links follow along when a file is renamed

July 6, 2026

When a file is renamed, the links from other files adjust themselves.

• This covers wiki links, embeds and relative Markdown links; for a page with sub-pages, the links to every sub-page renamed along with it as well.
• A checkbox in the dialog controls it for each occasion, a preview shows the files concerned beforehand with the number of places found, and a report sums up afterwards what was adjusted and what was not.
• Documents open and unchanged follow along. A document with unsaved changes receives the adjustment in the editor as an undo step of its own.
• With the document history switched on, every adjustment is traceable as a revision and can be taken back.
• Two settings decide whether the adjustment and the preview are ticked from the start.
• Inside an area, backlinks, tags, auto-completion and the linter now cover the whole area instead of only the folder of the current file and two levels below it. The panels also name the folder, so that files of the same name can be told apart.
• The index is built when the area is opened and kept in a cache file in the area folder; on opening it again, unchanged files are taken over instead of read anew. That file is a cache and nothing else, and can be deleted without any risk.

0.42.1 A correction to the build process

July 5, 2026

A follow-up to the previous version, with no effect on the application itself.

• Fixed: a check in the build process kept the program file from being built with its full version number before the release was made. Nothing about the behaviour of the application changes.

0.42.0 A fourth part to the version number

July 5, 2026

Three smaller pieces of work in one release.

• The version number carries a fourth part that makes every released state unique and places it in time. It appears in the About dialog, in the changelog, in the release notes and in the file properties of the program file.
• Fixed: changes made in the plain source view did not show when switching to the rendered view, because that view was not rebuilt.
• Changed: the file holding the settings of an area carries a new extension. Existing areas are converted quietly when they are opened.

0.41.0 Sub-pages, and renaming files

July 3, 2026

Pages can have sub-pages to any depth, as a logical order independent of the folder structure. Along with that, renaming arrives as a basic function.

• The order is carried by the file name with a special separator; in links the ordinary slash is written. Sub-pages of the same name under different pages do not collide.
• Two relative forms: a link to one’s own sub-page, and one to the parent page. Neither needs to know the name of the page it sits in.
• Auto-completion, embeds, the outgoing links panel and the live view treat sub-pages like any other target.
• A command creates a sub-page and asks only for the name; the separator never has to be typed. Where the sub-page already exists, it is opened rather than overwritten.
• Renaming arrives as a basic function, from the menu and from the tab context menu. Open tabs in every window, bookmarks, the list of recent files, the session and the companion file all follow; name collisions are declined beforehand.
• A page with sub-pages takes its whole sub-page tree along when renamed, and the dialog says how many that is. Collisions are checked across every target before the first file is touched.
• Above the document a path bar shows the chain of parents with clickable steps; a new panel lists the direct sub-pages of the current file.
• The linter reports an ambiguous link target where it exists both as a folder path and as a sub-page.

0.40.0 Document history

July 3, 2026

On request the application records the changes to a document in a companion file beside it.

• Saves following one another are gathered into packets of change, each with a timestamp, what triggered it, and a checksum of the state afterwards. At intervals a complete intermediate state is kept.
• Changes made outside the application are recognised on opening and before every save, and added as a packet of their own. The history does not break because of them.
• It is switched at three levels: document before area before application, with levels not set inheriting. Out of the box the history is off.
• A symbol in the status bar shows the state and where it comes from; a click opens the history view or sets the document’s own switch.
• The history view lists every state with its time, its trigger and the extent of the change. Two states can be compared line by line, and an old state can be brought back into the editor. Nothing is ever deleted.
• Switching it off only pauses it. A history already there is kept and continues seamlessly when it is switched on again.
• A damaged companion file is never overwritten; recording then pauses with a notice.
• Changed: companion files cannot be opened as a document and do not appear in the area panel, in searches or in the link index.

0.39.0 Multiple starts, applications and areas

July 3, 2026

The program can be started more than once. Each start is a working context of its own, which can be bound to a folder.

• Every further start creates an independent application with its own windows and its own window numbering. The window title shows in stages only as much as is needed to tell them apart.
• An area binds an application to a folder and its subfolders as its only workspace. The title then names the area instead of the number, and the same area never runs twice.
• The boundaries are hard: the open dialog, the list of recent files, save as, drag and drop and every internal route stay inside the area. Files opened from the file explorer always land in an application without an area.
• Links to targets outside the area are marked in every view with a warning underline; the click does not open and says why. Images embedded from outside still appear.
• A submenu of its own lists the areas opened recently, the latest first, with the full path as a tooltip.
• A new panel shows the area as a folder tree with the file list of the chosen folder. A click opens, a button creates a new file, and changes made outside appear by themselves.
• Session restoring covers the whole structure of applications, windows and panes, including the binding to an area.
• Changed: two menu entries are now named more plainly, “New file” and “Open file”, to tell them apart from “New application” and “Open area”.
• Fixed: quitting immediately after a fresh window was opened could hang.
• Fixed: on a second start, the new start pulled the unpacked files out from under the running instance, so that new windows could no longer load their language files. Only the portable program file was affected.
• Anyone not using the new possibilities notices no difference: one start, one application, no area.

0.38.1 A correction to the tab context menu

July 3, 2026

A follow-up to the previous version.

• Fixed: the submenus for moving and copying a tab into another window opened stubbornly to the right and, for tabs near the right edge, fell outside the window. They now give way to the left where space is short, and are held back at the bottom.
• Clarified: “File → Quit” saves the complete session across every window. Closing all windows one by one instead brings back only the last one closed at the next start. That behaviour stays as it is, deliberately.

0.38.0 Two additions to the PDF export

July 3, 2026

The export follows the view, and front matter can be kept open.

• The export now follows the view you are in: from the source view it prints the raw Markdown with its syntax coloured, including line numbers where the tab has them switched on. Long lines wrap softly, and only the first printed line carries the number.
• A new switch keeps the front matter permanently unfolded, in the rendered view as well as the live view. It thereby appears in the PDF in full. Without the switch, unfolding by pointing and pinning stays as it was.
• The other views print the formatted document unchanged.

0.37.0 PDF export

July 3, 2026

A document can be written out as a PDF, always light and regardless of the appearance you have set.

• “File → Export as PDF” with a default shortcut, along with a save dialog offering a sensible name next to the source file.
• What is printed is the rendered content. The source and live views switch briefly to the rendered view for the printing and return afterwards.
• The PDF is always light, even with a dark appearance. Formulas, code colouring, callouts, containers and tables appear as they do in the preview, and diagrams stay vector graphics.
• Page-break rules hold code blocks, tables, diagrams, formulas, callouts and embeds together where possible; a heading never stands alone at the foot of a page.
• A new settings section holds the page size, the orientation and the margins.

0.36.0 Extensions from outside

July 2, 2026

The application loads extension packages you install yourself.

• Installing means placing a package folder in the extensions directory of your user profile. They are found at startup and through a refresh action; a faulty package is listed with a diagnosis and never loaded.
• A package newly found is switched off. Switching it on demands an explicit confirmation in a warning dialog that says plainly what it means: code from elsewhere with full access to your documents and the application, without any sandbox. Cancel is preselected.
• The confirmation holds per extension and version. After a change of version it is asked again.
• An extension can contribute six things: a Markdown extension, a sidebar panel, a command with a shortcut, a settings section of its own, its own translations, and a storage space of its own. It may read the colours, the appearance and the language.
• Faults stay contained: an extension that fails while loading is rolled back entirely, switched off, and shown with its error text. Faults while running do not take the application down.
• A settings section of its own lists every package with name, version, description, origin and state, along with the actions to switch on, switch off, remove, refresh and open the folder.
• With no packages installed, everything behaves as it did before.

0.35.0 Functions that can be switched off one by one

July 2, 2026

Twenty-seven existing functions can now be switched on and off individually.

• A new settings section lists every extension in three groups (rendering, linking, tools), each with a switch, a name and a short description. It takes effect at once, without a restart and in every window.
• Eighteen concern rendering: callouts, containers, highlighting, footnotes, emoji shortcodes, abbreviations, image sizes and captions, definition lists, line blocks, superscript and subscript, attributes, spoilers, change marks, extended task states, Perspective tables, formulas, diagrams and the colouring of code. Switched off, the syntax appears as ordinary text rather than as an error.
• Nine concern linking and tools: wiki links with their panels, embeds, tags with auto-completion, the linter, bookmarks, focus mode, the word count and the copy button on code blocks. Switching one off takes its panels, buttons, menu entries and shortcuts along cleanly.
• Where one extension rests on another, it is switched off along with it and marked with a notice. Its own switch is kept and takes hold again as soon as the ground beneath it returns.
• All data survives being switched off: bookmarks, state definitions, visibilities, shortcuts of your own and preferences come back when it is switched on again.
• Out of the box everything is on; without a configuration of your own nothing changes.
• Fixed: buttons in the status bar stayed visible although they were meant to be hidden.

0.34.0 A sidebar you can arrange freely

July 2, 2026

Every pane has a sidebar on the left and on the right, and every panel may sit anywhere.

• To the left and to the right of the content sits a sidebar with a drag handle of its own. A side appears only where at least one panel is visible there; both sides have their own widths, and they are kept.
• The side and the order of every panel can be chosen freely. The arrangement applies to the whole application, while visibility stays switchable per pane.
• Several panels in the same place share it as a group with a row of tabs; the tab chosen last is remembered, and showing a grouped panel brings its tab to the front.
• Rearranging happens by dragging in the sidebar itself: sort in above or below, group in the middle, append on free space. Target zones are marked in colour, Esc cancels, and the change takes effect at once in every window.
• Anyone who would rather not drag finds the same possibilities in the new settings section, including a reset to the default arrangement.
• The default arrangement matches what was there before; whoever changes nothing notices no difference.

0.33.0 Front matter in the rendered view

July 2, 2026

The block of front matter is no longer invisible in the rendered view.

• Documents with front matter show a discreet, folded line at the top with the number of fields. Pointing at it unfolds it, a click pins it, and moving away folds it back after a short delay.
• Unfolded, the original appears with its comments, its syntax set off in colour. Where the front matter is faulty, the raw text appears without a field count.
• It can be used from the keyboard too, with focus and Enter or space.
• In the live view the same line takes the place of the source lines while the cursor is outside. When the cursor moves in, the editable source appears again.
• The line is display only; the fields are still edited in the properties panel.
• A switch in the settings can turn the display off; out of the box it is on.
• Fixed: with documents carrying front matter, the scroll synchronisation of the split view was off by its length, and a click on a checkbox in the rendered view hit the wrong line.

0.32.0 Settings as a page of their own

July 2, 2026

The settings dialog gives way to a full page inside the tab system.

• The section navigation on the left, the chosen section on the right, at the full size of the program. The table of shortcuts finally has room enough.
• There is at most one such page per window; opening it again brings the existing one forward. It can be moved into the second pane and into other windows.
• Changing section keeps the draft. An error marks the section concerned in the navigation and blocks apply and OK.
• Nothing is saved until apply or OK; appearance values show a preview before that. New: closing the page without applying acts as a cancel and discards the preview.
• For the settings page, editing, saving, exporting and the view modes are switched off.
• Fixed: with a manual page open, save, save as and edit stayed clickable in the menu although they did nothing.

0.31.0 Hardening and fixes

July 2, 2026

A release for quality, without new functions. A pass over the whole codebase brought three serious findings and some twenty smaller ones to light.

• Fixed: an attribute value of a particular shape could break out of its attribute in the Markdown export and smuggle in code from elsewhere.
• Fixed: embedding other files was not bounded and could read any local file through path entries. There is now a limit to the document’s folder, a list of permitted extensions and a size limit.
• Fixed: an unsaved tab could lose its content when moved into another window if the target file could not be read. It is now kept and marked as missing, and moving onto a tab that is itself unsaved asks first instead of overwriting quietly.
• Fixed: files that could not be read were quietly dropped when the session was restored; they are now kept and marked as missing, with a notice.
• Fixed: errors while reading and writing lead to readable messages instead of a breakdown, a fault in the file watcher can no longer bring the application down, and a faulty link index led to false reports of broken wiki links.

0.30.0 A new product name

June 15, 2026

The product name and its own table function carry a brand of their own instead of the company abbreviation used until now.

• The new name appears in the window title, the About dialog, the start screen, the installer and the manual. Existing settings are taken over from the old profile at the first start.
• The table function of the program is now called Perspective Table, including the language given on its code block.
• Removed: the old language tag of the table and the old marker of the Markdown export are no longer recognised. Documents with the old table syntax and older exports have to be produced again. A deliberate clean break.

0.29.2 Help texts without version references

June 12, 2026

A follow-up to the manual release.

• Changed: statements pointing at particular versions have gone from the help texts. The chapters now describe the functions directly. When something arrived belongs where it belongs, namely in this changelog.

0.29.1 Help texts without references to other programs

June 12, 2026

A follow-up to the manual release.

• Changed: the manual and the function catalogue describe every construct in their own terms, without pointing to other programs for origin or style. Statements about working together are put neutrally, and example links point to a neutral example address.

0.29.0 A manual inside the tab system

June 12, 2026

The help window gives way to a full manual that opens as a tab.

• F1 opens an overview page as a read-only tab. From there links lead to every other page, and each page is a tab of its own.
• Manual pages have everything a document has: all four views, an outline, full-text search, zoom and the appearance. They can be moved into the second pane and read beside your own work.
• Twelve pages in five languages, from the basics of Markdown through block and inline constructs, task lists, images, formulas and diagrams, linking, front matter and tools, to the program’s own table function, plus an emoji reference.
• Chapters on syntax demonstrate themselves: first the source, right below it the rendered result, side by side in the split view.
• Two pages are generated as you go: the table of functions from the function catalogue, and the shortcut page from the list of commands. The latter shows the shortcuts actually bound, including any you changed yourself.
• A change of language switches open manual pages over at once, tab titles included.
• Manual tabs are strictly read-only and appear neither in the session nor in the list of recent files.

0.28.1 A fault when resetting a shortcut

June 12, 2026

A follow-up to the previous version.

• Fixed: where a default shortcut had been given to another command by overwriting, and was then reset on the original command, the same combination ended up in two places. Resetting now runs through the same conflict check as capturing, and applying checks the whole draft once more.

0.28.0 Shortcuts you can bind yourself

June 12, 2026

Every shortcut in the application can be changed in the settings.

• A new settings section lists every command in five groups. Clicking “Change” captures the next combination of keys, and Esc cancels.
• Conflicts are recognised and can be resolved by overwriting, in which case the other command loses its binding. Combinations fixed in place are protected, and combinations without a modifier are barred, since they would hijack ordinary typing.
• Bindings can be removed, reset one at a time, or set back as a whole to how they were shipped.
• Changes take effect on applying, at once in the menu, the editor and every open window, and they survive a restart. Only what differs from the default is stored.
• New is a command that inserts the current timestamp at the cursor, replacing a selection if there is one.
• Changed: three unintended side effects are gone, because key combinations are now matched exactly. The combinations freed up that way can be bound.

0.27.0 Fifteen new Markdown constructs

June 12, 2026

A batch of established notations, each of them working in the rendered view, the live view and the exports alike.

• Emoji shortcodes appear as characters. Emoticons made of punctuation deliberately stay text.
• Definitions of abbreviations give their occurrences in the text a dotted underline with an explanation on pointing.
• An image standing alone becomes a figure with a centred caption taken from the alternative text. A size given after the file name sets width and height, or just one of the two.
• Definition lists made of a term and its explanation, plus line blocks that keep line breaks and leading spaces, for addresses and poems.
• Container blocks: the familiar callout types appear inside them in their usual look, unknown names as a neutral box. Nesting is possible.
• Subscript and superscript, and underlining.
• Identifiers of your own on headings and marks on single pieces of text. For safety only the identifier and the class are allowed.
• Spoilers, which appear covered and become readable only on pointing or on keyboard focus.
• Change marks in five forms: inserted, deleted, replaced, highlighted and commented.
• Six further task states (in progress, cancelled, delegated, question, important, marked) as coloured boxes with an explanation. A new settings section manages them: switching them on and off, changing colours, and creating states of your own with a character, a colour and a name.
• Changed: a hash inside a block of attributes counts as an identifier and no longer as a tag.

0.26.0 A fuller set of automated checks

June 11, 2026

With no change to how the application behaves.

• Every function described in the function catalogue is now covered by automated checks or carries a reasoned exception. Nothing changes for the user; the value lies in future changes no longer breaking existing functions unnoticed.

0.25.0 Gaps between the views closed

June 11, 2026

Functions that worked in one place and were missing in a comparable one now work everywhere.

• Jumps to anchors and lines work in every view. Links from backlinks, bookmarks and the outgoing links panel scroll to the right place in the reading view too, and the outline hits the right occurrence where headings share a name.
• In the live view tags can be clicked, blocks carry copy buttons and translated callout titles, single-line formulas appear rendered, and a change of appearance recolours diagrams at once.
• In the reading view task boxes can be clicked and change the source.
• The link index is now built whenever it is needed rather than only on opening one particular panel. Four functions that depended on it had quietly done nothing before.
• The Markdown export begins with the front matter on line one again, so that other programs read it and the properties are filled when the file is opened again. Older exports are still recognised.
• A change of language now reaches every open window at once.
• Fixed: several places in the interface appeared in German regardless of the language set, among them the title and the file filters of the open dialog.
• Fixed: a series of missing responses, for instance on a file failing to open, on missing embed targets, on unreadable folders and on errors in the file watcher.
• Fixed: several faults of appearance and handling, among them invisible keyboard focus, too little contrast in the dark appearance, and context menus reaching outside the window.

0.24.0 Speed, and a smaller program file

June 11, 2026

A rebuild under the bonnet with clearly visible consequences.

• Switching between tabs is about a third faster with large documents, and the flicker of diagrams while doing so is gone.
• Per keystroke the text of the document is worked through once instead of up to six times. The split preview rebuilds itself less often with large documents, and embedded PDF files no longer reload while you type.
• The link index is built in small helpings. Before that, the application stood still for the whole time it took with large holdings.
• The program file has become considerably smaller, from about 96 to 82 megabytes.
• Fixed: a build run with a forgotten version number could overwrite the program files of the previous version. That is now barred.
• Fixed: uninstalling removed a whole registry key instead of only its own entry.
• Fixed: sortable table headings showed no response on pointing, and long lines in the link excerpts did not show the place found.

0.23.0 Fixes from a full review

June 11, 2026

A release of fixes only. A pass over the whole codebase brought to light, among other things, seven cases of data loss or crashing.

• Fixed: several ways in which unsaved content was lost, all of them around moving tabs between windows and panes. Automatic reloading could also overwrite what had been typed while the file was being read; now a dialog asks.
• Fixed: replacing after typing in between reached for stale positions and damaged text in the wrong place.
• Fixed: with faulty front matter, adding a field replaced the whole block. An entry was lost where the tab was switched while it was being saved.
• Fixed: numerous cases in the core of the application, among them the permanent failure of session saving after a cancelled quit, files lost when starting from a second instance, trouble with certain characters in file names, and a window left permanently empty after a reload.
• Fixed: an image written across several lines made the live view unusable through an endless loop, and a percent sign in the name of an embed broke the whole rendering.
• Fixed: numerous cases in the link index, among them wiki links with special characters, with paths, with anchors and with escaped characters.
• Fixed: hardening of the rendering. Raw HTML in the Markdown export runs through a narrow list of permitted elements, images are embedded only from the folder of the document, and wiki links with executable schemes no longer appear as links.

0.22.0 A foundation of automated checks

June 11, 2026

With no visible change to the application.

• The application gains a safety net of automated checks: quick individual checks for the logic, and nine complete runs through the real program, from starting up through opening, editing and saving to restoring the session.
• A check now runs before every change to the code and refuses it where something is red. For the user that means faults of this kind never reach a release in the first place.

0.21.0 The end of update checking

June 8, 2026

The application no longer checks for new versions itself.

• Removed: the menu entry for checking for updates, the automatic check in the background, and the dialogs that went with it. The reason: the check ran against a place on the net that no longer exists for this program. Code left in place would only have run into error messages and dead links.

0.20.0 The live view

May 24, 2026

The editor now renders Markdown where it stands. Anyone who wants to write in the natural reading image no longer has to switch between source and rendering.

• A fourth view alongside rendered, split and source. In the live view, bold, italic, struck through, highlighted, pieces of code, links and wiki links appear formatted, headings large, lists with bullets or numbers, tasks with a clickable box, quotations indented with a bar, rules, callouts as a box, tables and code blocks as a finished picture, along with formulas, images, embeds and diagrams.
• Cursor-aware: on the line the cursor sits in, the Markdown source stays visible; every other line shows the rendered image. The plain source view is kept unchanged.
• Reached from a button of its own in the status bar, from the view menu and from a shortcut, in keeping with the existing row.
• A new setting decides which view new tabs open in.
• Line wrapping, line numbers and folding now survive closing and reopening a tab as well as a restart.
• Fixed: a diagram with a syntax error left a broken picture in the cache; an error box with the source now appears instead. Clicking into a diagram puts the cursor reliably at the start of the source line.

0.19.0 Five conveniences

May 22, 2026

Bookmarks, a word count, outgoing links and more.

• Every code block gains a copy button at the top right, appearing on pointing and putting the content into the clipboard in full.
• The status bar shows the words, characters and estimated reading time of the current file, or of the selection where there is one. A click opens the details, with paragraphs, sentences and headings by level. Front matter, code and formulas are not counted.
• A new panel shows every outgoing link of the current file in the order of the document, each with its kind, its target including any anchor, the line and an excerpt. A click opens the target.
• In pipe tables the Tab key moves between cells and creates a new row at the end; Enter does the same, and twice on an empty row leaves the table.
• Bookmarks at file level, with nested folders as in a browser. Created by a shortcut, managed from a context menu with new folder, rename, move and remove, and sorted by dragging with clear drop zones. A star in the status bar shows whether the current file is bookmarked.
• Fixed: dragging files from the file explorer into the application had stopped working once the bookmarks brought dragging of their own.

0.18.0 Callouts, highlighting, footnotes and scrolling in step

May 21, 2026

Four additions to the writing and reading environment.

• Callouts: a quotation block with a type on its first line becomes a coloured box with a symbol and a title. Ten types from note through warning to example, each with a title in the language set, optionally collapsible. An unknown type stays an ordinary quotation and is noted by the linter.
• Highlighting: text between double equals signs appears on a yellow background, muted in the dark appearance.
• Footnotes with a reference in the text and the definition at the end of the file, plus a short form that carries the text right where it stands. In the rendered view superscript numbers appear, with a jump there and a way back.
• Embedding a block anchor now embeds the whole construct around it: multi-line list items with their sub-items, code blocks, table rows, multi-line quotations. Before, only the one line came along.
• In the split view both halves move in step: scroll on the left and the same place appears on the right, and the other way round. The step follows the paragraphs rather than a percentage, and it can be switched per tab.
• Fixed: a wiki link with an escaped vertical bar inside a table cell counted as broken.
• Fixed: embedded images, PDF files and other attachments were marked as broken throughout by the linter.
• Fixed: a file with Windows-style line endings counted as changed right after opening, without anyone having touched it.

0.17.1 Things wrongly taken for tags

May 20, 2026

Right after the previous version, several kinds of wrongly recognised tags showed up in daily use.

• Fixed: colour values written with a hash counted as a tag.
• Fixed: plain numbers counted as a tag, issue numbers and line references for instance. A tag now needs at least one letter.
• Fixed: jump targets in Markdown links counted as a tag.
• Fixed: hashes inside pieces of code counted as a tag. The rendered view had already left them out, the index had not.
• Tags in running text stay recognised as before.

0.17.0 Anchors, embeds, tags and auto-completion

May 20, 2026

Four building blocks for linking documents together.

• A wiki link can point at a heading or at a named block of the target file. Block anchors are set at the end of a line and apply to the block around them. The linter checks both kinds and reports broken targets.
• Embeds bring other content into the document: images at a size you choose, other Markdown files as a rendered block, optionally only the part behind an anchor, and PDF files in a viewer with paging and zoom. The depth is limited to two levels, and a missing target shows a placeholder.
• Tags from running text and from the front matter. A click opens a pre-filtered search, and a new panel lists every tag in the search space with its frequency, a filter field and the hits per file.
• Auto-completion while typing: file names and aliases after the opening bracket, then headings and block identifiers of the target file, and tags after the hash. Sorting puts matches at the beginning first, then frequency, then the alphabet.

0.16.0 Front matter, aliases and properties

May 20, 2026

The block of metadata at the top of a file becomes something you can use.

• The block at the top of the file is recognised as front matter and no longer drawn as a rule. In the source it is given a discreet background. Where the block is missing, incomplete or faulty, the application stays calm and does not crash.
• An alias field makes a file linkable under several names, regardless of capitals. Backlinks find the source through an alias too and mark it as such. Where several files carry the same alias, a dialog asks which is meant.
• A new panel edits the fields of the front matter directly, with an input suited to each type: text, list, date, number, true or false, and multi-line text. Nested structures appear as a preview without editing.
• On writing, fields left alone are kept character for character, comments and the order of keys included.
• Fixed: a property was written to disk at once, even where saving automatically was switched off.

0.15.0 Sorting, status colours and column alignment in the program’s own tables

May 19, 2026

Three additions to the table function of the program.

• Cells and rows can carry a status (error, warning, all right, information, neutral) and are then given a coloured background. The status of a cell comes before that of its row. The colours are checked for legibility in the light and the dark appearance.
• An entry in the table head sets the alignment per column. An entry on the single cell comes first.
• Tables can be opened for sorting by clicking: ascending, descending, back to the original. Sorting is numeric where it can be, otherwise alphabetical by the rules of the language, so that accented letters fall into the right place. With merged cells, sorting is switched off.

0.14.0 Nested tables of the program’s own, and the Markdown export

May 19, 2026

Tables inside tables, and an export for other programs.

• A cell can itself hold a table, up to three levels deep. From the fourth level on, the innermost appears as an ordinary code block.
• The new export turns a document into a file in which the program’s own tables stand as ordinary tables. They then appear as tables in other Markdown programs too. The original file is left unchanged.
• The exported file carries a mark at the top by which the application recognises it and shows it as a table as well. Ordinary Markdown files are untouched by this.
• Fixed along the way: a code block inside a cell could tear the table apart where it held characters resembling a table.

0.13.0 Merged cells and alignment in the program’s own tables

May 19, 2026

Entries on the single cell steer the layout.

• Cells can be merged across columns or rows, and their content aligned horizontally and vertically. Only this short list of entries is allowed; anything else is quietly passed over, so that no harmful code reaches the rendering from a document.
• Header cells automatically carry the entry saying whether they stand for a column or a row. Screen readers can thereby match data cells to their headings.

0.12.0 The program’s own tables, with multi-line cells

May 19, 2026

An ordinary Markdown table is built line by line and can hold neither lists nor several paragraphs nor code blocks in one cell. A table form of the program’s own closes that gap.

• It is written as a block with a language of its own. Inside it, particular characters open and close the table, separate rows, and begin cells, header cells and a caption.
• The content of a cell is set as full Markdown: lists, nested ones included, numbered lists, code blocks, marks, links and images.
• In other Markdown programs the block stays visible as readable source rather than looking broken.
• A help page of its own in five languages explains the form and demonstrates it at the same time, since its examples are real tables of this kind.

0.11.0 A choice of appearance, and symbols in the status bar

May 19, 2026

Three conveniences.

• The appearance can be chosen freely: light, dark, or following the system. Reached from the view menu and from a symbol in the status bar that cycles through them. The choice survives a restart and applies at once in every window, diagrams, code colours and the dialogs of the operating system included.
• The eight word buttons of the status bar are replaced by symbols. They carry tooltips and labels for screen readers in all five languages, and the bar becomes considerably narrower.
• The application checks in the background for new versions and, on finding one, offers to open the download page in the browser, to be reminded later, or to skip that version. Nothing is downloaded or installed by itself.
• Fixed: the sections of the sidebar could no longer be shown and hidden independently.

0.10.0 Coloured code, formulas and diagrams

May 19, 2026

Three large pieces for the rendered view.

• Code blocks with a language stated appear in colour, with a curated list of common languages. A language not known falls back quietly to plain rendering.
• Mathematical formulas are typeset, within a line and as a block of their own. Sums of money in running text are left alone. An error in a formula appears in red where it stands, without bringing the rendering down.
• Diagrams from a textual description, flowcharts, sequence and class diagrams or bar charts among them. They are loaded only when a document needs them, a change of appearance recolours them, and an error appears as a quiet box with the source and the message.

0.9.0 Comfort while writing

May 18, 2026

Indenting lists, zoom, a choice of font, focus mode and a linter.

• The Tab key indents list items by one level, and with Shift takes them back out. Bullet lists, numbered lists and task lists are recognised; a selection across several lines is a single undo step.
• Zoom per tab between 50 and 300 percent, by shortcut and by the mouse wheel. It applies to the editor and the rendering, not to the interface, and an indicator in the status bar resets it.
• A settings dialog with separate choices of font and size for the editor and the rendering, with suggestions and a preview. The values apply in every window and survive a restart.
• A focus mode hides the tab strip, the status bar and the sidebar. Along with it a typewriter mode that keeps the cursor line vertically in the middle.
• A linter marks four common shortcomings with a discreet wavy underline: bare addresses without link form, empty link texts, images without an alternative text, and wiki links whose target is not found. Code is left out, and a note on pointing explains the rule.

0.8.0 Folding, a table of contents and backlinks

May 18, 2026

Three pieces for finding your way through long documents.

• A track at the left edge of the source shows the nesting and lets sections fold away: headings as well as multi-line lists, quotations, code blocks and tables. Two shortcuts fold and unfold at the cursor.
• A table of contents in the sidebar shows the headings as a clickable tree. A click puts the cursor on the line and unfolds it where needed; in the rendered view it scrolls to the place. The section currently in view is highlighted.
• A panel for backlinks shows which files point at the current one, grouped by source with the line, any anchor and an excerpt. A click opens the source at the place found. The search space covers the folder of the file and two levels below it, and a watcher keeps it current without any help.
• Fixed: links within a document did not jump in the rendered view, because the headings carried no targets. From this version on they work.

0.7.1 The position and size of the last window

May 18, 2026

A follow-up to the previous version.

• Fixed: closing the last window lost its position and size, and the application afterwards started centred on the main monitor again.
• Fixed: on systems with several screens at different scaling, the restored size appeared distorted.

0.7.0 Moving a tab into another window

May 17, 2026

Until now the only way led into a new window.

• With several windows open, the context menu of a tab offers two submenus for moving and copying, with an entry per window and the file name of the tab active there as a tooltip.
• Moving takes unsaved content along and closes the tab at the source without asking again. Copying leaves it there unchanged.
• Where the file is already open in the target window, the existing tab is activated rather than a second one created.
• As soon as more than one window is open, each carries a number in its title. The count closes up again when one is closed, and it disappears once only one window is left.

0.6.0 Editing, saving and the status bar

May 16, 2026

The plain viewer becomes an editor: with a menu bar, saving, automatic saving, and search and replace.

• A native menu bar per window with file, view and help, with shortcuts shown on the entries.
• A full editor with coloured Markdown syntax, a light and a dark appearance, line numbers and wrapping. The editing mode can be switched per tab.
• Save and save as, unsaved changes shown by a dot in the tab and the window title, along with a dialog on closing and a notice where the file has changed outside.
• Automatic saving as an option: two seconds after the last input, or on leaving the window. Documents never yet saved are left out.
• A list of recently opened files in the file menu, with the full path as a tooltip and a distinction where names are the same.
• Search and replace in editing mode, one at a time or all at once, with back-references in pattern mode. Replacing every match is a single undo step.
• The toolbar at the top gives way to a status bar at the bottom, with the switches on the left and the editing pencil and the choice of language on the right.

0.5.1 A file passed in at a cold start

May 14, 2026

A follow-up to the previous version.

• Fixed: double-clicking a Markdown file with the application closed opened the window but did not show the file.

0.5.0 Several windows

May 14, 2026

A tab can be moved out into a window of its own.

• From the context menu of a tab, a file moves into a new window and thereby onto another screen, either moved or copied.
• Restoring the session now covers every window, each in its place, with its tabs and their view settings.
• A second instance with a file passed in, from the file explorer for example, hands the file to the window used last instead of starting a second program.
• Where the same file is open in several windows, watching for changes from outside stays in place until it is closed in the last of them.

0.4.0 Window position and a help dialog

May 12, 2026

Two additions.

• The application remembers the position, the size and the maximised state of the window and opens at the same place next time, on a second screen as well. Where the saved area is no longer visible, after unplugging a monitor for instance, it falls back to the default position rather than opening out of sight.
• The full-screen state is deliberately not remembered, so that the application never starts in full screen unexpectedly.
• A help dialog lists the functions and the shortcuts, in all five languages.

0.3.0 Searching

May 12, 2026

Searching in the rendering and in the source.

• A search bar at the bottom searches either the source or the rendering, with forward and backward navigation, a choice about capitals, and a pattern mode with a short reference.
• A known limit: in the rendering a match stays within one piece of text. A phrase cut through by a mark is not found there; in the source it is.

0.2.0 A view per tab, line numbers and wrapping

May 10, 2026

Settings move from the pane to the single tab.

• Source, split and rendered are remembered per file opened rather than per pane. Switching between tabs keeps the view each of them had.
• Line wrapping and line numbers in the source can be switched per tab. In the plain rendering the switches are greyed out, because they do nothing there.
• Fixed: the scroll position was overwritten when switching between tabs.
• An About dialog gives the name, the version and the origin of the icon. The installer offers to associate Markdown files with the application; uninstalling removes the association again.
• A two-pane layout: tabs can be moved into a second pane beside the first, each with its own tab strip and its own content.
• Wiki links are supported, optionally with a display text of their own. Where the extension is missing, it is added.

0.1.0 The first working version

May 10, 2026

A viewer for Markdown files, editing not yet included.

• A tab system for several files open at once, along with three views: source, split with a movable divider, and rendered.
• Markdown with tables, strikethrough, addresses recognised as links, and task lists. Images with a relative path are resolved against the document and embedded.
• Files can be opened from a dialog, dragged in several at a time, or handed over from the file explorer. A second instance passes its file to the one already running.
• A list of recently opened files, and on request the restoring of the session at startup.
• Changes from outside are noticed and the rendering follows. Where a file is deleted, its tab is marked as missing.
• Five languages for the interface, and a light or dark appearance tied to the system.
• A deliberate limit of this version: no editing. Raw HTML from a document is not executed.