Another release without inline diagnostics.
I can’t work with a dot in the gutter and an error tucked in the top right corner.
https://github.com/helix-editor/helix/pull/6417
I love helix but this, unfortunately, is workflow breaking for me.
nemith
joined 1 year ago
No harm intended but if you are reaching a conclusion that such a feature is not needed without going into more detail than “harm” can go the other way as well.
Sorry I didn’t link the discussion as I was on my phone and no partonization was intended.
Article is missing a lot of keys points. With iterator you can chain them together to provide even higher level abstractions.
There are plenty of containers (new maps with different algorithms like a BtreeMap, linked lists, etc) that now with generics could also use a generic way of iterating over them.
There was a pre-proposal discussion that went into a lot of detail of what is possible that wasn’t intended the release notes. I highly suggest the writer of this article dig much deeper into more benefits of iterators than the two trivial options that were included in the experiment description.
This point was brought up at the end of the video. You just need to watch it.
This is the terminal that was used by the creator of vi, Bill Joy.
It should be obvious on why those keys were used. They weren’t “mapped” they literally were the arrow keys. It’s hard to change defaults. Anyone who knows vi keybinding and install work on vim or any other system.
It would be easy for you to change your own keybindings. Why is there a need to change everyone’s default and break existing muscle memory.
https://vintagecomputer.ca/wp-content/uploads/2015/01/LSI-ADM3A-full-keyboard.jpg
I mean Tesla cars are just x86 Linux machines