It doesn’t have to know, just to assume 😛

and I bet it assumes that most puny humans are irrational and unintelligent compared to itself 😛

I haven’t really spent more than 2 minutes on it, but the effort that went into making that Amiga aesthetic is just awesome.

This is helpful from an emacs/evil perspective https://github.com/noctuid/evil-guide

thx!

And this series was recommended to me by a vim user https://thevaluable.dev/vim-commands-beginner/

and a big vim cheatsheet list http://micronerds.org/vim/

thx again again

Once you’re past the initial stuff (or maybe even before), https://pragprog.com/titles/dnvim2/practical-vim-second-edition/ is great at demonstrating how to get value out of your daily vim editing.

Very beginner friendly (just friendly in general 🙂 )

beware, though: once you get hooked on it it can be hard to use things without it!!

I keep hearing about how fast and good neovim is...

I've got about 25 years of building up muscles in my emacs pinky. This might be a lot for me to take on. I still struggle a bit with how it is different from doing something like hydra in emacs

but I've got someone I need to do remote pairing with and @U07FP7QJ0 seems to think it works so 🤷

the big difference from what I've seen (over the years) is that vi(m) is something you use, emacs is a place where you live

in vim, you live in the unix terminal, in emacs you live in your emacs environment, you just happen to edit code there as well

but I wonder if this might be the peanut butter and chocolate of working with text

neovim has bindings for JS... I might be able to script it using SCI... noooo, please don't convince me

I need to make sure that org-roam continues to work for me. My emacs env is at a low point w/what I'm doing atm

what bindings are you talking about, @U04V15CAJ? 😮

I switched to neovim recent(ish)ly, but I haven’t really used any features that are not within the vim/neovim venn diagram overlap

It has native support for LSP and lua but also RPC support for Node.Js, python, etc, @U7ERLH6JX told me

https://github.com/neovim/node-client

We can also get lispy scripting on nvim via https://fennel-lang.org/ 😄

are you referring to this @U0525KG62? http://devblog.arnebrasseur.net/2014-08-amazing-lisp-vim

• http://yannesposito.com/Scratch/en/blog/Learn-Vim-Progressively/ • https://www.openvim.com/tutorial.html

Here's my quite skewed towards clojure nvim setup if anyones interested: https://github.com/lispyclouds/dotfiles

My vim config is here 😉 https://github.com/lambdaisland/corgi

@U07FP7QJ0 I'm going to give corgi a try. Mostly to help with remote pairing.

That's really great to hear. Don't hesitate to poke me or open issues!

@U07FP7QJ0 will do. Are you using tmate or something else for shared environments?

tmux, and some internal tooling to spin up an environment in the cloud and give everyone SSH access based on their github keys

which cloud are you spinning things up in?

Can also recommend Mosh and https://github.com/StanfordSNR/guardian-agent

in our case it's with Exoscale (swiss cloud provider). We work with them because they're a Clojure shop, they're people we know, and they sponsor ClojureVerser/Clojurians log with cloud credits

To be honest it's not used as much as I had hoped, still trying to get the team to adopt more pairing practices

I feel like what I want to do is be able to spin up something like docker or some other chroot'd environment to share

yeah, pairing can be tricky

That should be doable too. We like to have it in the cloud because it's symmetrical, nobody has more priviliged access etc. It also means any person can continue or resume the project regardless of who else is around

I've even used it solo, it's really nice to come back to a project after a week and your Emacs and REPL and shells are still exactly as you left them

@U0525KG62 Here is my little Evil guide and useful links for learning / practicing Evil. https://practical.li/spacemacs/spacemacs-basics/evil/ There are a few things Spacemacs specific, but its 95% evil 🙂 I have usually just searched t'internet when I wanted to know how to do something, then just used it a lot until it sticks. Learning https://practical.li/spacemacs/spacemacs-basics/vim-style/speaking-evil.html is something that made a big improvement to my learning. Curiously, I've never needed to use the vim style : command in Evil, so suggest that bit can be ignored. I just haven't needed : commands with the nice set of tools I have in Emacs & Evil that help me wrangle text.

Although I did find : and a number to jump to a specific line number in code useful when pairing

Learning a bit of ed(1) can help people appreciate the ed/ex prompt (:) https://lambdaisland.com/episodes/ultimate-dev-setup

I didn't read "evil mode" literally, initially. "Practical Vim" is probably not evil-compatible.

Or maybe it is! I used spacemacs for a while and was annoyed with some stuff that I was missing from vim, but I don't remember what, exactly.