MojoPad 1.92.6 Released (Bug Fixes) (User Requests)

  • You can write after a comment again. A %%comment%% at the end of a paragraph is something you cannot type inside, and there was no position after it for a click to land on — so the cursor went to the end of the text before it and everything typed next appeared in front of the comment. Reopen the page and the spot after a comment is yours again. Inline formulas had the same fault and are fixed with it.

  • The folder tree and the page list are two areas. Each scrolls on its own, with a line between them you can drag — so reaching a folder no longer scrolls your pages away, which matters most when you are dragging one into the other. Double-click the line to put it back. A wiki with a handful of folders looks exactly as it did.

  • Unfiled, or every page. The heading at the foot of the tree is a switch. Unfiled still lists the pages in no folder; All pages keeps every page in view however many folders you have gathered them into — which is what you want when that list is the drawer you fish things out of while you write.

  • Focus one folder. Right-click a folder and choose ◎ Focus this folder and the tree shows only that one: a clear desk for what you are working on today. The row above it names the folder and takes you back. Nothing is hidden and nothing is moved — the view narrows, and it says so.

  • A pane’s header moves its page to the editor; it no longer trades one page for another. Open an article beside the one you are writing, click the pane’s title, and the article you were working on stayed open — before, it was replaced, leaving the same page on screen twice and your work in progress nowhere. The page goes to the tab that already shows it, or to a new one, and the pane closes behind it. The reading pane’s ⇄ still swaps the two if that is what you want.

  • A database view can ask a question with brackets. Views could only want all of their conditions — one flat list, joined by and. The row of chips under the title is now the question itself: it starts with All of or Any of, that word is a button, and ( ) adds a bracket with its own word and its own conditions. So papers from 2025 or 2026 that I have not read is one view rather than three. Brackets nest a few deep, and one you have not filled in yet asks nothing, so the table holds still while you build it. Every view you already have reads back exactly as it was.

  • A property filled by AI uses the model you gave it. If you set a property to answer with a particular model, it now does — whatever the Ask panel happens to be set to. It was following the panel instead, so a property pinned to a local model was quietly answered by whichever model you had last chosen for chat, and the only clue was the length of the reply.

  • The status bar says who is answering. A small mark shows whether questions are answered on this Mac, by your own agent, or by a provider you set up — quiet for the first, plain for the other two, and gone entirely when AI is switched off. Click it to change it. It says what will answer by default; an answer a property wrote still carries its own ✦ naming the model that wrote it.

  • A row in an embedded view opens once, not twice. A page whose body is a database view lost its own tab the moment you clicked a row — and the page you clicked opened twice. One click was being answered by two things: the row, and the link the auto-linker had made of the row’s title. The row now defers to the link, and it follows the same Settings ▸ Links & Pages choice as everything else instead of always opening over the top of what you were reading.

  • A page you already have open is not opened again. Following a link or a row to a page that is already in a tab takes you to that tab, rather than making a second one to close later.

  • An embedded view says how many rows it is not showing. A view embedded in a page shows its first twelve rows and offers to open the rest — but the line saying so was never drawn, so a view with forty-three pages showed twelve and left you to wonder. It reads “…and 31 more — open the view”, and pressing it opens the view.

  • Ask your wiki, with your own agent, can search the whole wiki. “How many pages mention this?” and “list every page about that” used to be answered from the few pages the question happened to be matched to — so the count was a count of those, offered with no sign that it was. It searches all of them now, leads with how many it found, and says plainly when it is naming only some of them. The tool only reads: it cannot change a page, add one, or move anything, and a wiki you have not opened in MojoPad is still off limits to it.

  • That search took the place of the agent’s web access. Worth knowing about, because it is a trade rather than an addition. A question about your notes carries the text of your pages with it, and pages arrive from the clipper, from mail, and from wikis other people send — so some of those words were written by somebody else. That was the one path where a stranger’s words sat beside a tool that could reach the internet, and now there is no such tool on it. Ask anything still searches the web, and connected tools you have granted a wiki still work exactly as you allowed.

  • A property filled by AI is answered in the words you asked for. If your property says bullet points, you get bullet points. MojoPad had been adding a page of layout guidance of its own underneath your instruction — eight shapes, most of them phrased as orders — which is right for the Ask panel, where nobody has said what they want, and wrong for a property whose instruction you wrote yourself. It showed most on models running on your Mac, which follow the longest and most specific instruction they are given; a property named for one shape could come back in another. The shape chooser in the Ask panel is unchanged.

  • A MojoPad link pasted into a Markdown page survives saving. A link to another wiki’s page, to a folder, or to a card was turned back into plain words by the next save — the words stayed, the address went, and it went from the file and not only from the screen. Links inside one wiki were never affected, which is why this went unnoticed: those are written as [[brackets]] and came through fine.

  • A page you have sealed with a password keeps its words to itself. That now includes the text inside a PDF, which was readable by an agent reading your wiki from outside even while the page it belongs to was sealed. A wiki with a password on the whole document is left alone entirely.

  • Clips go to the wiki you told them to. If you keep more than one wiki, the browser extension had been attaching a destination of its own to every clip — whichever wiki your last clip went to — including on the clips it takes the moment you press it, where you were never shown a chooser. MojoPad read that as a decision you had made and let it outrank Settings ▸ Web Clipper ▸ “Clip to”, so that setting did nothing at all for anyone with two wikis, whether it named a wiki or was left on “whichever wiki is in front”. Your setting decides now; a wiki you pick yourself in the chooser still wins, as it always did.

  • A clip filed under your clip folder is shown there. It was being filed correctly and drawn in the wrong place. The sidebar is painted while the clip is still arriving and was not painted again, so a clip safely inside Clippings appeared under Unfiled until something else happened to redraw the tree. Two other ways of saving a page had the same fault and are fixed with it.

  • A page clipped with the bookmarklet stops clipping itself. A whole-page clip that had worked perfectly was never marked as delivered, so MojoPad held on to it and clipped it again every time that wiki opened — for two weeks, the same page arriving as “Title 2”, “Title 3”, with a fresh question about the format each time. It is also asked about in the right words now.

  • The clipper extension is set up for the browsers we say it is. Settings names Chrome, Brave, Edge, Arc and Vivaldi; the piece that lets the extension reach MojoPad was only ever put in place for Chrome and Chromium. If clipping never worked for you in one of the others, it should now.