Rhapsodizing: thoughts on loading / saving Heynote's buffer

[cablehead]

Have you searched existing Github issues to see if someone has already requested this feature?

Briefly

Is your feature request related to a problem? Please describe.

Feeling the urge to use more than one buffer.

Describe the solution you'd like

It doesn't look like it's currently possible to have more than one buffer (although you could probably swap out the buffer.txt)? I've a hunch that might be intentional to keep Heynote a minimal focused tool? It'd be great to read about the rationale in the README 🙏🏻

Describe alternatives you've considered

Heynote may want to go multi-buffer in the future?

Additional context

I love opinionated small tools 💚

[heyman]

Your hunch is correct. The reason I haven't implemented any kind of support for multiple buffers is to keep Heynote simple and focused.

However, I haven't completely ruled out support for multiple buffers in some form in the future. I have some ideas that I want to explore.

[cablehead]

Just dropping this as an idle thought. Not sure what to do with it..

I use Stacks as my clipboard manager. Which is amazing at collecting your current context into "stacks". It does let you edit a single clip of a stack, with a basic <textarea>. Heynote is much nicer though for editing a "stack of stuff" (codemirror!). Not least because, as I'm editing a clip: I need access to my clipboard manager!

I'm finding myself wanting to "flick" a stack to Heynote (and flick it back). For whatever flick means.

[cablehead]

An experiment in interop with Heynote: https://stacks.cross.stream/releases/v0.15.6#xs-open-a-stack-of-clips-in-heynote