That said there's something absolutely defiling about this. It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie.
I love that it will make VIM more accessible for more people, but I hate how they do it. Kudos to the author.
That said there's something absolutely defiling about this. It's like installing a V8 in a Tesla, or replacing the pumpkin in pumpkin pie.
I love that it will make VIM more accessible for more people, but I hate how they do it. Kudos to the author.
Most pumpkin pies are actually made with butternut squash and other similar squashes, not pumpkin.
https://en.wikipedia.org/wiki/Cucurbita_moschata
https://www.thekitchn.com/whats-actually-in-your-canned-pump...
Some pumpkin, blended into a paste, some brown sugar, an egg or two, some heavy cream and some cinnamon and crushed cloves and you have your pie filling.
Try with pumpkin, nutmeg, cinnamon, and cloves… it’s that old timer pumpkin pie taste.
In the UK and EU, coffee cake is cake with coffee.
Likewise tea cakes in the US are cakes made with tea and tea cakes in UK and EU are cakes to have with tea. So…
Not a lie, just a Spider-Man meets Spider-Man moment when you learn you can actually make coffee cakes with coffee (or espresso) and you can make tea cakes with tea (I prefer oolong).
This "tradition" of using Butternut Squash instead goes back to the 1930s at least.
In the southeast coast of US, if you make a “pumpkin pie” with squash, you won’t be invited back next year.
(Chalk and sugar in the same sentence just made me think of Macdonald's milk shakes.)
No you weren't. To use your style, if YOU want to play along and be pedantic, then your edit wasn't about North America, it was about just the U.S. and Canada.
As Wikipedia notes:
>The term [pumpkin] is most commonly applied to round, orange-colored squash varieties, though it does not possess a scientific definition and may be used in reference to many different squashes of varied appearance.
If the article is simply intending to say that it does not usually come from squashes that are orange, oblate and ridged, then that's fair. But I don't think it's mostly butternut squash, and I don't see why manufacturers would try to hide using the most popular variety of squash.
Interestingly, I expected them to go easy on pretty much anything
https://www.snopes.com/fact-check/canned-pumpkin-isnt-actual...
[I'll just add one more note, not mentioned in the article, which is that typical Jack-o'-lantern pumpkins are quite awful for cooking. Much worse than any canned pumpkin. If you want to cook with fresh pumpkin, research the varietals that are known for good texture and flavor. Don't grab a carving pumpkin from the pile.]
Ugh, they really are much less aesthetic than a nice plump orange one. This feels similar to the childhood realization that regardless of the name or the box color there's not really much strawberry juice in anything; it's all apple and pear.
And then you have sweet potato pie...
Here in the Willamette Valley of Oregon, we grow a lot of crops for seeds, of which various squashes are some. It’s amusing to see the first time, but squash grown for seed is typically just shredded in the field, with seeds collected and the flesh tossed out over the field. Results in a lot of “wtf are they doing” among those unfamiliar, because it looks exactly like pumpkins were grown just to immediately destroy them.
Doesn't most major distributions alias vi to vim nowadays? I think I've also come across vi being aliased to vim-tiny if I remember correctly.
Everywhere else, when you type vi, you get vim. Some neophile Linux distros provide neovim instead.
Regardless, vi and vim (and neovim) are the same in basic operations.
It's still functionally correct that "vi is always installed" and no additional action is necessary for basic text editing.
https://github.com/teslamotors/buildroot/tree/buildroot-2021...
Same with this vim: if you just need an editor that is recognisable and "not weird" then this modeless vim might be useful; though why not just install nano, pico, gedit, notepad++ or even notepad.exe?
“But your fingers aren't touching the strings!”
If you learn Vim you’ll have access to Vi and Vi-like interfaces in lots of other software including terminals, database clients and everything that uses readline.
From my experience anything with "vi navigation" basically just means using the home row keys for navigation + modes. So I haven't come across many interfaces yet where the verb order differences between helix/vim come into play.
In mpv I use gg/G to getting to the beginning/end of a file.
Many terminal file managers use vim binds or idioms (such as x for delete, marks, etc).
That was more convenient for me, especially as I remap my caps-lock key to CTRL system-wide.
I taught myself vim by setting the vim cheat sheet to be my terminal background, though I greyed it out slightly so it didn't obscure what I was typing. Once you have that there are only a few phrases you really need to know: "+p, "+y, "+d to access the system clipboard, :split and :vsplit, C-w w to switch windows, and g C-g for word/char count.
https://www.glump.net/_media/howto/desktop/vim-graphical-che...
What exactly do you hate?
The site says:
> > Ctrl+S to save, select text using Shift+←/→/↑/↓, and copy/paste using Ctrl+C/V.
I haven't setup Control-S, but I have very similar bindings: Shift and arrows for selecting, then Alt or Control-Shift for moving the selection around, as shown on https://raw.githubusercontent.com/csdvrx/CuteVim/main/record...
Also, like the author I have a shortcut to change themes (F9) and another to toggle invisible chars (F8), and I try to use the top of the screen as much as possible (I show the offset in hex, the row and column position etc).
I like how vim is modal, but some Windows shortcuts (like Control-C) just make too much sense to given them up on Linux: I have put `stty intr ^X` because using Shift-Control-C to copy from the terminal was way worse.
Having a few chording shortcuts give you the best of both worlds!
BTW, all of the other shortcuts proposed on this site make a lot of sense to me: I do expect Ctrl-F to search, and Ctrl-T to open tabs, I think I will copy a few :)
https://unix.stackexchange.com/questions/12107/how-to-unfree...
I don't think anyone needs (or even wants) the terminal to freeze on such a common shortcut in 2024.
Personally, I have reclaimed Ctrl S for word delete (usually done by Alt-d)
And, agreed, macOS' use of shortcuts is fantastic and I wish I could replicate it on Linux.
gsettings set org.gnome.desktop.interface gtk-key-theme "Emacs"
xfconf-query -c xsettings -p /Gtk/KeyThemeName -s Emacs
Try both commands.I also want to use Command (Super or Hyper?), which really improves keyboard shortcuts. Command + left/right = jump to beginning or end of line, Option + left/right = jump to beginning/end of word. I know you can do the same with Control + Shift, but some apps don't support it. Plus Cmd+c/x/v for copy/cut/paste works fine in terminals, I don't have to remember to "code switch" my shortcut "language". Cmd+Backspace deletes the whole line, etc etc.
setkbmap us -option ctrlL:swapcaps -option compose:rwin
You can place that command at XFCE's startup settings for applications.
My `stty intr ^X` disagrees
I've made Ctrl-C do copy paste in the terminal, even in vim, with a special function for wayland:
vnoremap <C-C> <CMD>call WLCopy()<CR>
I find it rather useful to keep important output of programs on the screen when it is impossible (or I forget) to pipe them into a pager.
Ctrl-C does work in the GUI. That said, one thing I like about Linux is being able to highlight text using the mouse and then pasting it by middle-clicking. I don't have to interact with the keyboard at all to copy and paste text that way.
Not expecting anyone to agree, but this is how I feel when using minimal shells that do not implement vi editing, e.g., set -V or set -o vi. Busybox/toybox is one example. In the aggregate, I actually do more editing on the command line than I do in vi. If the shell is permanently set to emacs-like keys and editing then I am constantly switching back and forth to "vi mode" everytime I edit a text file and return to the shell, i.e., nonstop.
Maybe putting diesel generator in a Tesla so you can use it even though charging is not your cup of tea.