-
A paper goes by its title everywhere, with its file name a glance away. A paper imported as PMC1234567.pdf or named by its DOI, with a Title from a reference lookup, showed its title in the Pages panel and its file name nearly everywhere else. Now it is the title you read.
Everywhere a page is named. Ask’s list of pages found and its answers; Backlinks, Outgoing, Related, Tags and the other side panels; search and every page picker; the window’s title and the status bar; graph and canvas cards; Go ▸ Recent Pages; a page-type property; exports — Markdown, Word, ePub, a compiled paper, a shared page — and your published site, its contents and its search. Lists that show titles are sorted by them, so a shelf of papers reads in title order instead of by registry number.
The file name stays close: at the end of each row in Ask’s list, beside the title in pickers and menus, and in the preview. In an answer, a citation shows the first few words of the title and the preview shows the rest; clicking it opens the right paper, as before.
Nothing is renamed. Links, a search for the file name and your saved conversations work exactly as they did, and a copy of an answer, or a piece of it dragged into a page, keeps the file names it cited, so it still links when you paste it. A page you named yourself keeps your name, the page’s own header — where you edit its name — shows the name, a locked page shows only its name, and a paper you set to stay out of exports is named only by its file name in other pages’ exports. An assistant connected to MojoPad is given each paper’s title beside its name, and still asks for the page by its name.
-
Point at a page in Ask and see what it is before you open it. Triaging a list of thirty papers found by a search, you can now rest the pointer on any row and a preview opens beside the drawer, never over the list: the paper’s whole title; the file it came from, its journal, year and authors; the sentence where it says the words you searched for, with them marked; the start of its abstract; how many passages you marked in it and the first of them; and your own notes on it.
The same preview opens on an answer’s citations, on the Cited and Read chips under it and on a page linked in the answer’s words, and a citation’s preview says how the answer came by that page. Press Tab to reach a row or a chip and its preview shows; Escape puts it away and does nothing else. A page that is not a paper shows its opening words and when you last edited it, and a locked page shows its name and nothing of what is inside. The preview over a link in your own page is the same one, so a link to a paper shows the paper rather than its file name twice. Settings ▸ Links & Pages ▸ Show a preview bubble when hovering links and page lists now turns off every one of them.
-
“Show the other 15.” The button under Ask’s list of pages found read Show 15 more of 15 — one number twice. When the rest fits in one press it now says Show the other 15; when there are more than that, it says how many it will add and how many are still to come.
-
See where a page lives, right above its title. Arriving at a paper by a link or a search, you no longer have to open the Pages panel and look for the highlighted row to learn where it is filed: the line above every page’s title now starts with its folders —
Research › Sleep › Trials — the one that holds the page a shade darker. A page loose at the top of the tree says Folders, and a page in no folder says Unfiled. A page more than three folders deep shows the first folder, …, and the last two, and pointing at the path shows all of it. In a narrow window the path folds to its , which opens the page’s own folder.Click a folder to see what is in it — and to move the page there. A small card opens under the name. It lists that folder’s own folders, with how many pages each holds and the one holding this page marked, and its pages by the names the Pages panel shows: a paper by its title, a locked page by its name alone. Click a page to open it, ⌘-click for a new tab, right-click for the usual menu; a folder of more than twelve offers the rest as a gallery. Click a folder in the card to go into it, and ‹ or a name above to come back out — from Folders at the top, every folder in the wiki is a few clicks away. Move “…” here moves the page into the folder you are looking at; the path and the Pages panel follow at once, and the message offers Undo. Show in Pages panel and ◎ Focus this folder are under it.
The keyboard does all of it: Tab to a folder name, Return to open the card, the arrow keys to walk it — → into a folder, ← back out — and Escape to put it away and land back on the name. The path is not shown in Focus Mode, with the page title hidden, in a page opened in a small window, or in the Journal, a Longform document and Side by Side, which have heads of their own, and it is never written into your page. In a second window the path is there too, but pages are filed from the window you opened the wiki in, and the card says so every time you press Move.
-
Moving a page to another folder can be undone, from the menu, the palette or a drag. Only right-click ▸ Move to offered Undo; moving a page with File ▸ Move This Page to a Folder…, by dragging its row onto a folder or next to a page in another folder, or with a folder’s Add Page Here… could not be taken back. All of them offer it now, in the same words, and Undo puts the page back in the folder it came from, in the same place in the list. File ▸ Move This Page to a Folder… also marks the folder the page is already in, and the choice that takes a page out of every folder now reads Out of its folder — at the top of Folders. In a second window it says why it cannot move the page instead of opening an empty list, and opening, closing or showing a folder there no longer tells you that folders are kept in the other window.
How much of your wiki search by meaning can see
-
See how much of your wiki a question can find by meaning. When you added two hundred papers and wondered when Ask could find them by what they are about, the only sign was a message that passed in a few seconds. Now the row under the Ask box, after + New, keeps a small ring and a count of the pages that can be indexed. Once every one of them is in, it says All indexed and the ring is full — a locked diary or a scanned letter no longer keeps it from ever finishing. While it catches up it says how many of them are in — 29 of 31 indexed — and while pages are being read, Indexing… 29 of 31, with the ring turning (it holds still when your Mac is set to reduce motion). If nothing in the wiki can be indexed — every page locked, say — it says No page can be indexed.
Point at it and it says why. Point at the count, or press Tab until it is highlighted, and a card says what is true now — Every page that can be indexed is, or 29 of 31 pages that can be indexed are — and then what can’t be indexed, one line per reason with how many pages each covers: locked pages are never indexed; a scanned paper has no text to read; a file could not be read; pictures and recordings have no words. What is still to come has lines of its own: pages waiting their turn — a page counts only once its latest words are in, so the page you just edited shows as catching up for a few seconds and then comes back — and files not read yet. It also says when a very long page is indexed from part of its text, when indexing is waiting for an answer to finish, and when the model stopped answering and will try again after your next edit. Escape puts the card away.
After a big import it counts through the papers. A paper you have just added counts as soon as it arrives, and is indexed once its words have been read out of it and read for meaning, so the count says Indexing… 31 of 231 while the papers are read, instead of All indexed.
In Settings, and everywhere else the index is counted. Press the count to open Settings ▸ AI, where both numbers now sit under Search by meaning for every wiki you have open — how many of the pages that can be indexed are, and how many can’t be and why; changing the model there shows every page being indexed again. With AI switched off, in Settings or for the wiki, the count says Search by meaning is off, and its card names the box to uncheck — for a wiki, pressing the count opens the Info palette, where Use no AI in this wiki is. If the model you chose isn’t running, the count says Search by meaning is paused rather than that nothing is set up. A second window on the wiki shows the same count, and so does a page opened in a small window, in its header — All indexed, or 29/31 indexed while it catches up, or only the ring when the window is narrow — and Help ▸ Save Diagnostic Report… has a line with both numbers — counts only, never a page’s name or words. A second window also reads the index again each time the wiki’s own window saves it, so a question asked there no longer searches the index as it was when that window opened. In a narrow drawer the count is the first thing to make room. The Related, Rediscover and writing panels that said how many pages were indexed now give the same numbers as the count, and so does the message when indexing finishes (Search by meaning is ready — all indexed).
-
A wiki shared between two Macs with different models keeps an index for each, so neither undoes the other. Syncing one wiki between a Mac that uses one embedding model and a Mac that uses another, each Mac found the other’s index when it opened the wiki, read every page again with its own model and saved over it — so the other Mac did the same the next time, and every switch meant waiting for the whole wiki to be read. Now a wiki keeps an index for each model, side by side: the first time a Mac opens it, every page is read with that Mac’s model and the new index is saved beside the other one once every page is in (while it is being built, the count’s card says the pages are being indexed again because the model changed), and from then on each Mac opens the wiki ready.
Changing the model keeps the index you had, so changing back in Settings ▸ AI reads only the pages you edited since. A wiki keeps indexes for up to two models; when a third one indexes it, the one saved least recently is let go, and is simply made again if that model is ever used again — except that changing the model on one Mac lets go of the index that Mac used before, never the one the other Mac is searching with. Opening a wiki made on another Mac, or one whose model you have since removed, used to read every page again every time and never save what it read; now it is read once and kept. If Ollama isn’t running when you open the wiki, its index is left as it is and read again once Ollama is started, instead of every page being read again.
A page you lock leaves every index in the wiki within seconds — the other Mac’s too — and is never added to a new one; if the other Mac saves its index before it has heard of the lock, the page is taken out again as soon as that save arrives, and again whenever the wiki is opened. A page locked on the other Mac while you are working here leaves this Mac’s index as soon as it arrives, and a page unlocked there can be found by meaning here again. Before, a page you locked or deleted while search by meaning was reading it went into the index anyway, with a few of its words kept there, where the page’s lock didn’t cover them; each page is now checked again just before it goes in. With a password on the wiki, every index is sealed with it, and Help ▸ Save Diagnostic Report… says if one is not.
Update MojoPad on both Macs. An older MojoPad on the other Mac keeps its index where it always was and goes on using it, but if it uses the same model as this Mac, it reads the whole wiki again each time this Mac has saved the index in the new way. The browser extension’s suggestions by meaning and an assistant asking which of your wikis knows about something use the index made with an Ollama model when a wiki has one, even if the newer one was made with MojoPad’s own model — and when a wiki has two made with Ollama models and Ollama on this Mac doesn’t have the newer one’s model, the other one. When a wiki has none they can use, an assistant is told it could not search that wiki, and why; the browser extension simply offers no suggestions for it.
-
Changes to a board, a mind map or a storyboard are found by meaning. Editing a sticky on a board, a branch of a mind map or a card in a storyboard changed what a word search found at once, but search by meaning went on answering from the page’s old words until some other edit started indexing again. The same was true of a linked file read back in, of pages changed by a command, and of edits made while AI was switched off. Each is now indexed a few seconds later, like any other edit — or, for edits made while AI was off, as soon as it is back on.
A wiki kept on two Macs
-
If you sync a wiki between two Macs, three ways a change could be lost are fixed — update MojoPad on both. All three were in earlier versions.
A change the other Mac made to how the wiki is arranged was undone without a word. When the other Mac added or renamed a folder, filed a page or pinned one, and changed no page, this Mac never noticed: the bar saying the wiki was changed on another device didn’t come up, and the next time you changed your folders here, this Mac saved its older copy of the arrangement back over the other Mac’s change. Now a change to the arrangement alone brings the bar up, as a change to a page always has. It is the Mac with the wiki open that notices, so a Mac still on an older MojoPad can go on putting its own arrangement back over yours — which is why both need the update.
A change the other Mac made a moment before your last save here was missed. A sync keeps the time a file was saved on the other Mac, so its change can arrive carrying an earlier time than your own last save — and this Mac asked only whether anything was newer than that. The bar never came up, even when all you had done here was open or close a folder, and this Mac’s next save went over the other Mac’s change. Now each file is compared with the one this Mac last saw, whatever time it carries. And a change the other Mac made to a page or to the arrangement is never taken for one of this Mac’s own because of when it arrived: while this Mac was saving something, even saving that same page a moment later, or just as you opened a second window on the wiki, opened a page in a small window or switched a window to it. The bar comes up in every window that had not been told. And a save here that would go over a change the other Mac made so recently that this Mac had not looked yet — to that same page, to your folders, or to a saved conversation — is no longer made: the bar comes up then, and the save waits for your choice like everything else. A conversation saved while the bar is up waits the same way, and Keep mine saves it.
Keep mine didn’t save what was waiting. What you did while the bar was up — words typed into a page, a page you made, a change to your folders — was saved after Keep mine only if you changed it once more, so closing the window could lose it. Now everything that was waiting is saved the moment you answer Keep Mine, even on a page you don’t touch again. And answering Not Now to Keep mine’s own question now leaves the bar up and your changes held, as that question promises; before, it took the bar down anyway.
-
While the bar says the wiki was changed on another device, changes to how it is arranged wait. Moving a page into any folder, making, renaming, removing or reordering a folder, a pin, the folder focus or sort, making or changing a property or a kind, saving a desk or a new saved view, importing, deleting a page or bringing one back: made while that bar was up, each showed on screen and was then thrown away when you chose Reload, because nothing is saved until the bar is answered. Now each is turned down before anything on screen changes. The bar says so on a line of its own — That change waits until you choose Reload or Keep mine — and gives a small nudge, and after Keep mine the same change goes through. An Undo pressed while the bar is up comes back, so it is still there afterwards; a suggested property you accept, or a site title you type, stays on screen the same way; and adding a task to a page that isn’t a project yet waits before the task is written, instead of the task vanishing. Words you type into a page are not turned down: they stay in front of you, Reload discards them, as its tip says, and Keep mine saves them (above).
What could not be taken back waits too. Deleting a page for good or emptying Recently Deleted, locking a page with a password or taking its password off, setting, changing or removing the wiki’s own password, moving a single page to another wiki, and changing a saved view you already have — a filter, a column, the sort, its name — wait the same way; each of them used to change something at once that Reload could not bring back, or that it quietly threw away. If the bar comes up while you are typing a page’s password, or answering whether to take it off, the page is left as it was — and the same goes for choosing where to move a page or a folder, or which column a saved view should use: nothing is moved or changed. If it comes up while you are asked about deleting pages for good, nothing is deleted and what you ticked in Recently Deleted stays ticked; while you are asked about deleting pages from a folder you follow, nothing is deleted and no file goes to the Trash; and while you are asked about the wiki’s password, the password is left as it was. If the other Mac takes the wiki’s password off while the wiki is open here, this Mac no longer saves under the old password — that made the wiki impossible to open, here or anywhere: your changes wait on the bar instead, and Reload opens the wiki as the other Mac left it, with no password. A page the other Mac restored and changed stays in Recently Deleted when you delete it for good or empty it, and the bar comes up, where before it was deleted with no bar at all. And if the bar comes up just as a page you locked is saved, its earlier versions are kept until you choose: Keep mine saves it locked and then removes them, and Reload leaves the page as it was, versions and all — before, they were already gone.
Nothing that arrives is lost. A research answer that arrives, a clip, or something you capture is kept where it came from until you choose — even when the bar comes up only as it is saved — so Reload no longer loses it — and a clip you turn away, or one already in your wiki, is let go of at once, so Reload doesn’t bring it back to ask about again. An AI assistant is told to wait instead of being told its page was added, and it is told before you are asked about its change, not after you say yes. A paper your library brings in, or a project made from your task list, is filed in its folder once you choose Keep mine — it used to stay unfiled for good. Closing a window while changes are waiting, a page opened in a small window included, or quitting now asks first, and switching the window to another wiki waits like the other changes. Cancel on a quit leaves MojoPad as it was, so a wiki you close afterwards is no longer reopened the next time MojoPad starts. A wiki with a password that goes unused while changes are waiting no longer closes itself on them, and isn’t left on screen either: its window is covered by its lock screen and answers no assistant, and your password brings it back with the changes still waiting. The lock screen covers everything the window shows — a presentation, a flashcard review or an open question included — and while it is up the window runs no command but closing it and changing the theme, so no new window or small window opens on the wiki and nothing is shared, printed or exported. The developer tools don’t open over it, and the menu bar stops listing its pages, folders and snippets until your password brings it back; a wiki with a password leaves no page names in the menu bar once its last window closes, either. A window that opens on the wiki while every other window of it is locked gets the lock screen too, and nothing opens from that one either. The wiki stops being shared as soon as no window of it is left in use, including when a small window you were still using closes later. Your password is checked against the one this Mac opened the wiki with, whatever the wiki’s file says now, and if the wiki can’t be locked it stays open as it was and says so. It is covered, not closed — the wiki stays open behind that screen, so the changes waiting can still be saved. Words typed into a locked page are kept when it locks itself again. If the other Mac turned on Use no AI in this wiki, it is on here as soon as the bar comes up, or as soon as it arrives if the bar is already up, and Keep mine keeps it on. If another window of the same wiki saves a page this window is holding, you are asked which to keep, page by page, and Keep mine on the bar leaves those pages to that question. And Keep mine now says what it does, in its tip and in its question: it saves this window’s pages and folders at once, over the other Mac’s changes.
Folders you follow from your Mac
-
Moving a page into a folder you follow from your Mac asks what you mean — by every route. Filing a draft into the Drafts folder you follow so other apps can open it, you may want it there as a file — or only filed beside its neighbors, as a MojoPad page. Before, only dragging a page from the list under the folders made it a file, and every other way — the folder path’s card, File ▸ Move This Page to a Folder…, dragging a row onto the folder or next to a page in it, a folder’s Add Page Here…, right-click ▸ Move to, the Pages palette’s Move to… and File it… in the Journal’s inbox triage — filed it in MojoPad without a word, so the folder showed a page that was not on your Mac. Now all of them ask the same question, for the folder or any folder inside it.
Save It as a File There makes the page a file in that folder on your Mac, where it lives from then on: a page of writing is simplified to Markdown, a page of plain text is saved as plain text, its history keeps the page as it was just before, and a file of that name already there is never written over — yours gets a number, and the message says so. A page name your Mac can’t use for a file is made one it can: .plan is saved as plan.md, since a name starting with a period would be hidden. Just File It Here keeps it a MojoPad page in the folder, writes nothing, and offers Undo. Cancel moves nothing.
Several pages at once are asked about once, with how many can become files; protected pages, boards, maps and papers, and a page that already has a file of its own elsewhere on your Mac, are filed here either way, and a page like that moved on its own is simply filed, with the message saying why. A folder that is only here in MojoPad, not on your Mac, one your Mac won’t let MojoPad write in, and every folder in a wiki with a password — a file on your Mac wouldn’t be protected by it — are only filed into too, and the message says which. While the bar saying the wiki was changed on another device is up, a move into a folder you follow waits like every other change to how the wiki is arranged (above); if the bar comes up while a page is being saved as a file there, the file just made for it is taken back — never a file anyone else put there since — and when it can’t be, the message names the file left in the folder.
Undo never takes back a file. Saving writes to your Mac, so the move’s Undo never takes it back — when some pages were saved and others only filed, it puts back only the filed ones and leaves the files alone, and when every page became a file, the message offers Show in Finder instead. A script or a connected assistant moving a page there cannot be asked, so it files it in MojoPad and its answer says the page did not become a file.
-
Making a page there, bringing files in, and dragging a whole folder in ask too. A folder’s New Page Here… asks before the page is made: saved as a file, it is a new file in that folder on your Mac; just filed, it is a MojoPad page there; Cancel makes nothing.
Bringing files in. Import Files Here…, files dropped on the folder from the Finder, and File ▸ Import… with the folder picked ask once for everything you chose, saying how many can be saved there. A Markdown or text file saved there is an exact copy in a new file — its frontmatter and links just as they were — and its page reads that copy from then on; the file you picked stays where it is, untouched, and a text file’s copy is a Markdown file, as every import reads it, which the question says. A web page is simplified to Markdown. A note with pictures of its own, PDFs and other papers, pictures, books and other files are imported and filed there either way, each with its reason — a book counted once, however many chapters — and never hold up the rest. A file already in that folder, picked again, is named as one you already have instead of being copied beside itself. Cancel imports nothing. A folder of folders brought in, or parts of an export sent there from File ▸ Import…'s panel, are filed in their folders as MojoPad pages, and the message says nothing was written to your Mac.
Dragging a folder in. Drag one of your folders into a folder you follow and you are asked once for every page inside it: Make It a Folder There makes that folder, and each folder inside it, on your Mac inside the one you follow, and saves its pages of writing as files in the same folders they are in here — never where your Mac already has a folder of that name, in which case nothing is written and the message says why. A folder whose own name your Mac can’t use, one that already mirrors a folder on your Mac, and an empty one are moved without the question, and the message says which and why. A script making a page or keeping a file there files it without asking, and its log in the Scripts palette says nothing was written to your Mac.
Clipping
-
A bookmarklet clip that makes no page is no longer fetched again every time the wiki opens. When you clip with the bookmarklet and nothing selected, MojoPad fetches the page itself — and four ways that could end without a page were kept as unfinished: the page was already in your wiki and you chose Open the one I have, you closed Keep this clip as…, you said no to MojoPad fetching from that site, or the site would not hand the page over. For up to two weeks after, every time the wiki opened, MojoPad fetched the page again and asked or warned you again. Each of those is now finished with the moment it happens. A site that refuses is said once, naming the page and its address, with the two ways that do work: select the part you want first and clip that, or clip with the browser extension. Only a page MojoPad could not reach at all — you were offline, the site was having trouble, or a hotel or airport network was showing its sign-in page — is kept and tried again the next time the wiki opens, three tries in all, each saying how many are left; after the third, MojoPad lets it go and says so, with the page’s address.
-
A clip of a page on an older, unsecured address is saved. MojoPad fetches only over a secure connection, and a bookmarklet clip of a page whose address was not a secure one was thrown away as though you had said no — without asking you anything. It is now fetched over a secure connection, which nearly every site offers. The same goes for File ▸ Import URL… with an address typed without its beginning, such as example.com/article, which MojoPad refused outright.
-
A clip from the browser extension that could not be saved is never thrown away for you. It is the only copy of what you clipped — the page may have changed, or gone behind a paywall, since. If it cannot be saved (a full disk, say), MojoPad now says why, keeps it, and asks whether to keep it or discard it; kept, it is tried again the next time the wiki opens, for as long as it takes — it is never cleared after two weeks, as clips nobody came back for are. It still reaches its wiki when you open that wiki by another path, and if the wiki has been moved or renamed, the next wiki you open asks whether to save the clip there, naming the wiki it was for. Before, it warned you at every open without saying what was wrong. A selection you clipped is kept the same way.
Writing, and what Settings says
-
Typing after a link keeps your space, and your words stay out of the link. Type a space after a link at the end of a line and then a word, and the space vanished — Glossary Methods came out GlossaryMethods, with Methods joined to the link. The space now stays, and so does the / menu after it: a / after a link and a space opens the menu, as it does after any space. Two more cases: a / typed after a link you chose from the [[ picker now opens the menu too, since there is a space between them, and the first letter typed right after a web address you pasted into the middle of a line no longer joins the address.
-
Settings ▸ Reading Aloud says where to see which Japanese voice you have. It said MojoPad could not tell. Since 1.93.0 Help ▸ Save Diagnostic Report… has named the best Japanese voice on your Mac and said whether it is the better kind, and Settings and the manual now send you there. Two more things the manual said too broadly are corrected with it: a book’s highlights carry no color, so an assistant reading your marks gets a color only for a paper’s, and a first- or second-level heading on a page’s very first line keeps a larger space below it than every other heading.