Live data from Hacker News

Apple Notes Expected to Gain Markdown Support in iOS 26

macrumors.com

251–260 of 277 posts

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#251
post #143

Earlier quoted context omitted.

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: 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…

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…

Yeah, that's my thinking with these tools. I think it needs to be more of a standard.

Either Markdown++ or Org Lite. I'll take either :) I'm not a fan of coupling formats and tools tightly.

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#252
post #122

Okay, am I the only one who didn’t know that (apparently) the next iOS version is going to be 26, not 19? I assume, they’ll start following a year of release both for macOS and iOS, so it would be easier to know for non-techies. But my first reaction was ‘em, 8 years into the future? Looks weird, isn’t it? Maybe that’s some kind of a joke.’

19 + 7 = 26, lucky number 7!

Haha, nice finding!

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#253
post #4

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.

https://sixcolors.com/member/2021/01/export-your-apple-notes...

https://zapier.com/blog/export-apple-notes/

There are ways to export, definitely not as straightforward as other tools.

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#254

Earlier quoted context omitted.

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/ )

That PEP has been rejected.

ah TIL! I only read it when it was first proposed.

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#256

Earlier quoted context omitted.

> You find readme documents in Markdown in every open-source repo, but why? What are you supposed to read them with? Every source control website I've used will render Markdown as HTML for you.

So you need to round-trip it through a Web site? Wow, convenient.

It's always been very convenient for me since that's where I do most of my readme reading.

The IDE that I use most of the time also renders markdown.

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#257
post #4

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.

I've been using this app for years to export Apple Notes to markdown backups (no affiliation, just a user): https://apps.apple.com/us/app/exporter/id1099120373

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#258

Earlier quoted context omitted.

> ... it’s really an incomplete spec ... . But it won anyway 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...

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 onlin…

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

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#259
post #115

Earlier quoted context omitted.

=string= leads to the text being transcribed verbatim. A good hint is to recall that the equals sign kinda implies verbatim.

Ironic then that [0] (the first hit when I search "emacs org mode tutorial") says: You can make words *bold*, /italic/, _underlined_, =code= and ~verbatim~, and, if you must, +strike-through+. [0]: https://orgmode.org/worg/org-tutorials/org4beginners.html

That seems to be a very old tutorial. It's indeed confusing that they host that on the official site.

The official manual states equals is used for =verbatim= quotes: https://orgmode.org/manual/Emphasis-and-Monospace.html

Re: Apple Notes Expected to Gain Markdown Support in iOS 26

#260
post #49

Earlier quoted context omitted.

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.
Post reply on HN