turboponyy

16 ms·

181.
by turboponyy 5y ago
I would totally use this over GitHub Gists if this worked for file formats other than markdown, where you could specify the syntax highlighting language. Of course, you could just wrap your text in ```py ```, for example, but that would mea
182.
by turboponyy 5y ago
This is the variant that I've played - with the constraint that you must play at least one card, of course. We also included an endgame for the players that had managed to get rid of all their cards, though: they had to successfully gu
183.
by turboponyy 5y ago
The way I learned (and still do learn) vim was the following: 1. Try to use vim to do something with text 2. Realize I don't know how to do that (efficiently, or at all) 3. Look up how to do it efficiently 4. Try to do it that way from
184.
by turboponyy 5y ago
cat key | xclip -selection clipboard # is even easier after you alias the second part (edit: or whatever the Wayland equivalent for xclip is)
185.
by turboponyy 5y ago
That sounds like a lot more trouble. And then again, you could build the same templates, styles, and macros over Latex for even more performance. Not to mention that Latex files are just text files, so you can apply any sort of text process
186.
by turboponyy 5y ago
With regard to vim, unless you've really hacked away at your .vimrc / init.vim, you can usually just apply the vim plugin to your editor and have an identical file editing experience. Interfacing with the file system / Git &#
187.
by turboponyy 5y ago
If you followed through with your analogy, you'd have to concede that non-modal editors are like cars without gearboxes. Either way, what's distracting context switching for one, is essential functionality that enables effortless