-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
coc.nvim
Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
regex
An implementation of regular expressions for Rust. This implementation uses finite automata and guarantees linear time matching on all inputs.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
FYI I didn't see Windows support listed on the installation page (https://docs.helix-editor.com/), but it seems to be available on the releases (https://github.com/helix-editor/helix/releases)
The one page you should add to the documentation is "differences from Vim".
For example, https://github.com/purescript/documentation/blob/master/lang... makes picking up PureScript as a Haskell programmer much easier than having to read all of the documentation and do the diff yourself.
There is multiple cursor[1]. Checkout the video my emacsrocks[2]. You can combine that with regex tools if you need to do this over complex patterns[3]. There is also iedit may fit your mental model better[4].
[1] https://github.com/magnars/multiple-cursors.el
Vim has supported jump to definition via `ctags` for decades, works great for Ruby. Here's a tutorial from ThoughtBot (https://thoughtbot.com/upcase/videos/intelligent-navigation-...).
Vim also supports the same LSP implementations that VSCode uses via Coc.nvim (https://github.com/neoclide/coc.nvim), which provides the same code navigation features that VSCode has, including jump to definition.
Onivim 2 is getting there. Version 0.5.5 was released two months ago, 0.6 would be worth taking a look at https://v2.onivim.io/#timeline
It's a main contender for me to replace VSCode, whereas this one doesn't look that enticing. I want a terminal in my editor, not editor in my terminal, had enough of that
> I'd like to have an analogue to jump back with my C-x stuff like I do with M-. and M-, - any emacs people have suggestions on how to do that?
If you use Xref UI for "Find References/Implementations/Type", M-, should work in those cases too.
There is a more general question: how to "jump forward" again, without re-invoking the previous navigation command with the exact arguments. IDEA, already mentioned in comments, has key bindings for that.
There are several third-party packages which attempt to solve it as well. I'm using this one:
https://github.com/tcw165/history
You can also add "jump back" to your other navigation commands, even if they don't use the Xref UI.
Just this morning I upgraded to NeoVim 0.5 and set up TreeSitter and LSP with Lunar. I haven't had much time to play with it today, but it's looking good so far. https://github.com/ChristianChiarulli/LunarVim
It seems the biggest issue with ropes is search. The rust regex engine (which this editor uses) expects an array. In the worst case scenario you forced to copy the entire document into an array to run search on it. Only to throw that away when you are done. That offsets a lot of performance gains ropes are supposed to provide.
https://github.com/xi-editor/xi-editor/issues/1192#issuecomm...
Yeah, the search implementation right now is kind of thrown in there just to get out of the way of my editing.
There's a way to search through rope chunks by using the low level regex-automata: https://github.com/rust-lang/regex/issues/425#issuecomment-7...
Alacritty currently does that to search over it's cells, I'd like to look into it.
I'd say that pointing is inherently slow because it involves checking where the cursor is, where the target is, moving it in that direction, then stopping at the right time. With a typical keyboard-based browser interface clicking the update button would have been a 2 combination.
Check demo animation on Saka Key's readme: https://github.com/lusakasa/saka-key
Sure, I have two QMK keyboards right here: https://github.com/archseer/keys
I consider key remapping orthogonal though, as TeddyDD has stated, there's more to modal editors than just convenient shortcuts.
Wasm started in the web, but has since been ported even to the Linux kernel [0]. It seems perfect for situation where you near machine code levels of performance, but don't want to carry different binaries for different CPU architectures - exactly what you want from a plugin system. It also allows far greater isolation than "real" compiled code.
[0] https://github.com/wasmerio/kernel-wasm
I really like the way kakoune (https://github.com/mawww/kakoune) handles it, the editor doesn't have any scripting as such, it has an "API" that can be used by shell scripts or tools written in any language. Unix is the IDE.
I just could never get my head around the key bindings with kak.