@b0rk I had decided to spend some time getting better with vim/neovim, and in the process I discovered #Helix. The Helix (& Kakoune) selection -> action model makes so much sense! That it's ready to roll without a bunch of configuration is a bonus.
The only thing I wish for is more interactive tutorial/practice apps (like vim-hero.com) for Helix.
I've been using the #HelixEditor as my main drivers for the better part of a year now and I couldn't be more happy with it. I've managed to get a near-IDE setup and experience thanks to zellij and some awesome TUI tools.
This article aligns well with my experience, I recommend reading it if you're "modal editor curious" or dissatisfied with you vim maintenance burden.
I'm pretty sure #HelixEditor is still clean
Getting really into #HelixEditor in no small part because it doesn’t push AI down your throat. And, you know, not software made by a huge, evil corporation.
@scy @gjherbiet Nice - the #HelixEditor equivalent bindings are move_visual_line_down and move_visual_line_up - much more intuitive with soft line wrapping enabled
I don't use Reddit, but I need to bring this here.
https://www.reddit.com/r/HelixEditor/comments/1koshhu/steel_plugin_pr_summary/
#HelixEditor #Steel
Compiled `ty` and `pyrefly`—one from `astro-rs` and the other from `Meta`. Both are Python type checkers and LSPs written in Rust. I’ve figured out how to integrate pyrefly with hx, but I haven’t done that for ty yet. ty is still in a very early stage, but pyrefly seems a bit more stable. It’s exciting to see competition between two outstanding open-source projects for Python type checking and LSP support. #rust #python #lsp #helixeditor
@b0rk I am absolutely not telling you what to do. I'm giving you a datapoint. I am a #Vim / #NeoVim expert. I have used Vim for ... hmm, maybe it's decades. Not sure. I use Vim key-bindings everywhere that I can. I have given talks and made YouTube videos about Vim.
I’m always trying new things. For instance, #RustLang. One thing I thought I'd try is the #HelixEditor. For a lot of people, and you may well be one, Vim/NeoVim is the right choice. If it is, I won't try to convert you. But my experience so far with Helix has been so positive, that even after decades of Vim being my favorite, it has been replaced by Helix.
I still use Vim wherever that's the right choice, for instance remote machines I don't control. But editing actual code in Helix using that language's LSP and with tree-sitter is absolutely delightful. Even the fact that Helix isn't a “finished” editor doesn't dissuade me.
At work, #Python is our main language, and we all have PyCharm. I use the Vim bindings via #IdeaVim. I prefer Helix even to that.
So there's your datapoint. Maybe someone you know well and trust has an opinion that sheds more light on the two editors.
My #HelixEditor config file is 5 lines of beautiful simplicity
@gedankenstuecke @Kroc Our cluster admin tolerated using VS Code, but people regularly ignored the guidelines and bogged down the head mode.
I never liked VS Code, and am still learning the ropes with #HelixEditor after years of using surface level emacs. The #MicroEditor is also nice (with better mouse support), but having built-in LSP support is great (this powered much of what appealed to me in VS Code).
Does anyone have any advice on where to start for learning c++? I already know Python and Rust really well. My motivation for wanting to learn C++ is to expand future career possibilities if things go south at my current job and I also generally enjoy learning.
I'm a big fan of #Linux and #HelixEditor and would want to use both. I'd like to know how to setup a basic project, how to select a compiler, how to add dependencies, how to setup modules, etc.
@stib Shouldn't it just work out of the box if your #LSP supports the `textDocument/documentColor` method as mention in the PR? I'm using #tailwindcss-language-server for #CSS and it does show the swatches in the completion picker w/out any extra config.
There's a dedicated LSP mentioned in the PR that displays the swatches right in the document buffer as well: https://github.com/q60/uwu_colors (haven't tried it).
if you are using Helix editor and from Emacs, Consider:
```
[keys.normal]
"C-space" = "select_mode"
C-y = "paste_clipboard_after"
[keys.select]
A-w = ["yank_to_clipboard", "exit_select_mode"]
```
#Emacs #HelixEditor
I've been using Helix editor for a few days. So far I'm enjoying it more than Neovim. Everything I need is already there. Even C++ debugging was quite easy to configure. Gonna trial run it next week at work.
It seems I haven't used #Emacs this week and have only been using the #Helix editor. I surprised myself a lot. #helixeditor
So it does look like the TypeScript language server has a limit of 4MB source size where it disables type checking (and actually shows an erroneous error stating that exports that exist in the file do not exist) for files that are imported but not open in the current workspace/session.
Still not sure if this is documented anywhere or not (haven’t been able to find it, if it is).
99.99999% of the time, unless you’re doing niche stuff like I am, you won’t run into this.
Workaround: should you have such a large file, e.g., with a large generated object, try and refactor to split it up into multiple files and rejoin it a separate file. The actual object size/memory usage isn’t the issue, it’s the file size.
Right, well, I can reproduce it with a simple example so I just filed a bug. Let’s see if it’s a known issue/limitation or what.
https://github.com/typescript-language-server/typescript-language-server/issues/951
Screen recording showing the issue:
I created a crib sheet for the #Helix text editor:
https://www.bobulous.org.uk/coding/Helix-crib-sheet.html
As usual I intended the new page to be compact and concise; and as usual it ended up being huge and rambling. Hopefully it'll still be of use to people who aren't fully familiar with the most useful keys and commands. (And just maybe of vague interest to #Neovim users who are thinking about trying Helix.)
Let me know if you spot anything incorrect.
Emacs `C-u 80 #`
Helix `i#<esc>79.`
