The new tree-house injection support in #HelixEditor 25.07 is awesome (correct syntax highlighting for nested languages, e.g. rust code in a markdown code block in a rustdoc comment)
I've been using the #HelixEditor as my daily driver 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 your (neo)vim config maintenance burden.
@mattwilcox I switched to #HelixEditor a few months ago. Motions are superior (and easier to learn) compared to Vim in my opinion. Also, no need for plugins for many things like tree-sitter or LSP support.
Not sure of best process practices for #coding. I can't help but copying files over and over until I've got the code I want, then I come up with some new file structure to name it... and start all over again.
#HelixEditor (and #tmux is helping with split screens, file pickers, scratch buffers and whatnot, but sheesh I'm all over the place.
I'm guessing there is a lot that comes with experience. Maybe using git to its capabilities can assist. Maybe some written word as a side note helps. I used to use Jupyter but even that got to be a convoluted mess.
I'm certainly writing a lot more since my sporadic attempts when working in GIS, so maybe it's just that I'm starting to think about this more now.
Please send me some of your favourite tips!
I'm pretty sure #HelixEditor is still clean
This is a great little tutorial for searching in the #HelixEditor https://helix-editor-tutorials.com/tutorials/using-helix-global-search/
#editor #coding
@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
@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.
Is there a good/accepted way to get #HelixEditor pull requests flagged for review? Lots of comments would be bad. Lots of thumbs up?
eg https://github.com/helix-editor/helix/pull/12514 for mouse double-click to select word, triple-click to select line
@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.
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:
This week hell froze over:
After being part of the 'Ctrl+b,Ctrl+n,Ctrl+p,Ctrl+f' club for about 18 years I joined the 'hjkl' club by switching over to Helix as my daily driver editor.
OMG, #HelixEditor def has some amazing new updates..
Global search is just perfect now.. thank you! So glad I support this project
I’m thinking of switching to #HelixEditor, how is the experience for other Rust developers out there? Is there something missing?
Trying out two terminal editors (#HelixEditor and #MicroEditor), and starting to work out what I like best in each that is missing from the other, e.g. helix mouse support is lagging https://github.com/helix-editor/helix/issues/12500 while micro’s Python syntax support doesn’t handle f-strings yet https://github.com/zyedidia/micro/issues/3605
@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration