An open source model benefits everyone and can also be viable for mod developers

Sure, in the sense that you get fewer quality mods. Is that what you meant by “benefits everyone”?

Has no one here heard of jq?

If both sides have a shared data model

If the sides don’t have a common understanding of the data structure, no format under the sun will help.

Somehow none of this is a problem in sim racing, where plenty of paid mods exist just fine.

I’m ready for someone to try explaining how sim racing is totally unlike other games.

How comes paid mods work out fine in sim racing then?

Assetto Corsa has tons of paid mods, along with tons of free mods, and the game developer Kunos is one of very few profitable game devs in sim racing. Why haven’t paid mods ruined the modding scene and bankrupted the company?

In sim racing, Assetto Corsa has tons of paid mods, and simultaneously its developer is one of very few profitable companies. How come Kunos aren’t bankrupt from paid mods existing?

if you don’t defend your intellectual property you may lose it

Another day, another instance of someone confusing copyright with trademarks.

Sim racing is full of paid mods, and it’s working out fine. We acknowledge when someone puts effort into development, probably because majority of sim racers aren’t teens and have worked jobs.

Nah, specifically with this keyboard apparently the guy who designed it was reading mystical literature at the time, and put in a bunch of terms from that: from yoni, shakti and padme hum to ein soph and not-so-mystical fly agaric.

gcc is the most typical, works on the current line.

Iirc those buttons are full of nonsense and gags in the film, because until the bluray era no one could pause and read them.

Vim has a built-in tutorial on the motion commands and such. I don’t remember how it’s invoked, but probably something like :help tutorial. You’ll get an overview of the commands and see which ones might be useful to you right away. As I mentioned, I recommend getting the hang of them one or a few at a time, so they are incorporated in your toolbox.

Speaking of help, it’s generally useful in Vim to use :help {something} when you want to recall how something works. It has consistent naming for the help pages for various functionality, e.g. :help :s shows the page about the :s command, and there are pages for every motion command, etc. — I don’t remember the prefixes as it’s been a while since I used Vim proper, but just :help should give you an index.

Also, if you’re coding in Vim, there are ways to integrate documentation for your language, so that K would show help for the function or whatever under the cursor. Back in the day I’ve had PHP docs plugged into Vim, but it’s been a while, so idk how it’s done now. Iirc there are dumps of docs from the Dash app, which might be available as vimdocs.

It’s very easy to pick up. Out of the box, it’s just Evil, Ivy/Vertico, Org-mode, and several programming modes. The spacebar is likewise employed for many actions, but I don’t use most of them myself: just have about a dozen that I invoke regularly. The enabled modules (readymade configuration) and installed packages are specified in config files, and doom sync handles installing them.

It has some emacslisp helper functions/macros to add mappings, add hooks on modes, etc. — these are more convenient than those of raw Emacs.

I’m not sure why the author switched Doom to Vertico in the upcoming version 3, when Ivy was working fine. I’ve made some configuration tailored to Ivy, so enabled it back via the config file.

I found Doom to be a good middle-ground between raw Emacs+Evil and a complete overhaul of Spacemacs.

a couple of visual mode commands

Those might also work in the normal mode with motions, depending on the text. E.g. gcap would comment out the current paragraph (iirc).

I hope that you use the motion commands at least, because that’s the whole point of the separate modes. If not, you should look them up and add some of them to your workflow little by little.

The most basic ones are wand b to go a word forward or back; 0 and $ to go to the start or end of the line, or g0 and g$ for the visual line. f to jump to a particular letter forward. { and } to go to the start/end of the paragraph.

V is useful for selecting whole lines. ctrl-v for block selection (or ctrl-q, depending on your setup).

% can jump or select to the matching parenthesis or brace. With matchit installed, it also jumps to matching keywords like end or HTML tags.

gc comments out the selection (or uncomments it). Works with motions too, like gcc.

For pasting, you should use p in the normal mode. Also P pastes before the cursor. This is useful for moving text around by deleting it with something like daw, jumping elsewhere, and doing p.

And of course, the regex replacement with :s// is very useful if you have more than a few lines that need approximately the same change.

Pro tip: use Evil.

Another pro tip: if on Windows or Linux, remap alt to ctrl and win/menu to alt.

Org-mode, which is made for Emacs, has built-in spreadsheets.

Now every time I’m trying to do a ternary in Lua, I miss being able to just stick an if in there.

Look into Doom Emacs. It’s pretty cool in general, but especially if one is inclined towards Vim’s keybindings (which I recommend learning) and uses Org-mode.

tried jumping to the first line of my comment using C-a

That would work in MacOS (iirc), since most of app shortcuts there are on the cmd keys, and some Emacs/readline bindings work in text fields. Though C-a moves to the first character of the current line, not first line.