vim-mundo VS riscv-v-spec

there's also telescope-undo and vim-mundo

I don't always need it, but when I do I find vim-mundo incredibly helpful. Understanding the vim undotree is hard without a visualization and mundo's ability to search my undo chunks makes it easy to revive some previous change that wasn't committed to version control.

Still using mundo here (https://github.com/simnalamburt/vim-mundo)

You mean undo/redo? that's u and . To view undos visually you can use a plugin like [vim-mundo](https://github.com/simnalamburt/vim-mundo

I'm glad you found something that works for you, and I don't mean to dissuade you even if I could, but to me that feels like an antipattern if you only use it for typed text.

Consider that with a text editor like Vim, for example, you can "time travel" [0] through your file's edits, or even have undo branches/trees [1][2] available per file. That saves you the trouble of having to transcribe text from screenshots, and also barely uses any storage space.

Plain text is also highly more portable and more likely to be recoverable in case of drive failure or file corruption.

Additionally, or alternatively, you could try any sort of manual versioning system or background automatic backup solution that keeps versions of files as you work on them.

[0]: https://vimtricks.com/p/vimtrick-time-travel-in-vim/

[1]: https://neovim.io/doc/user/undo.html#undo-tree

[2]: https://github.com/simnalamburt/vim-mundo

mundo undo tree

It's not just minutes either, you can do seconds with s, hours with h, days with d and get this - "writes" with w. You can also just simply go back to an arbitrary n number of buffer states before; but just like writes, that's hard to keep track of mentally and instead you should probably use a proper plugin for that.

I used to use Typora before I got into Neovim and realised that it wasn't free software either. Now I'm quite satisfied with my current setup, which uses: - aerial.nvim for header outline and navigation - run-code.nvim for running code blocks - vim-mundo for persistent undo history traversal (like Mac's time machine) - Prettier for auto-formatting Markdown as well as code blocks to their respective languages

Using a plugin like undotree (or Gundo, or Mundo) to visualize the edit history is by far the most practical solution to OP's problem, and I'm shocked you're the only person to suggest it.

There's a fork called mundo which has an inline diff mode that I'm a big fan of — https://github.com/simnalamburt/vim-mundo

Here are some resources I can recommend:

RVV spec (also look at the examples in the repo): https://github.com/riscv/riscv-v-spec/blob/master/v-spec.ado...

RVV intrinsics viewer: https://dzaima.github.io/intrinsics-viewer

Tutorial: RISC-V Vector Extension Demystified (3 hour video going over every instruction): https://youtu.be/oTaOd8qr53U

RISC-V Vector extension in a nutshell: https://fprox.substack.com/p/risc-v-vector-extension-in-a-nu...

If you want to see a more complex example/real world application, then you might also be ibterested ib my article about vectorizing unicode conversions: https://camel-cdr.github.io/rvv-bench-results/articles/vecto...

In terms of development I'd recommend using qemu and a cross compiler, or if you want hardware try to get the kendryte k230 (currently the only sbc with rvv 1.0 support) or wait a bit for better hardware (BPI-F3 and sg2380 should release this year).

And this isn't just some theoretical or something unlikely to happen - the official spec already contains such a bug. If the writers of the spec can't get things right, even with the small amount of code in the spec, I don't have high hopes that less informed programmers will. RVV being absurdly complicated (IMO, compared to SVE2 and AVX10) doesn't help its cause here.

Will the reference one actually be the most optimal one on future hardware?

I'll do a deep dive into the https://gms.tf/riscv-vector.html#getting-started tutorial, and probably pop the proverbial stack and just study RVV 0.7.1 on its own (using https://github.com/riscv/riscv-v-spec/releases/tag/0.7.1).

I see your point. You can file a request for it at https://github.com/riscv/riscv-v-spec/issues if you want to pitch it to the relevant ISA bodies. The bar for implementing it pretty high.

It's not "unusual"; using data registers for mask is a valid tradeoff especially for low-end implementations, whereas higher-end architectures can easily use shadow registers. Discussed in depth at https://github.com/riscv/riscv-v-spec/issues/811