> Instead of tapping buttons to bold text or create headers, users could type *bold* or # Header directly into their notes.
Which will be more keystrokes, not fewer – it's faster to get to the formatting buttons than it is the punctuation keyboard on iOS, and even on Mac the shortcut commands are often faster too.
Notes was a fanastic example of a rich-text environment, but if Markdown input helps the die-hards that is great, so long as I don't have to ever see, use or be aware of it.
Apple Notes is used not only with onscreen keyboards in iOS, but also with physical keyboards in iPadOS and macOS, where familiarity with Markdown input could make it faster than shortcut commands.
I tend to copy Markdown content from other sources into Apple Notes. Being able to paste into Notes and have it format in the view is a big win.
It is possible reporting is getting this wrong and the Markdown feature and it is just to serve use case above. As an example, Google Docs recently enabled "Paste from Markdown" that also is a huge convenience.
Yeah, this would be huge for me; I often toss a bunch of notes into an Apple Notepad note just to have it in my pocket, and everything I write with a keyboard is markdown.
This just makes it so I don't have to stare at a bunch of random characters and can have actual formatting. A win in my book!
I think it’s user preference. For me it’s easier to get to the punctuation asterisk (basically muscle memory and <0.5s) than to tap the formatting menu, wait for the keyboard sheet to go down and the formatting sheet to go up, tap Bold, then tap the X and wait for animations to complete again (which I have no muscle memory for and need to look at every UI element that I’m tapping).
But formatting already-typed text on iOS is incredibly fiddly (as you have to select a text span first, and iOS fights you every step of the way when you do this — especially if the span starts or stops at something iOS doesn't consider a "whole token.")
Meanwhile, inserting punctuation representing formatting into already-typed text, merely requires placing the insertion caret, which is much less fiddly.
I was just typing a reply to gush about how much I agree with you and how awful iOS text editing is (I’m on my iPhone at the moment) and decided to play with editing text to get some example complaints, when I had an epiphany:
iOS lets you double tap to start a text selection now. I don’t know when this started. I’m 99% sure I used to long-press to start a text selection, and that it would start highlighting the word under the little preview bubble. My muscle memory is still to do this when I want to highlight text; it just never works and I always get frustrated.
Maybe if I start remembering to double tap to highlight text, the text editing experience might actually start to be passable? :shrug:
(Yes, I know about long pressing the keyboard to use it as a trackpad. I do that most of the time, but it’s still fiddly, it very very often misinterprets a tap and starts text selection wildly off from where I wanted it to, and the only fix is to tap around in the text area.)
But yes, you’re right about editable text being the difference: my memory of long pressing to highlight/select is exactly how text selection works for noneditable text, like in regular web sites in safari.
That’s the big inconsistency, and why I’m always frustrated by iOS text editing. Long pressing normal text highlights it, but long pressing editable text does not.
So it’s not that they changed something, it’s that the behavior is different for editable vs noneditable text, and my brain keeps doing the wrong one. Maybe now that I know about double tapping my brain can finally have a complete picture of the behavior split and I can stop fucking it up each time.
(Although I’m still pretty certain that doing a brief long press, but not long enough for the magnifying glass to show up, used to select a word of text. I can’t prove this though. Maybe I’m remembering the Force Touch days when you used to be able to do a Force Touch while long pressing to expand selection. That would make sense with the timeline.)
hm, here is the original iphone user guide for ios 3.1
> When you’re typing, you canalso double-tap to select a word. In read-only documents, such as webpages, or email or text messages you’ve received, touch and hold to select a word.
Also, double tapping selects by words in editable notes vs by letter in read-only, so the OS will continue to fight you feeble attempts at trying to have a consistent experience!
> iOS fights you every step of the way when you do this
oh, indeed, that's true even for simple movements: you tap somewhere, the cursors jumps there momentarily and then jumps back. You tap again, same thing. So the system knows what you want, but just "competently" engineered in a way to ignore you...
I don’t know if it’s just me, but it feels like it’s gotten more fiddly with time. Either that or I notice it more, because I’m using the thing more as time goes on.
I can’t understand people who use an iPad full time. My dad does this and I don’t know how he does drive himself mad with all the taps required to do basic things.
I first thought it was some kind of extrapolation like... at the rate features are currently being added, Markdown will land in ~2032 with iOS 26... just noticed about the new version numbering, I missed that news!
It sounded to me like a joke, as in “markdown will be supported on February 30th”. Then I read the article text, which seemed serious, and I was confused.
I think the version number from year is quite good. I keep forgetting which version is new and old with the current system. Now it will be easy to remember if you are lagging behind one year, or two or whatever.
Yes; Ubuntu did this from the beginning; (6.06 is the first I've used, and I still remember _when_ I used it), Python's introducing CalVer too (aptly numbered PEP https://peps.python.org/pep-2026/)
what do you mean by marketing? it's based on the year the version is pushed now. Which makes alot more sense at the end of the day and helps to know which version came when
I’m a fan of year based versioning, but this change is likely a response to Samsung doing this, which makes their Galaxy S25 sound newer and more advanced than the iPhone 16.
It’s a silly game to play. Firefox did something similar. Their versioning moved famously slow, then all the sudden they started releasing major versions every other week until their version numbering was compatible to Chrome’s version.
I think it's far more likely that they're doing it to reflect the fact that their products are essentially updated in synchronized waves, and you have to update all at once to get the best out of it (i.e. across macOS/iOS/watchOS/tvOS, if you own all those devices). This way each wave gets an obvious number so you know what matches what.
I would not recommend investing in the iOS Notes ecosystem. There is no way to export these notes with their metadata and media intact without using iCloud. If you need a note-taking app, go with Joplin instead; it supports Markdown, has both iOS and desktop clients, and supports self-hosted syncing.
You can connect iOS Notes with any IMAP server. This supports a reduced feature set (no embedded images, tables, or audio) but does allow for self-hosting.
Interesting. Did they add this feature recently? How do you set it up?
Embedded files (photos, video, audio, PDFs, etc.) and bullet hierarchies were the two things that I remember being the most trouble; you can copy bullet hierarchies from iOS Notes and paste them into another app, but they aren’t detected when copying the note via Shortcuts. Embedded files had to be manually saved. I think you could Airdrop notes to a MacOS device, but it would wipe the date created metadata from what I remember.
I wrote python code to extract the notes years ago[1], but it's bit-rotted, so it no longer supports tables, raw stroke data, or the newer features like equations. Maybe I'll update it someday, but I'm not using notes at the moment and have too many other things going one.
This is great until you edit your notes on IMAP from more than one app. Apple Notes, Outlook, Gmail, and others with access to IMAP notes will corrupt one another's entries very easily. Style is also very difficult to control in this setup.
Apple Notes is not intended for people who want to own their data and have control over export
I really wish Apple would revisit third-party server support with something more modern, such as a Markdown + file hosting backend (over WebDAV or whatever they currently consider the cool way of file sharing), but I'm not holding my breath.
“Apple is working on supporting the ability to export notes in Markdown from Apple Notes, which is something third-party apps have supported for years.”
Am I misunderstanding or is that the feature you were asking for? If not then what does the article mean by export?
That would fix the problem if it supported the export of indentation and attachments, but I would still never bother with a proprietary solution when a free-as-in-freedom solution already exists.
I’m still holding out for a phone I can use as a general-purpose computer, though, so take that for what it’s worth.
It does not, although you can open notes in iCloud via a browser, and I’m not acquainted with how that functions in the UK (and if it’s available), mostly because I don’t do it.
I use Obsidian these days, I found the switch from Apple Notes pain free. I still think Apple Notes is a great app for almost everyone. Not perfect but really good.
I went this way as well. I used to try and make all my notes in Notion. But found the lack of offline support and the mobile app very limiting. Then I tried Apple Notes with a framework called "Forever Notes". Obsidian does everything Forever Notes does but better.
I’ve used my google account for notes for years. The earliest one looks like it was around 2014. Have you tried adding an email address from a platform that supports notes?
I love Apple Notes for being easy and “just works” within the Apple Ecosystem. Easy to share with family, notes updated across devices, etc.
Markdown support is a nice addition and hope this makes it easy to transfer notes with other app faster and an intact formatting across the journey.
However, I use it as a starting entry point for my notes, which are mostly temporary, rough, and ephemeral. These notes are the ones I won’t mind losing and can walk out. Anything important or critical that is added here is eventually moved to a plain-text note (Markdown) elsewhere.
> There is no way to export these notes with their metadata and media intact without using iCloud.
You can have an Apple Notes folder backed by IMAP which lets you get at the notes as `multipart/related; type="text/html"` emails (including media). I use it on my servers for family-controlled email allow/deny lists.
(Definitely more faff to deal with than something like Obsidian or Joplin's Markdown notes though.)
Can't give a definitive answer but my allow/deny list parser has always used `MIME::QuotedPrint` through `html2text` to convert them from MIME'd HTML into plain text and that was last updated September 2021.
I've also got a test note from late 2020 which is also `text/html; quoted-printable` which suggests at least iOS 14 (I don't think the 15 alphas would have been out by then.)
Just a sidenote: you can use Git in iOS as well if you are brave enough.
E.g. with Obsidian your notes are stored into specific directory and it stores files as Markdown in hierarchical way. Then mount this app-specific directory to iSH and use git. Downside is that automatic syncing can be difficult since there is limited amount of time iSH can run in the background.
Notes: I'm stuck with this and wish I could leave, but the combo of security and attachments leaves me with few options. Notes is buggy, lacks interoperability, has crap AI integration, etc. BUT... the real pain is Apple Messages. The inability create folders, rules, etc. is insanity. At a time when most comms are instant why would you not offer users the same level of organization they enjoy with email, or with other IM platforms?
Markdown export would be appreciated. My number one concern with Notes is that it is 100% opaque file formats (weird serialisation inside SQLite and no api). Backup to markdown would be great.
It's not a coincidence at all. Markdown is the "native" language for most LLMs, and the hype around it requires even low-level tools to support it (for both legitimate and marketing reasons)
If you post something even slightly outside the current hype, it's very much hit-and-miss whether it gets eyes. It also depends on day of week and time of day when it was posted. Repeated reposts used to take care of that but they've been made impossible, probably because of spam and abuse.
I really hope Apple Notes makes this something that's opt-in and I don't have to see. Thankfully it sounds like it is an export only feature.
I think there is a bifurcation of people who like markdown and people who like rich text. And both groups have strong opinions. Apple Notes was my goto rich text editor. Fingers crossed that they aren't making this worse for us.
Related: I switched away from Bear notes because personally I find markdown hideous to look at. This post made me go back and check on it today and it looks like Bear notes now supports hiding markdown right after you type it. This seems like a really good compromise, though I still don't like that I see it when I place my cursor on it. Worth a shot if you're a "never markdown" person like me.
Bear’s implementation is great. One thing I hate about rich text is that it's basically impossible to not inherit the formatting of adjacent text if you move your cursor around, nor is it possible to see the current formatting state. If your cursor is between whitespace and an italic word, will inserted text be normal or italic? Markdown’s formatting characters solve this by creating a boundary that the cursor can be on either side of.
Interesting, because I find that very intuitive. If my cursor is on or next to formatting, it'll inherit it.
I find formatting after the fact a lot easier too. Bold a line? cmd+shift-right and then cmd+b. Trying to add formatting after the fact with markdown isn't fun. Though many editors try to helpfully insert markdown for you with hotkeys, it often fails on multi-line things.
This is a solved problem, but not implemented almost nowhere. Your text cursor can simply show whether text is going to be italic with an indicator. And moving cursor an extra step away from the italicized word will reset the formatting to that of the space char. But also panels in many apps show current formatting in their formatting button state
I take all of my notes on ChatGPT now, and for more structured data I have built specialized tools/agents, and even small front ends like for my portfolio management track.
It’s crazy how different my world used to be back then; note apps feel so primitive now.
For example I have a thread for engineer status updates. I get the call transcripts from an internal app my company developed and I push everything into ChatGPT. When I need to recall something, I just ask ChatGPT. It is much better than indexed search.
If I need to just write and don’t want feedback, i tell ChatGPT to not reply until I say so, and I will just write in the most lazy and disparaged way, a true brain dump, When I am ready, ChatGPT will sort out my thoughts.
If conversations get too large I summarize everything that’s important and migrate to another conversation.
I'm suspecting this is because future Apple Intelligence features (when they actually get released) will allow LLMs to write notes, and of course we all know markdown is well understood by LLMs.
As another commenter said, they haven't officially announced it yet. That said, it's all I've heard about in the Apple world for the last couple of days¹, so it may just be that you don't follow Apple news closely.
After reading the comments here about the new numbering, I wonder if skipping 19 was part of the reasoning for the change. They may not want to be associated with COVID-19.
Markdown is the defacto language of the llms. Between this and the python library from Microsoft that converts all of their formats to markdown I think that markdown officially has won the markup language war.
I also vote for HTML. It’s the only language I can write in which also includes all the metadata I want to include (schema.org and wikidata.org ontologies).
I’m very curious about why I’ve been downvoted. I assumed the HN crowd was tech-savvy enough to know what ontologies are? And one can’t write a blog post in Turtle.
Depends on which war we are talking about. Personal writing? Professional writing? Machine-readable? For personal writing, HTML is not really participating, for the rest, mostly yes, even though for AI-tooling markdown seems the preferred language now.
Which opens the question, is there a real advantage in using Markdown with AI instead of HTML? Or did nobody ever tried this?
That keyboard was such a POS that a Wall Street Journal writer did a feature story on it without correcting any of the mistakes the keyboard introduced. It was essentially illegible. Then the Web site had buttons that you could push to remove each kind of error and make it legible: https://www.wsj.com/graphics/apple-still-hasnt-fixed-its-mac...
Which is funny because it’s really an incomplete spec that originated from a blog post. But it won anyway because both machines and humans can use it with relative ease, which is apparently quite a difficult thing to achieve in a markup language
It might be my Emacs bias, but I find Org much nicer as a format. For instance, timestamps and todo items make it trivial to use Org as a planner. This would be great to have in applications such as Apple Notes.
I love org-mode, but if I were king, it would accept freakin' back-quotes for monospaced text. Instead, it takes ~tilde~ or =equals=, and I will never remember the difference no matter how many times I look it up.
This is also the primary hangup that's kept me from adopting org-mode for notes, and I instead keep everything in MarkDown, and miss out on all the org-mode organization effects. The differences in link syntax are hard too, but I've got 5-10 years of DokuWiki in my history that make the link syntax more palatable. However, I still prefer MarkDown syntax for links too...
I switch between Markdown and Org Mode a lot, the syntactic differences don't bother me too much, but I guess I like Markdown's a bit more. But what I really miss in Markdown:
6. Inline LaTeX and document generation in general.
Now 1 is just an editor feature, and some of these others could be, too. But I wish Markdown was more powerful, extensible, or less ubiquitous.
What bothers me most about Org Mode is that support is pretty limited outside Emacs. We use it as a wiki replacement at my company, for that integrations into other editors are kinda good enough. But there's some areas like reporting only Emacs users can realistically work on. GitLab (and Forgejo, which we recently switched to) render Org pretty nicely, so it's easy to consume in a browser. But editing is a different story.
So I guess I wish for either a less complex (and thus easier to support) Org, or a more powerful Markdown.
I’ve seen a lot of apps extend markdown to support various additional features. Obsidian, for example, has an extensive number of community plugins which offer a ton of features.
This of course ends up being editor specific, but if org has the same limitation, by being tied to emacs, is it really any different? I think what emacs has going for it in this case is that it’s been around for decades, and we can assume it will continue to be around for decades into the future. The markdown editor de jour may not be.
But for the life of me, there are so many things I hate about Markdown:
- Alternative syntax for _italic_ *italic* and __bold__ **bold** (why?)
- versus using /italic/ and *bold*. It just feels so right
- You need to use HTML tags <u>to underline</u>, or <s>strikethrough</s>, or just about anything in Markdown (including line breaks! You need to use the <br> tag)
- +strikethrough+ is alright, but _underline_ just makes sense
- Lack of a unified Markdown standard:
- Diminishes portability (e.g. varying approaches for file meta tags like in Obsidian)
- Causes different renderings of the same document (e.g. Obsidian vs GitHub)
- There was a serious standardization effort in 'Standard Markdown', only for the original creator to be a knob about it: https://blog.codinghorror.com/standard-markdown-is-now-common-markdown/
It's a shame too because despite Orgmode being superior to Markdown in just about every way, its adoption is nowhere near as close (editing is hard on iOS, and needing Emacs is a barrier for the general public).
Which is what frustrates me with the invention of Markdown.
A ten minute web search would have revealed it was already a solved problem, instead of splintering and inventing a new 'standard'. But that was somehow too much effort.
Markdown was never created as a standard, it was created to fit one person's workflow and how they liked to format documents. It just so happened that it's pretty similar to how many others like to format documents.
You can have all that and even more with Markdown too, but it comes with the price of "vendor lock-in", as most of those are kinda optional and depending on which markdown-app you are using. On the other side, org-mode has also kind of a vendor lock-in, as there is only one leading and format-defining app, even if there are a handful of clones implementing a subset of its features. Though, at the moment org-mode, has a slight advantage in having a more well-defined and maintained format-definition, while Markdown seems more a chaotic meltingpot of anything goes.. but it seems the community-effect manifests in the long run, and people settle on new features and their syntax. The only thing missing is a proper definition of this, which is supported by everyone. Obsidian seems to have enough weight to pull this at the moment, but we will see.
Markdown handles complexity by allowing html to be freely put into the doc. The basics are really easy, and if you need to do something more advanced html exists. Though this can sometimes make readability drop to 0. I ended up doing this for a complex table I wanted in a readme file, and kind of regret it. I have to explain to people on my team how to use preview mode in their editor, or to view it in the repo online. Although that view online does look nice.
I mean it’s the same problem with mermaid but I still use that pretty religiously. Being able to have your README natively render graphs is super useful and most engineers these days have a markdown previewer built in to the software they use eg vscode
Except of course that almost nobody makes a READER for Markdown. WTF? It's mystifying.
You find readme documents in Markdown in every open-source repo, but why? What are you supposed to read them with?
After much searching I finally ended up with Marked, on the Mac. A paid app. But that's about it for options. And no, I'm not talking about text editors that offer a "preview" pane that you can optionally invoke. I'm talking about a simple reader for Markdown that renders it, so you're not reading a shitty text file with a bunch of formatting codes in it. Why bother putting them in, if nothing parses and acts on them?
What a dumb pain in the ass. Do you seriously check out a repo, run the read-me file through a Markdown-to-HTML converter, and then launch a browser to read the result?
Many modern editors, including VS Code, have a button which opens a preview pane to see rendered Markdown. It’s a single button click (the page with the magnifying glass on it in the upper right), no one is installing pandoc to read readme files.
The preview is really only needed if there is advanced formatting or HTML in there. A basic markdown doc should be easy to read in plain text.
Thus my point. If everyone's answer is "just read the plain text," then why have the junk in it at all?
And I don't want an extra "preview" pane. That was the specific complaint. Nor do I want these docs in my IDE at all. I want all the available space in my IDE for code.
Again, why have this format all over the place when there are vanishingly few VIEWERS for it? Or vice versa?
Thanks! But then why not just use plain text? Because of the lack of widely-available, lightweight Markdown readers, everyone just ends up reading the text with a bunch of codes in it. It's just... dumb.
I'm not "playing dumb" it's basically exactly the type of text I would type in my notes before it was codified. Headers, bullets, bold, italic, all would have fit in perfectly in text-based Usenet groups of the 90s.
It's not "clutter" it's meaningful information for the human eye in plain text.
Which is why I'm asking: what's your alternative? Is it no headers, no lists, no standard * or \_ for emphasis, as it has been done long before Markdown existed?
Except that they aren't shown as bullets, headers, or bold unless your viewer understands the Markdown codes that invoke those decorations. Which is what I'm decrying the lack of.
My "alternative" is to have DEDICATED, lightweight Markdown viewers. The major OSes have long come with a simple text-file viewer that can render RTF. Why not Markdown?
In the meantime, I'm mystified as to why the format is so rampant when there is so little support for it.
The whole point of Markdown is that the formatting codes intutitively make sense and are readable even without a viewer and without needing to read a specification first. People have been using asterisks as bullet points and to emphasise things long before anyone came up with Markdown.
Maybe it doesn't to you, but it does to most people.
Typically, italic formatting indicates gentle emphasis, bold formatting indicates strong emphasis. Given this, * and * make sense. However, typically people use _ for gentle emphasis in Markdown, which makes _even more_ sense. Be careful not to confuse specification of rendering,
As for - and >, they've been in use in plain text email clients for bulleted lists and quotations for 35 years now [1].
I'm not confusing anything. I'm saying that the example I provided is not intuitively recognizable as a block quote. And it gets worse when you have more nested decorations.
Those formatting codes are informative content. They tell the reader (even in plain text) that something is a section heading, bullet, code, etc.
This is information people often want in a plain text file, and having a common way to signal those things is beneficial when working on teams or sharing with others.
What’s the alternative? Everyone makes up their own bespoke way of formatting their text file that works for them, then has a key to explain it in their doc?
I was going to call out that out as a strawman, knowing that it doesn't meet the classic definition. Let me look up what's it's called when you bury a not-agreed-with assertion in a question that requires the recipient to agree with it...
Ah, so that's the definition of a "loaded question." Thanks for the fallacy!
"Loaded Question: A loaded question contains an assumption that may or may not be true or agreed upon. It's designed to trap the respondent into confirming a premise they might not agree with, regardless of their answer.
Complex Question Fallacy (or plurium interrogationum): This is a logical fallacy where the question presumes the truth of something that may be false or unproven. Answering it directly implies agreement with that presupposition."
Typora, obsidian, marktext, vscode and emacs with the right extensions, etc. Most people don't care enough to search them out, but you have a good number of choices available.
Thanks, but most of those are examples of exactly what I'm talking about: an editor with a Markdown "preview" function tacked on. I just want to double-click on the .md file and read it in a rendered form. Otherwise... what's the point?
And because of the lack of such readers, everyone just reads the plain text with a bunch of garbage in it. It's just gallingly dumb.
And read-me files are for, <gasp>, READING. Not writing. I have no need to EDIT any Markdown files... pretty much ever. Nor do I need to clutter my IDE with tabs devoted to reference material, much less an extra pane to "preview" it in its intended rendering.
Your pretension that most programming involves writing Markdown "source code" is absurd. I neither want nor need Markdown in any of my source-code editors, ever. Not once in decades of professional programming have I missed it.
And if I do need to create Markdown, I will want to do so in a simple WYSIWIG editor and save it as MD. Again... not in my IDE.
Someone writes the README... And WYSIWYG? Who uses those?
And how often are you even reading READMEs? For me it's usually once, when I first use a library, because it typically gives an outline of the project and/or instructions on how to install it. So I'm reading it in a browser.
Meanwhile I'm updating my own READMEs often, usually using them as a sort of to-do list and then outlining existing functionality.
Like, are you really using so many libraries as glue that reading READMEs is such a common task that you specifically want it in your IDE? Is that the current state of programming?
I'm not familiar with the first two, but did try MarkText. I don't remember why, but I ended up paying for Marked. Thanks for the references; I'll check those others out.
For a second there I thought you were referring to a hardware solution. It would be pretty neat if I could drop straight markdown files into my Kindle and have them rendered in an aesthetically pleasing fashion.
Thanks, but that's a prime example of having to launch an editor and invoke a "preview" function (after installing a plug-in) to view this inexplicably ubiquitous format.
It's even dumber when you ponder: What is this a "preview" of? How the document will look in... a nonexistent viewer?
HTML is. Markdown is a way of writing it that is human friendly. A notes app that can do rich-text to expressive HTML would be even better but it seems like that's not what the market is interested in.
And if you doubt me on that last point, look at things like callouts in Obsidian, clearly people want to be able to do more but we keep tacking weird formatting extensions onto Markdown.
276 comments
[ 3.3 ms ] story [ 248 ms ] threadWhich will be more keystrokes, not fewer – it's faster to get to the formatting buttons than it is the punctuation keyboard on iOS, and even on Mac the shortcut commands are often faster too.
Notes was a fanastic example of a rich-text environment, but if Markdown input helps the die-hards that is great, so long as I don't have to ever see, use or be aware of it.
It is possible reporting is getting this wrong and the Markdown feature and it is just to serve use case above. As an example, Google Docs recently enabled "Paste from Markdown" that also is a huge convenience.
This just makes it so I don't have to stare at a bunch of random characters and can have actual formatting. A win in my book!
AIUI it's only Markdown export support for now
Meanwhile, inserting punctuation representing formatting into already-typed text, merely requires placing the insertion caret, which is much less fiddly.
iOS lets you double tap to start a text selection now. I don’t know when this started. I’m 99% sure I used to long-press to start a text selection, and that it would start highlighting the word under the little preview bubble. My muscle memory is still to do this when I want to highlight text; it just never works and I always get frustrated.
Maybe if I start remembering to double tap to highlight text, the text editing experience might actually start to be passable? :shrug:
(Yes, I know about long pressing the keyboard to use it as a trackpad. I do that most of the time, but it’s still fiddly, it very very often misinterprets a tap and starts text selection wildly off from where I wanted it to, and the only fix is to tap around in the text area.)
But yes, you’re right about editable text being the difference: my memory of long pressing to highlight/select is exactly how text selection works for noneditable text, like in regular web sites in safari.
That’s the big inconsistency, and why I’m always frustrated by iOS text editing. Long pressing normal text highlights it, but long pressing editable text does not.
So it’s not that they changed something, it’s that the behavior is different for editable vs noneditable text, and my brain keeps doing the wrong one. Maybe now that I know about double tapping my brain can finally have a complete picture of the behavior split and I can stop fucking it up each time.
(Although I’m still pretty certain that doing a brief long press, but not long enough for the magnifying glass to show up, used to select a word of text. I can’t prove this though. Maybe I’m remembering the Force Touch days when you used to be able to do a Force Touch while long pressing to expand selection. That would make sense with the timeline.)
> When you’re typing, you canalso double-tap to select a word. In read-only documents, such as webpages, or email or text messages you’ve received, touch and hold to select a word.
Also, double tapping selects by words in editable notes vs by letter in read-only, so the OS will continue to fight you feeble attempts at trying to have a consistent experience!
oh, indeed, that's true even for simple movements: you tap somewhere, the cursors jumps there momentarily and then jumps back. You tap again, same thing. So the system knows what you want, but just "competently" engineered in a way to ignore you...
I can’t understand people who use an iPad full time. My dad does this and I don’t know how he does drive himself mad with all the taps required to do basic things.
It’s a silly game to play. Firefox did something similar. Their versioning moved famously slow, then all the sudden they started releasing major versions every other week until their version numbering was compatible to Chrome’s version.
(Wait, I am.)
Embedded files (photos, video, audio, PDFs, etc.) and bullet hierarchies were the two things that I remember being the most trouble; you can copy bullet hierarchies from iOS Notes and paste them into another app, but they aren’t detected when copying the note via Shortcuts. Embedded files had to be manually saved. I think you could Airdrop notes to a MacOS device, but it would wipe the date created metadata from what I remember.
You just connect the account and turn on the notes synchronisation (right below calendar synchronisation).
https://github.com/dunhamsteve/notesutils
Apple Notes is not intended for people who want to own their data and have control over export
I really wish Apple would revisit third-party server support with something more modern, such as a Markdown + file hosting backend (over WebDAV or whatever they currently consider the cool way of file sharing), but I'm not holding my breath.
Just tested and embedded images do seem to be supported?
("insert photo" -> add photo -> photo is stored as a MIME part on the note)
Which PM comes up with this? And what does a developer thing when they implement this?
“Apple is working on supporting the ability to export notes in Markdown from Apple Notes, which is something third-party apps have supported for years.”
Am I misunderstanding or is that the feature you were asking for? If not then what does the article mean by export?
I’m still holding out for a phone I can use as a general-purpose computer, though, so take that for what it’s worth.
If so then the UK does not have E2E Notes.
https://support.apple.com/en-la/102537#:~:text=Open%20Notes%...
I applaud the effort simonw put into this, it works great on macOS... the platform AppleScript runs on.
I try other systems and then I end up wanting the simplicity of notes.
Markdown support is a nice addition and hope this makes it easy to transfer notes with other app faster and an intact formatting across the journey.
However, I use it as a starting entry point for my notes, which are mostly temporary, rough, and ephemeral. These notes are the ones I won’t mind losing and can walk out. Anything important or critical that is added here is eventually moved to a plain-text note (Markdown) elsewhere.
https://brajeshwar.com/2025/notes/
You can have an Apple Notes folder backed by IMAP which lets you get at the notes as `multipart/related; type="text/html"` emails (including media). I use it on my servers for family-controlled email allow/deny lists.
(Definitely more faff to deal with than something like Obsidian or Joplin's Markdown notes though.)
I've also got a test note from late 2020 which is also `text/html; quoted-printable` which suggests at least iOS 14 (I don't think the 15 alphas would have been out by then.)
E.g. with Obsidian your notes are stored into specific directory and it stores files as Markdown in hierarchical way. Then mount this app-specific directory to iSH and use git. Downside is that automatic syncing can be difficult since there is limited amount of time iSH can run in the background.
https://zapier.com/blog/export-apple-notes/
There are ways to export, definitely not as straightforward as other tools.
Edit: The article has since been corrected.
Overall, I'm surprised to see markdown become mainstream so quickly.
https://blogs.windows.com/windows-insider/2025/05/30/text-fo...
https://9to5mac.com/2025/06/03/exclusive-ios-26-messages-car...
They are rebranding it to reflect the year, à la FIFA 26
I think there is a bifurcation of people who like markdown and people who like rich text. And both groups have strong opinions. Apple Notes was my goto rich text editor. Fingers crossed that they aren't making this worse for us.
Related: I switched away from Bear notes because personally I find markdown hideous to look at. This post made me go back and check on it today and it looks like Bear notes now supports hiding markdown right after you type it. This seems like a really good compromise, though I still don't like that I see it when I place my cursor on it. Worth a shot if you're a "never markdown" person like me.
[1]: https://whatever.com
I find formatting after the fact a lot easier too. Bold a line? cmd+shift-right and then cmd+b. Trying to add formatting after the fact with markdown isn't fun. Though many editors try to helpfully insert markdown for you with hotkeys, it often fails on multi-line things.
I take all of my notes on ChatGPT now, and for more structured data I have built specialized tools/agents, and even small front ends like for my portfolio management track.
It’s crazy how different my world used to be back then; note apps feel so primitive now.
If I need to just write and don’t want feedback, i tell ChatGPT to not reply until I say so, and I will just write in the most lazy and disparaged way, a true brain dump, When I am ready, ChatGPT will sort out my thoughts.
If conversations get too large I summarize everything that’s important and migrate to another conversation.
I can't even imagine what this even means.
¹ well that and the iOS redesign.
https://daringfireball.net/linked/2025/06/03/sdw-physicality...
That's a shame. I was hoping for at least the option to edit in markdown (and praying for LaTeX support too)
This gave me the belly laugh I needed, thanks!
In some contexts, JSX and markdown are also competing.
I think HTML is the true winner.
Which opens the question, is there a real advantage in using Markdown with AI instead of HTML? Or did nobody ever tried this?
Oh wait, maybe it's 30% of it is repeated...
That keyboard was such a POS that a Wall Street Journal writer did a feature story on it without correcting any of the mistakes the keyboard introduced. It was essentially illegible. Then the Web site had buttons that you could push to remove each kind of error and make it legible: https://www.wsj.com/graphics/apple-still-hasnt-fixed-its-mac...
The official manual states equals is used for =verbatim= quotes: https://orgmode.org/manual/Emphasis-and-Monospace.html
1. Collapsible headlines and headline search.
2. Executable source code blocks (for notebook style work).
3. TODO states.
4. Time tracking and clock tables.
5. Table formulas.
6. Inline LaTeX and document generation in general.
Now 1 is just an editor feature, and some of these others could be, too. But I wish Markdown was more powerful, extensible, or less ubiquitous.
What bothers me most about Org Mode is that support is pretty limited outside Emacs. We use it as a wiki replacement at my company, for that integrations into other editors are kinda good enough. But there's some areas like reporting only Emacs users can realistically work on. GitLab (and Forgejo, which we recently switched to) render Org pretty nicely, so it's easy to consume in a browser. But editing is a different story.
So I guess I wish for either a less complex (and thus easier to support) Org, or a more powerful Markdown.
This of course ends up being editor specific, but if org has the same limitation, by being tied to emacs, is it really any different? I think what emacs has going for it in this case is that it’s been around for decades, and we can assume it will continue to be around for decades into the future. The markdown editor de jour may not be.
Either Markdown++ or Org Lite. I'll take either :) I'm not a fan of coupling formats and tools tightly.
I also like [Markdown's text first](https://hyperlink.com) then link format much more than [[https://hyperlink.com][Orgmode's link first then text]].
But for the life of me, there are so many things I hate about Markdown:
It's a shame too because despite Orgmode being superior to Markdown in just about every way, its adoption is nowhere near as close (editing is hard on iOS, and needing Emacs is a barrier for the general public).Markdown isn't going away anytime soon.
A ten minute web search would have revealed it was already a solved problem, instead of splintering and inventing a new 'standard'. But that was somehow too much effort.
https://raw.githubusercontent.com/git/git/refs/heads/master/...
When the original is in markdown, it's somehow always noticeable.
It's the new classic example of "worse is better".
Other markups may be more well thought out and more complete, but Markdown beats them hands down on usability.
Consider the comparison between MD and RST, for example...
You find readme documents in Markdown in every open-source repo, but why? What are you supposed to read them with?
After much searching I finally ended up with Marked, on the Mac. A paid app. But that's about it for options. And no, I'm not talking about text editors that offer a "preview" pane that you can optionally invoke. I'm talking about a simple reader for Markdown that renders it, so you're not reading a shitty text file with a bunch of formatting codes in it. Why bother putting them in, if nothing parses and acts on them?
Browsers read html. You're supposed to read markdown with a browser by rendering it to html and reading the html.
Or, from the other angle, with Markdown being found in so many places, why aren't there popular viewers for it?
The preview is really only needed if there is advanced formatting or HTML in there. A basic markdown doc should be easy to read in plain text.
And I don't want an extra "preview" pane. That was the specific complaint. Nor do I want these docs in my IDE at all. I want all the available space in my IDE for code.
Again, why have this format all over the place when there are vanishingly few VIEWERS for it? Or vice versa?
If you're on macOS though, the best option for rendered Markdown is a quicklook plugin. There are a few around - I like [1] though.
[1]: https://github.com/smittytone/PreviewMarkdown
What is your alternative to Markdown here?
If everyone's just using a plain-text reader to view these files, then why clutter them up with formatting codes?
It's not "clutter" it's meaningful information for the human eye in plain text.
Which is why I'm asking: what's your alternative? Is it no headers, no lists, no standard * or \_ for emphasis, as it has been done long before Markdown existed?
My "alternative" is to have DEDICATED, lightweight Markdown viewers. The major OSes have long come with a simple text-file viewer that can render RTF. Why not Markdown?
In the meantime, I'm mystified as to why the format is so rampant when there is so little support for it.
Maybe it doesn't to you, but it does to most people.
An update to Microsoft Notepad which renders Markdown is currently being rolled out: https://blogs.windows.com/windows-insider/2025/05/30/text-fo...
I'm not sure I agree *something* is intuitive for italic and **something else** is intuitive for bold, or that this is intuitively a block quote:
> #### The quarterly results look great!
>
> - Revenue was off the chart.
> - Profits were higher than ever.
> > Everything is going according to *plan*.
As for - and >, they've been in use in plain text email clients for bulleted lists and quotations for 35 years now [1].
[1]: https://en.wikipedia.org/wiki/Posting_style#:~:text=The%20co...
This is information people often want in a plain text file, and having a common way to signal those things is beneficial when working on teams or sharing with others.
What’s the alternative? Everyone makes up their own bespoke way of formatting their text file that works for them, then has a key to explain it in their doc?
Every source control website I've used will render Markdown as HTML for you.
Ah, so that's the definition of a "loaded question." Thanks for the fallacy!
"Loaded Question: A loaded question contains an assumption that may or may not be true or agreed upon. It's designed to trap the respondent into confirming a premise they might not agree with, regardless of their answer.
Complex Question Fallacy (or plurium interrogationum): This is a logical fallacy where the question presumes the truth of something that may be false or unproven. Answering it directly implies agreement with that presupposition."
The IDE that I use most of the time also renders markdown.
And because of the lack of such readers, everyone just reads the plain text with a bunch of garbage in it. It's just gallingly dumb.
That's what documentation generators are for, to render all the docs and search them if you're just a user.
Your pretension that most programming involves writing Markdown "source code" is absurd. I neither want nor need Markdown in any of my source-code editors, ever. Not once in decades of professional programming have I missed it.
And if I do need to create Markdown, I will want to do so in a simple WYSIWIG editor and save it as MD. Again... not in my IDE.
And how often are you even reading READMEs? For me it's usually once, when I first use a library, because it typically gives an outline of the project and/or instructions on how to install it. So I'm reading it in a browser.
Meanwhile I'm updating my own READMEs often, usually using them as a sort of to-do list and then outlining existing functionality.
Like, are you really using so many libraries as glue that reading READMEs is such a common task that you specifically want it in your IDE? Is that the current state of programming?
Are you being intentionally obtuse? I said that's exactly what I DON'T want.
.gitignore or .ignore file...
text on the left, render on the right pane
example: https://imgur.com/9rjoMa2.png
It's even dumber when you ponder: What is this a "preview" of? How the document will look in... a nonexistent viewer?
Thank you for pointing me to the MarkItDown library [1]. I had no idea such a thing existed.
[1] https://github.com/microsoft/markitdown
And if you doubt me on that last point, look at things like callouts in Obsidian, clearly people want to be able to do more but we keep tacking weird formatting extensions onto Markdown.