shuka

Exactly that, I completely agree. I don't want to stop using apple notes, I just want to be able to use vim as well.

Even though: "Forecasts may tell you a great deal about the forecaster; they tell you nothing about the future". But historically speaking, AppleScript is pretty stable.

Any ideas?

Damn! I'm so sorry to hear that :(( Happened to me too and I also find it kinda frustrating. As you can see on the README, my first backlog item is to add a diff mechanism. Would also love for help but either way I'm going to add it. In the meanwhile all I can offer is to buy you a coffee and apologize <3

Great! Looking forward to getting some issues and reviews :)

I find this quite amusing

What an awesome project! That's a great idea and it could easily incorporate it, I'd love to help out, let's talk(:

Unfortunately not yet, but that's a great idea! Could you open an issue-or better so, PR—for this?

That's a great idea! Could you open an issue-or better so, PR—for this? I've had some additional backlog ideas.

Oooh not yet, I've thought about it, as well as some other ideas of bulk syncing and diffs. I'd love for open issues—or better so PR's—on the repo!

What I tend to do—you can also see in the readme—is that I push it to Notes, then pull if I've made any changes. When you already have the id on the note, you can move your note anywhere you'd like (:

Yea, it was a bummer they don't have access to it on the AppleScript side. I considered using an x-callback for it but it's not that stable either which is what I was going for. Maybe in the future

That's so great to hear! I'd love to see your next project

It's a mix of the lack of documentation for the response payloads and the integration with the shell commands. My tip would be to wrap everything in shell, handle errors on the AppleScript end, and keeping it incredibly simple.

For example, the errors raised from the AppleScript without printing the error inside a try-catch are incredibly dim. So instead I've opted to wrap them on the AppleScript level, print the error and return an empty string. Kinda reminded me of old-school shitty C code.

I've used Apple Notes for years because it syncs fast and stays out of the way. But when I'm writing in the terminal, there's always been friction getting Markdown into Apple Notes.

Existing tools were either bloated or read-only. So I built Stash: push a Markdown file to Apple Notes, pull changes back. It uses YAML frontmatter to track which note belongs to which file.

Built with Bash, AppleScript, and Pandoc. No databases, no daemons, no config files. Install via Homebrew. Happy to take suggestions and answer questions about the quirks I ran into along the way.