That's actually what Idiot Flesh did in the 90s. They had one show where the band outnumbered the crowd, so they had the crowd gather in the middle of the venue and they played the show around them.
"The Civil War was about states' rights!"
Yes. States' rights to own slaves.
Who could have predicted this outcome from a failed Fox personality?
I do. Supply and demand. Supply hasn't caught up.
Yeah. I just use Emacs for coding.
I love the graphic. It is now the wallpaper on my laptop.
He's right. It's just another tool in the hands of a skilled technician. The upgrade from a hammer to a nailgun didn't suddenly make everyone a master carpenter, but in the hands of some that knows how to use it, it can greatly increase productivity. We are in the very early stages of AI, and we are working out the details. While it's not a great comparison, I remember when Windows 95 launched and, when you could find RAM, it was literally worth more than its weight in gold. Small shops had to keep it in a safe. This was because Windows 95 needed at least 8MB ( <- not a typo) of 30 pin SIMM RAM to run well. A couple years later and people were putting them on their keychains as a joke.
Or the minutes that I get in early. Or take a short lunch.
This isn't exactly a fix, but it keeps me from accidentally locking up my terminal and potentially losing work
map('i', '', 'gj', {})
map('i', '', 'gk', {})
map('i', '', '', {})
map('i', '', '', {})
map('n', '', 'j', {})
map('n', '', 'k', {})
map('n', '', 'l', {})
map('n', '', 'h', {})
Now if I forget to leave Insert Mode, the cursor just moves to the left, and C-H in Normal Mode still works as expected.
p.s. I commented the key_bindings in alacritty.yml
I think I'm on the trail. According to this post on Reddit, some terminal emulators have trouble passing the correct codes to terminal apps like Neovim. I did manage to break C-H completely, but that's not really helpful. By adding the following keybinds to alacritty.yml, I'm getting Neovim to behave differently, but not as expected.
key_bindings:
- { key: F6, mods: Shift, chars: "\x1b[17~;1u" }
- { key: H, mods: Control, chars: "\x1b[72;4u"}
The first one for S-F6, gets Neovim to recognize the 'F6' part, but does not behave any differently than if I just pressed 'F6' without the modifier. But, without this key binding in alacritty.yml, Neovim doesn't react to Shift+F6 at all.
The second entry, if I'm in Insert Mode in Neovim, causes Neovim to switch to Normal Mode and go to the top of the buffer. In normal mode, it just goes to the top of the buffer instead of the defined behavior of moving to the pane to the left of the current pane.
So, I've basically managed to get a "different error", but not solve the problem. Any ideas?
I'd like to figure out that mapping. I do this all the time. I forget I'm in insert mode, try to move the curser with 'j' and just end up typing a bunch of j's that I have to delete.
holy shit that guy is twisted af.