101–110 of 321 posts
Does anyone happen to know if there is a terminal IDE that more or less operates like the very basics of popular GUI IDEs? By this I mean has a file manager pane which can be manipulated by mouse, allows multiple open tabs which are selectable and closable by mouse, is generally mouse-aware with regard to cursor activity on the text, and operates as a regular user would expect (not modal)? The closest thing I've foun…
I gave it a try out of curiosity with Rust, which you might reasonably expect to be well supported. But it didn't start a language server. So I followed the docs to find out how and was none the wiser. A tad undercooked, I'd say.
Documentation is missing, it's a bit scattered
Earlier quoted context omitted.
He is saying that these tools aren't improving his dev process and therefore are not better for him. Better is also such a subjective feeling - please either quantify the improvement or don't present it as an objective truth.
> He is saying that these tools aren't improving his dev process and therefore are not better for him. That would just be a personal preference thing, and it would be fine if they just stated that and left it at that. But they also mention how they are "put off" (wtf) from people who claim that the LSP/tree-sitter support makes this a viable candidate to replace vim/neovim. Saying you're being "put off" by what other…
Earlier quoted context omitted.
Have you checked what that unsafe code does? Unsafe code is not bad per se, there has been quite a bit of discussion about the naming of unsafe and many are of the opinion that it should have better been called something like trustme to clarify that the code must not be necessarily unsafe , just that the borrow checker doesn't fully check here, which for certain core algorithms can be necessary. As long as the conten…
> just that the borrow checker doesn't fully check here, which for certain core algorithms can be necessary Why is that? Does this imply that there are certain algorithms you simply can't write (efficiently) when using the borrow-checker? (I don't know Rust btw, but have plans to start learning very soon)
I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…
I do appreciate Helix as a research project investing in new ideas, but I do feel it a lot more limited. Everything keyboard/motions related just feels much more limited than Vim. For example, re-doing actions makes little to no sense because most actions tend to be split in two. `3dw` can be redone just fine on neovim, but not on Helix.
Earlier quoted context omitted.
Reliable? I trust Tree-Sitter's grammars a hundred times more than the underspecified regex monstrosities that power highlighting in other editors. Tree-Sitter grammars are unit tested, have usable primitives for precedence and associativity, and are generally far more predictable than previous highlighting systems. Also, name a language for which there is no Tree-Sitter grammar yet. The only remaining ones are so ob…
Python, Janet, Haskell, and Hare were the filetypes I remember either being unsupported or not working well. I need to be able to depend on basic language support from my text editor, even when I work with niche languages.
Re Hare: I haven't even set that one up. Setting up a new tree-sitter on neovim requires extra work for each tree-sitter, and that's definitely a flaw that needs to be addressed.
(For those who like the traditional vim binds, I salute you, but I have craved an upgrade for a while now)
I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…
> Those are by far the most important features for a text editor to have The most important feature of a text editor is that it can edit text well. Vim is popular because it’s the best _text editor_ not because it has a bunch of plugins making it an IDE.
Code is text. So it is good to have a very good text editor for manipulating it as text. But code is also very different from plain text. It is highly structured. When I think about code I think about it as some kind of syntax tree (call hierarchies etc) . I don't think about it as character buffers. So if I am programming and I can have something that supports good text editing but also good tree editing then I will take that over something that only does good text editing.
If people want to replace vim, they should not change the keybindings.
It's pretty close to vim keybindings, but the paradigm change makes it incompatible with 1:1 keybindings.
That said, coming from 15+ years of Vim, I was felt pretty much immediately at home with Kakoune, and dropped right in to Helix with comfort.
I fully expect Helix to replace Vim, Neovim, and Kakoune for most users in the long run. Helix is built from the ground up around Tree-Sitter and LSP. This means you get the best syntax highlighting available, and IDE-like functionality, with zero configuration required other than installing the appropriate language server. Those are by far the most important features for a text editor to have, and crucially, they ar…
Can someone elaborate on why Vim doesn’t work well on non-english keyboards. I use Vim occasionally using a Nordic layout but would like to know why English is superior.
Here's a photo of the layout: https://image.shutterstock.com/shutterstock/photos/279261125...
As an Argentinian, I've no fucking idea why we have our own layout instead of just using ISO Spanish.
It doesn't look terrible, but believe me, switching to US English International was a one-way trip.
