![]() ![]() I didn't know I needed a multicursor before I had tried Kakoune and I would highly suggest anyone to try Kakoune just for the multicursor experience. ![]() I've used Kakoune for over a year now and I haven't had need for macros except for maybe 2 times. It makes it so easy to select text.įinally multicursor, it's so good. I think one of the best things Kakoune has to offer is that selection mode (visual mode in Vim) is always accessible through so if I want to select some random number of characters going left, I'll just hold L, or if I want to select all characters until the end of line I'll just press GL whereas gl takes me to the end of line. So for example in Vim you may accidentally select too many characters to delete and then you need to redo the command whereas in Kakoune you can adjust the selection before executing the action. It switches from "action selection" to "selection action" which allows you to first select the thing you want to operate on and only then specify what you want do with it. When I want to rewrite a string in vim, I unconsciously type `ci"` it would take me a long time with Helix to regain that level of fluency. the verb/object syntax is reversed in Helix `dw` in vim is `wd` in Helix. There are some very fundamental differences, e.g. I took a look at the Helix documentation, and while it’s definitely “vim inspired,” it’s different enough that I would have to rewire years of muscle memory to be as productive as I am in vim. Still using vim at $WORK for a variety of reasons (giant c++ codebase that does not easily plug in to clangd/LSP), but I might be doing the switch soon.ĭo you have some supernatural ability to quickly (re)learn muscle memory for new keybindings? I’d consider myself a fairly advanced vim user, and it took me literally a couple years to get to the point of fluently using complex navigation/editing commands. >I've used Helix for all my recreational programming projects (in Rust) for about 6 months and I've written about 10kLOC of code with it. Thanks to everyone working on the project. It's still rough around the edges, but good enough for a daily driver. But I haven't had a need to add any kind of plugin, and it's easy enough to fork a shell for an external process if needed. Lots of people are requesting a plugin extension system, which is kinda understandable since every editor seems to have one. opening a Makefile in Vim triggers a ftplugin script that messes editor-global config instead of buffer-local, with the default out of the box scripts). I particularly like the fact that all the important features are built-in and not half baked scripts with unintended side effects (e.g. I had very little friction coming from Vim and a little bit of Kakoune. My Helix config file is about 5 lines long, but my Vim config is in the hundreds of lines. Hint: use `hx -health` to check that all the tools are properly installed and configured (it shows a matrix of programming languages and their associated tooling, with red/green check marks). Plugging in rust-analyzer still needed a line or two of config file editing, but that should not be necessary for very long. Installation was easy and the default configuration is good. Still using vim at $WORK for a variety of reasons (giant c++ codebase that does not easily plug in to clangd/LSP), but I might be doing the switch soon. It also supports similar integration with shell scripts and any other Unix scripting language.I've used Helix for all my recreational programming projects (in Rust) for about 6 months and I've written about 10kLOC of code with it. It’s also fully scriptable with Applescript, and works directly with the native Perl, Python, and Ruby environments provided by Mac OS X. Questions can be answered in BBEdit’s Help Book or the extensive manual (both available under the BBEdit Help menu), by sending email to (they answer all their emails!), and you can even get helpful pointers on Twitter at are some of the built-in text processing actions that BBEdit can do natively (many allow grep matching): ![]() In addition, dozens more languages are supported in Codeless Language Modules which are enumerated both on this site and on the official Bare Bones web site.īBEdit’s customer support is legendary. The languages BBEdit supports natively include: ![]() BBEdit is a text editor with lots of features that make it ideal for editing any sort of code, words, or even web pages. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |