typos VS helix

There is typos though that takes a bit different of an approach to spell checking. When the default is to ask the user (like in a text editor), a regular spell checker is likely better. typos is more meant for being run in an automated fashion.

I recommend you run https://github.com/crate-ci/typos

Oh yeah, I can see you short hashes being a problem. The challenge has been finding the right heuristic for them

Is there good usage examples for this tool? typos simply traverses directories on invocation, wonder if there's a static analysis equivalent for ltrs.

highly recommend adding https://github.com/crate-ci/typos to your CI...very easy to add to a github action, catch fun spelling errors even in camelCased and snake_cased variable names...catch em before they become public facing APIs

I like to use https://github.com/crate-ci/typos as a command-line option. It's built to run as a service or in CI... I run it in our code review software and it has been a big hit.

there's a little comparison table here https://github.com/crate-ci/typos/blob/master/docs/comparison.md

typos

Nice post. Obligatory Helix plug: For anyone interested in taking this further, there are whole editors designed around multi-cursor editing.

https://helix-editor.com/

I could never turn it off completely but I do sometimes use the Acme theme during the day (it's too bright in the evening), which highlights just comments, strings, and errors.

https://github.com/helix-editor/helix/wiki/Themes#acme

You can use a snippet LSP to work around Helix not having a built-in LSP manager. They're listed in https://github.com/helix-editor/helix/issues/395

I'm probably not the average python programmer.

But I normally just create two terminals (I have a tiling window manager) and in one I open a python file under /tmp/ write my code and execute it in the other terminal.

I would probably use a REPL if it was integrated in my favorite editor ( https://helix-editor.com ).

Wow, that's been there a while: https://github.com/helix-editor/helix/commit/35c974c9c49f912...

Wonder how I missed that. I'm getting a re-education in helix today -- thank you! I'll go through `hx --tutor` again before I insert any more feet in my mouth.

Interesting to see how they are gonna approach integrating plugins/extensions system, because this is likely gonna be one of the major factors affecting adoption and ecosystem growth.

Helix devs, for instance, lean towards a Scheme-like implementation. [1]

[1]: https://github.com/helix-editor/helix/discussions/3806#discu...