51–60 of 142 posts
Helix's features look very cool, but I could not switch to it because of this bug [0]. It has been open since May 2022 and it is still not fixed. Basically you can't exit insert mode with a key combination like `jk`. Four years feels like a long time for such a basic bug. I will stick to NeoVim for now. 0. https://github.com/helix-editor/helix/issues/2612
Helix's features look very cool, but I could not switch to it because of this bug [0]. It has been open since May 2022 and it is still not fixed. Basically you can't exit insert mode with a key combination like `jk`. Four years feels like a long time for such a basic bug. I will stick to NeoVim for now. 0. https://github.com/helix-editor/helix/issues/2612
I went to Zed for this reason.
I do almost all my development on JetBrains IDEs (Rust, Python, Kotlin). IME they are unmatched for giving you code insights and suggested fixes (combined with "click here to do that") out of the box. But they are absolute resource hogs and I don't trust that they (or their best features) will always remain free. I've tried to get into neovim a few times. It's fine for basic editing and I use it a bit when I am ssh'd…
I'm also on the jetbrains train, but I stopped using it for a while because they're sluggish . An editor's interface should never lock up, an editor should never have popups that demand focus, etc but both intellij and vs code do this. At the moment I'm on VS Code again because Sublime Text isn't keeping up to date anymore (its ecosystem has mostly been dormant since 2014 or 2016) and Zed is still fully in developmen…
Does the author really not use any other vscode feature than lsp? What about e.g. gitlens or jupyter
Jupyter is harder, I haven't found anything that gets me there yet.
Helix and other new editors (kakoune comes to mind) always appealed to me because they seemed to have slightly more intuitive approaches to editing than vim, but I just don't think I can ever switch, purely because vim just exists everywhere I need it. It (or vi) is installed on practically every system I ever touch by default, and almost every IDE/editor under the sun supports vim keybinds either natively or via wel…
I do almost all my development on JetBrains IDEs (Rust, Python, Kotlin). IME they are unmatched for giving you code insights and suggested fixes (combined with "click here to do that") out of the box. But they are absolute resource hogs and I don't trust that they (or their best features) will always remain free. I've tried to get into neovim a few times. It's fine for basic editing and I use it a bit when I am ssh'd…
I've never experienced sluggishness, but, I also keep track of how much memory it's using and ensure I don't run low. It's clearly a huge resource hog, but I'm also glad for that. It's using all of my computers resources to analyze the code in amazing ways which help me develop fast. Emacs, Sublime Text, and others were all about typing speed. Fast development goes far beyond just typing speed.
Earlier quoted context omitted.
> avoiding RSI I tried all manner of keyboards over the years, and in my opinion, none of them solve RSI. I'm now back to a standard qwerty for the same reason as OP - they're just immediately available everywhere. What did help my no-longer-existent RSI was simple - I don't rest my wrists any more like I was taught in high school typing class (by an instructor that would whack our hands with a ruler if we were caugh…
Personally I started getting wrist pain 2 or 3 years ago. I have been using Colemak anyway for more than 15 years - my original reason for switching was because the German QWERTZ layout I grew up with is not very programming friendly, symbols like [] {}/\ are hidden away behind hard to type chords. I found as a nice side benefit that my typing speed increased by 20-30 or so WPM... I did also have typing classes in sc…
On a completely standard rectangular-block keyboard, I don't use pinkies to type. Actually, I do use my left pinky to hit left shift. But that's it.
Apparently DAP protocol support has been merged - but I find the documentation lacking, and afaik for typescript/javascript it won't work out of the box, as helix needs a pointers to the dap server (and that can't simply be in PATH)?
How are everyone debugging with Helix?