#helixeditor — Public Fediverse posts

Going all-in:

alias vi=hx
alias vim=hx
alias nvim=hx
export EDITOR=hx

https://helix-editor.com

#helixeditor #helix #nvim

There’s life beyond VSCode… thought I’d share my dev setup:

• Main monitor: WezTerm¹ running in a three (sometimes four)-way split with Helix Editor² as my main editor, a terminal pane for general commands while working, and Yazi³ usually running in another for working with files/directories in a project.

• Other monitor: Sublime Merge⁴ always running full-screen so I can immediately see exactly what I’ve changed (in real time) as I’m working.

Others (not shown): Browser(s) on a third screen and my laptop’s monitor as a fourth screen sometimes for other apps (read: distractions) :)

What’s yours like?

¹ https://wezterm.org
² https://helix-editor.com
³ https://github.com/sxyazi/yazi
⁴ https://www.sublimemerge.com

#myDevSetup #web #dev #WezTerm #HelixEditor #Yazi #SublimeMerge

There’s life beyond VSCode… thought I’d share my dev setup:

• Main monitor: WezTerm¹ running in a three (sometimes four)-way split with Helix Editor² as my main editor, a terminal pane for general commands while working, and Yazi³ usually running in another for working with files/directories in a project.

• Other monitor: Sublime Merge⁴ always running full-screen so I can immediately see exactly what I’ve changed (in real time) as I’m working.

Others (not shown): Browser(s) on a third screen and my laptop’s monitor as a fourth screen sometimes for other apps (read: distractions) :)

What’s yours like?

¹ https://wezterm.org
² https://helix-editor.com
³ https://github.com/sxyazi/yazi
⁴ https://www.sublimemerge.com

#myDevSetup #web #dev #WezTerm #HelixEditor #Yazi #SublimeMerge

There’s life beyond VSCode… thought I’d share my dev setup:

• Main monitor: WezTerm¹ running in a three (sometimes four)-way split with Helix Editor² as my main editor, a terminal pane for general commands while working, and Yazi³ usually running in another for working with files/directories in a project.

• Other monitor: Sublime Merge⁴ always running full-screen so I can immediately see exactly what I’ve changed (in real time) as I’m working.

Others (not shown): Browser(s) on a third screen and my laptop’s monitor as a fourth screen sometimes for other apps (read: distractions) :)

What’s yours like?

¹ https://wezterm.org
² https://helix-editor.com
³ https://github.com/sxyazi/yazi
⁴ https://www.sublimemerge.com

#myDevSetup #web #dev #WezTerm #HelixEditor #Yazi #SublimeMerge

There’s life beyond VSCode… thought I’d share my dev setup:

• Main monitor: WezTerm¹ running in a three (sometimes four)-way split with Helix Editor² as my main editor, a terminal pane for general commands while working, and Yazi³ usually running in another for working with files/directories in a project.

• Other monitor: Sublime Merge⁴ always running full-screen so I can immediately see exactly what I’ve changed (in real time) as I’m working.

Others (not shown): Browser(s) on a third screen and my laptop’s monitor as a fourth screen sometimes for other apps (read: distractions) :)

What’s yours like?

¹ https://wezterm.org
² https://helix-editor.com
³ https://github.com/sxyazi/yazi
⁴ https://www.sublimemerge.com

#myDevSetup #web #dev #WezTerm #HelixEditor #Yazi #SublimeMerge

There’s life beyond VSCode… thought I’d share my dev setup:

• Main monitor: WezTerm¹ running in a three (sometimes four)-way split with Helix Editor² as my main editor, a terminal pane for general commands while working, and Yazi³ usually running in another for working with files/directories in a project.

• Other monitor: Sublime Merge⁴ always running full-screen so I can immediately see exactly what I’ve changed (in real time) as I’m working.

Others (not shown): Browser(s) on a third screen and my laptop’s monitor as a fourth screen sometimes for other apps (read: distractions) :)

What’s yours like?

¹ https://wezterm.org
² https://helix-editor.com
³ https://github.com/sxyazi/yazi
⁴ https://www.sublimemerge.com

#myDevSetup #web #dev #WezTerm #HelixEditor #Yazi #SublimeMerge

