Writing a long paper. A paper is not one page, and it is not only the draft — around it sit the marked-up manuscript your editor sent back, the journal’s guidelines, the interview transcripts, and the thoughts that outgrew this paper and belong to the next one. View ▸ Writing View arranges MojoPad for exactly that: your folder tree on the left, the section you are writing in the middle, and down the right, for that section — what it is meant to do, a word target and how close you are, notes to yourself that never leave the app, and its footnotes as cards you can click to jump to.
And beside all of it, the part that is not a writing app’s usual furniture: what else in your wiki reads like the section you are writing — notes, quotations, pages, and the PDFs and books in your library, offered by meaning rather than by anything you remembered to file. The list changes as you move between sections, and clicking one opens it beside your draft rather than instead of it, with your sentence still where you left it. It reads your own pages on your own Mac; nothing is sent anywhere. There is a new manual chapter, Writing a Long Paper, that walks through the whole shape.
- Your private notes were printing. Notes to yourself and What this section is about promise they are never exported and never printed — and every export honoured that, but printing did not: they came out on the paper in a column beside the page, under the very hint that promised they would not. Anyone who has printed a page with notes on it has printed the notes. Fixed, along with the toolbar and a small window’s title bar, which were printing too.
- Clips go where you meant them to. Until now a clip landed in whichever MojoPad window you had used last, so what you clipped while reading depended on which window happened to be in front — fine with one wiki, a filing accident waiting to happen with several. Settings ▸ Web Clipper ▸ Clip to now lets you name one, and every clip goes there whatever you have open. Leave it on Whichever wiki is in front and nothing changes. Underneath it, File clips under folder names the folder they arrive in — and that folder is now created for you if it is not already there, which it never was before, so the setting simply looked broken. (Asked for by a reader who keeps several wikis — thank you.)
- A clip waits for the wiki instead of being lost by it. This is the important one. If the wiki a clip was going to had not finished opening, the clip was thrown away — silently, while your browser said it had been saved. The same thing happened every time to a wiki with a password: the clip arrived while the unlock screen was up, was discarded, and typing the password did not bring it back. Since the browser extension lets go of its copy the moment it hands it over, the article was gone and nothing anywhere said so. A clip is now held until the wiki is genuinely ready — including waiting on the unlock screen and filing itself the moment you type the password.
- A clip that has nowhere to go says so. If the wiki you named has been renamed, moved, or is on a drive that is not connected, MojoPad used to file the clip into whatever window happened to be in front, without a word — so weeks of reading could quietly accumulate in the wrong wiki while Settings still showed the name you chose. It now tells you, and offers to put the clip in a wiki that is open instead. Clips can also no longer land in the manual, which MojoPad replaces whenever the app updates, or in a small reference card, which cannot record where a clip came from.
- The same for everything else that arrives from outside. A line sent to today’s note from a launcher or a shortcut, and a page printed with Save PDF to MojoPad, could be dropped the same way — and worse, because there is no browser tab to go back to. They wait now too.
- A clip is never reported as saved when it was not. With a lapsed trial, or with a change from another device still unresolved, a clip appeared in the sidebar and said it had been clipped while nothing was written to disk. It now says plainly that it could not be saved, and why.
- The Web Clipper settings say which tool each one is for. There are two ways to clip and they do not take the same settings, but they were listed together with no indication of which was which — with the bookmarklet’s own address sitting at the top, so everything under it read as a bookmarklet setting. They are now grouped by what each applies to, and there is a link to install the extension, which until now the pane described without offering any way to get.
- A small window can be written in, with everything the main window has. Cards could already be edited — the pen in the header — but with no formatting controls and no Find, which made one a place to type rather than a place to write. Turn the pen on and a card now carries the same format bar and the same Find and Replace as the main window; turn it off and it is a clean reading card again. Since each card is its own window, you can draft in one, keep a source open beside it, and work on a translation in a third. (Asked for twice in one letter by an academic who translates quotations while he writes — thank you.)
- Quick capture waits too. A thought typed into the quick-capture panel (⇧⌘7) while its wiki was still opening, or sitting on its password screen, was thrown away while the panel closed as though it had saved. There is no browser tab to go back to for a thought, which makes it the worst place to lose one. It now waits, and if nothing can take it the panel keeps your words on screen instead of closing on them.
- The panel no longer says “saved” before it is. It cleared the box and reported success the instant you pressed Return, while MojoPad was still deciding where the thought should go.
- A dismissed format question no longer reports success. Clipping a whole page asks whether you want it clean or as a snapshot. Dismissing that question threw the clip away and the status line still said it had been clipped.
- Clipping several pages at once keeps all of them. Clips taken in quick succession into a wiki that was not open arrived together and asked their format question over the top of one another; one was answered and the rest were lost.
- Links to a page open the page. A link made with Copy Link to Page, clicked from an email or another app, waited half a second and then gave up — which is nowhere near long enough for a wiki that asks for a password, so it opened the wiki and sat on the home page instead. It now waits properly.
- Turning a Markdown page into plain text no longer leaves backslashes behind. Markdown pages store a backslash in front of characters you typed as text but Markdown would otherwise read as formatting — so that
like thiscomes back as you wrote it rather than turning into italics and losing the asterisks. Once a page is no longer Markdown those backslashes mean nothing, and they used to come across as literal text. (Reported by a reader writing Org-mode inside MojoPad, where asterisks are the formatting and this was exactly the wrong way round — plain-text pages are the answer there, and now the conversion tidies up after itself.) - What a document password covers, stated honestly. Setting a password encrypts your pages and everything about them. It does not encrypt whole files you brought in — an attached PDF, a saved snapshot of a web page, a recording — which sit inside the document readable, under the name they arrived with. The manual said otherwise, which was wrong, and it now says exactly what is and is not covered and what to use when the file itself is the secret. Encrypting those files is being worked on.