Thanks to a work-in-progress Homebrew cask by Andi Péter (https://codeberg.org/GramEditor/gram/issues/15#issuecomment-11159294), I was just able to quickly install and play with the new Gram code editor (https://codeberg.org/GramEditor/gram#gram) – a fork of Zed with all the bullshit (AI, telemetry, etc.) removed that looks like it could be great editor to recommend both for people just learning to code (as I was, recently, to recommend for people learning Kitten¹) as well as seasoned programmers who don’t want to work in terminal.

And, as a bonus, it actually has a Helix Editor mode so if that’s your daily driver (raises hand), you can just use it like Helix (i.e., Helix Editor in a graphical shell).

If you want to try Andi’s build (only works on Mac at the moment and remember, you have to trust Andi):

brew tap petrosz007/gram-tap https://codeberg.org/Petrosz007/homebrew-gram-tap.git
brew install --cask gram

PS. You can follow the author of Gram, @krig, on the fediverse :)

¹ https://kitten.small-web.org

#gram #editor #gramEditor #programming #coding #dev #zed #zedEditor #helix #helixEditor #brew #macOS #noAI #privacyRespecting #tool

#RedoxOS: “Sergey Reshetnikov fixed and updated the #HelixEditor which was not working for some time.”

https://www.redox-os.org/news/this-month-260228/

@ctietze @nikitonsky I've switched to the Alabaster themes a few weeks ago, too. The comments being more prominent is one of the reasons I've stuck with it. #alabaster #HelixEditor

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).

My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.

Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/

My port of the Alabaster theme (family) for Helix was approved, merged to `main`, further modified as per requests, and modifications merged to `main`, too.

The time from creating the PRs to having them merged was really short. Now how long it takes to get from `main` into an actual **release**, that I don’t know.

My original repo (just the theme family) lives at https://github.com/wolf/alabaster-for-helix. The `README` there has screenshots; points to the works of Alabaster’s creator (Nikita Prokopov, “tonsky”), which includes the original themes, repo, and an article that explains it all.

I use this theme all the time and will continue to maintain it. I see further suggestions in Issues on my repo. I take suggestions, issues, and PRs seriously.

#HelixEditor #OpenSource #Themes #Alabaster

Published my port of the Alabaster theme family for Helix.

Alabaster is a minimal syntax highlighting approach by Nikita Prokopov (tonsky) - only 4 semantic colors: strings, constants, comments, and definitions. Everything else stays plain text because code structure is already clear from formatting.

I've ported all 6 variants (light/dark × standard/BG/mono) from the original Sublime theme (staying as close as possible to the original). Also submitted a PR to ship these with Helix upstream!

Original theme: https://github.com/tonsky/sublime-scheme-alabaster
Read tonsky's essay: https://tonsky.me/blog/syntax-highlighting/
My port: https://github.com/wolf/alabaster-for-helix

I tried to duplicate the original exactly, however Helix has multiple selections so I made the colors distinct between "selection" and "primary-selection".

#HelixEditor #Helix #Alabaster #MinimalDesign #SyntaxHighlighting #TextEditor #Rust

I wrote up how I set up #ty with #helix, with a focus on finding third-party packages (a.k.a. virtualenvs, which I keep on a central location!)

https://blog.lanzani.nl/2026/using-ty-with-the-helix-editor/

#HelixEditor #python

Just shared my WezTerm¹ configuration. It’s not very long and mostly just adds a few keyboard shortcuts that I find more ergonomically-pleasing, specifies light/dark themes and improves colour scheme consistency and also, if you use Helix Editor², automatically implements light/dark mode theme changes for it in line with the rest of the terminal.

https://codeberg.org/aral/gists/src/branch/main/wezterm.lua.md

¹ https://wezterm.org
² https://helix-editor.com

#dev #terminal #WezTerm #HelixEditor #config #configuration #dotFiles #gist

Working on #AdventOfCode. My plan was to solve each day in both #Python and #RustLang. I thought I would be further by now. Yes, my Python answer to day 1 solves both parts, but I'm trying to be exemplary: good names, docstrings, comments-where-needed, tests, project structure, all the things.

For some reason, #HelixEditor keeps complaining about the #LSP (using both #Pyrefly and #Ruff, as usual). I'm concerned I haven't set things up right somehow, but I don't yet see where I've gone wrong.

Once this is working, further days will be easy. At least ... I hope!

@etiennebacher Jarl is working as an R linter in #HelixEditor now, thank you! https://jarl.etiennebacher.com/editors#helix #RLang

Beginner-friendly, unofficial documentation for Helix text editor

https://helix-editor.vercel.app/start-here/basics/

#HackerNews #BeginnerFriendly #HelixEditor #Documentation #OpenSource #TextEditor #LearningResources

This was going to be a question for the Fediverse: I use the #HelixEditor. I use a light-colored #Theme (dark foreground text on a lighter background; yes, I know that puts me in a narrow group). Currently, I use #Onelight, but with some tiny modifications (https://github.com/wolf/dotfiles/blob/main/helix/dot-config/helix/themes/onelight-fixed-bufferline.toml) to make buffer-line "tabs" look right.

Reading this (https://tonsky.me/blog/syntax-highlighting/ by Nikita Prokopov aka Tonsky, sorry couldn’t find a Mastodon address) article makes me feel like there could be something better.

I wanted a light colored theme like his but made for Helix (his theme is called "#Alabaster"). I was having trouble finding the right thing, but looked harder and found this: https://github.com/beebeeep/helix-alabaster. Maybe **that’s** the right thing. I’ll try and report back.

If anyone out there has suggestions, please reply!

#Atuin update: I've come to rely on it. It's a must have for my daily shell usage. Works great everywhere ... except on #GitBashForWindows. Lots of problems there. Here's how I solved them:

* Install `ble.sh`. Use `curl` to do this. Do not get it with Git. Do not attempt to build from source.
* Install by sourcing `ble.sh` at the **end** of your `.bashrc`. That's how the instructions about getting it with `curl` tell you to do it. The Git based instructions want you to say something different in your `.bashrc`. You want the `curl` instructions.
* In my install, #Ble was too slow out-of-the-box. Missed keystrokes, etc. I copied the `blerc.template` from the GitHub repo to a local `~/.blerc`, and edited it to disable almost every kind of completion and also syntax highlighting. Speed is now acceptable. (Might be that my #Windows box is too slow. That seems unlikely.)
* I use `vi` mode; #Vim. `ble.sh` picks that up from my `.inputrc`; #Readline. I use #Starship for my prompt. I had to disable in `.blerc` the showing of my current `vi` state (insert, visual, command, etc) and also edit `.inputrc` to not add characters to the prompt to show insert vs command mode. Those changes let me have my normal `starship` prompt.

I do have one problem remaining. It's not related to `atuin`; it's related to the command line itself. In #Bash and #Zsh, it's easy for me to be on the command line and get what I've typed so far directly into my editor; #HelixEditor. Usually something like Esc-v or the like. `ble.sh` doesn't seem to have a way to do that, but maybe I just haven't found it yet.

Yes. I use #LightMode. Everywhere (just about). I know I'm in a minority. And light mode is often broken for things (like when using light mode in the #HelixEditor, the buffer tabs are wrong and deceptive).

For terminal windows that are ssh'd into some remote box _sometimes_ I'll use dark mode.

I work in three different platforms: #GitBashForWindows (mostly, because that’s the environment for my job), #macOS, and #Linux. My shell environment is pretty complex, and as #CrossPlatform a I can make it. The most annoying thing I have to handle in my scripts is the difference between paths on a Windows system vs anywhere else, and especially the leaky magic Git Bash for Windows employs to deal with it (that’s the main thing I want to communicate in this post).

I’m a very experienced #Bash user/programmer, but more and more I find myself converting Bash scripts to #Python.

These days my Python scripts are run via a #uv shebang line, which I love. uv creates an environment to run such a script. That environment is not active while I’m _editing_ the script (using #HelixEditor) so, Helix reports all the symbols that it could only have gotten from that venv. I don’t yet know of a non-brute-force way to fix that (that is the second thing I wanted to communicate in this post).

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.

https://github.com/typescript-language-server/typescript-language-server/issues/951#issuecomment-2786000876

#TypeScript #max #lines #memory #constant #object #import #bug #issue #LSP #languageServer #HelixEditor #VSCode #JavaScript #microsoft #workaround

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:

https://vimeo.com/1073284447?share=copy#t=0

#TypeScript #max #lines #memory #constant #object #import #bug #issue #LSP #languageServer #HelixEditor #VSCode #JavaScript #microsoft

#Vim #NeoVim has #Surround plugin. #HelixEditor has it built in. The Helix version doesn’t do "surround with function". I started a discussion on the Helix Discussion board, but privately forked and cloned and started experimenting. Just when I finally got a response in the discussion, I finally had close to a working prototype.

https://github.com/helix-editor/helix/discussions/13179

The response showed the keystrokes to do it in Helix as it is now, and they were reasonable. Using Nik Revenco’s way was a better match for Helix’ "vision" as expressed in their Vision.md doc.

I learned a lot from prototyping a command (in #RustLang #Rust) within Helix (in particular, how to make a prompt in the editor and get a string from the user was a big thing for me), but I ended up throwing it away. I was wrong.

I’m really starting to like Helix, but like Rust, I have so much to learn. Still experimenting, still learning for both.

I see #HelixEditor is getting a built-in language (eventually, I don’t know when, and I don’t have links to information about it). The language will be a #Scheme called Steel. Steel is inspired by #RacketLang and written in Rust. I’ve written small programs in Racket and don’t much like it. I find them hard to understand when I come back to them later. Probably that’s just lack of experience. Adding a built-in language is a really good thing. Picking a Scheme is almost certainly a great choice, despite my feelings. If I do settle on Helix and if I do end up scripting it, maybe I’ll end up liking Scheme more. As far as I’m concerned, this addition to Helix can’t come soon enough.

Oh another pluginmanager for #neovim has bitten the dust, and I totally not noticed. #packer #nvim
I finally want to get rid of this bullshit and use #HelixEditor everywhere...looking at you #Debian

and finally, this is very much a kakoune thing, but i don't think selection and navigation should be different things. and more so when im working with blocks of syntax. i'm not working with characters, no do i think in characters. i think in expressions or statements or identifiers or literals.

this is very much a personal opinion, but there's so much room for improvement in this field, i don't see how we've been more or less stagnant for so long. i don't want to use a lisp just so i can use paredit. i want paredit in every language i use.

and doubly finally, you're welcome for me hashtagging every single post in this thread/rant entirely differently. if you're following any of them, you get randomly exposed to some subsection of my thread, without any of the previous parts.

#kakoune #helixeditor #structuralediting #textediting

@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 😉

@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 😉

@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 😉

@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 😉

@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 😉

I have been playing around with #HelixEditor a bit. On hand1, I like it quite a bit, with the simplicity of configuration yet still being quite feature rich. But on hand2, I've gotten so used to my #Neovim setup that I don't think I want to break my old habits.

Once you get Neovim setup, it's not bad. Of course a little work here and there if plugins have breaking updates, but that doesn't seem to be too frequent.

Just learned #Packer has stopped development. Time to switch to #Lazy now.

A question for the #editor nerds using #HelixEditor #vim #emacs or gui editors as #geanyide. Is it technically possible to set code highlighting to bold, it, font sizes, etc. I am asking because a young family member is probably totally colour blind (as in can only see levels of grey).

Hi all :) I create/update some #slackbuilds for #slackware-current

#HelixEditor
#procs
#alacritty

The repo have the link for the pre-build packages.

Let me know if you find any issue.

PS: I will try to compile some of then in Slackware15 but the main focus is the current/next-version.

https://github.com/r1w1s1/slackbuilds/tree/main

@gregorni

Editor: #HelixEditor #KateEditor
Terminal emulator: KDE Konsole
Shell: #bash (GNU Bourne‐Again SHell)
Linux Desktop: KDE Plasma 5 on #slackware current
Langs: #bash :)
Containerization: #docker
SCM: #git

@codemonkeymike it gives you a modern #vim experience out of the box and sane defaults, without feeling bloated. Reminds me a bit of #doomemacs .
Also using #lua instead of relying on #vimscript was a good decision from the #neovim devs, IMO.

Definitely not as easy to configure as #HelixEditor , but an improvement over configuring vanilla neovim from scratch.

#Nushell and #HelixEditor connected via #LanguageServerProtocol a.k.a. #LSP

My pull request got merged, now you get diagnostics with each keystroke.

This week I’ve discovered the power of tmux, especially when paired with ssh. Being able to use the pose of my M1 Mac mini on my ancient laptop without any config or set up or even needing to git push is amazing.

Some of my favourite tools in the terminal:
🧬 Helix as my editor.
🛌 Lazygit for git.
🗄️ Broot for file managing.
🐈‍⬛ Catppuccin themes.

#AppDev #OpenSource #tmux #HelixEditor #lazygit #broot #catppuccin

Mit dem #helixeditor scheint man gut ( #python )-Programmieren zu können.
#Autocompletion ist einfach einzustellen und der run-shell-command zum Ausführen eines Python-Skripts, gibt die Shell-Ausgaben an ein Popup weiter. Weiß nicht, wie das bei einem anderen #editor gelöst ist, aber find ich hier gut gemacht.
Werd ich versuchen #neovim + #tmux zu ersetzen.

#hx