Christmas Breakfast Pro Tip™: Boil eggs in an electric kettle.
Yes. A small, user-funded, ad-free, federated instance running open source software. I like being able to switch instances if I need to, and not having my impressions be sold to third parties.
And while you’re at it, create a Mastodon account (https://mastodon.technology is a nice instance) and double-post for a while. Or, you can even cross-post your non-replies from Mastodon back to Twitter.
It’s difficult to be the first to switch to a new social network or messenger app. However, please ask you friends and family to move off WhatsApp again. @signalapp and @telegram are great alternatives.
Not everyone will switch, so you might have to use two apps for a while. 🤷♀️
I might publish from there through ActivityPub eventually.
I didn’t start my own instance because I didn’t want to have to keep it running. Right now, all updates are in a git repository, and that page is statically generated. Also, I’d like to post updates that only get syndicated to a single place, and not necessary to Mastodon (like Reddit, for example).
Oh, wow. I love the idea of editing lines based on context other than what file they’re in. The use-case in the README—all lines with a linter error—is very clever as well. Nice trick!
qq[commands]q here, because somebody once told me that‘s quickest. Using the q registry is probably adding the the confusion, though.
Something I learned the other day is that you can print and yank macros from and to their registries by using "ap and "ay (for the a registry) so you can see commands printed out. I’m hoping that will help me get a feel for them a bit more.
Last week I learned about Vim’s o in visual select mode, cursor placement with /foo/e+3, why I should use line completion (⌃X⌃F) and that I should finally get into macros. Some great tips in this thread (and more are always welcome).
https://twitter.com/
What's that Vim trick that blew your mind the first time you learned about it? A feature that has a big (or small) impact on your workflow, or just a command you use a lot. Anything goes! 🤯
— Jeff Kreeftmeijer (@jkreeftmeijer) December 20, 2018
Got it, I’ll keep following @ed1conf over there, then. If you’re ever looking anyway, I have a testing account on https://mastodon.technology, which looks like a friendly instance. :)
Mastodon ProTip™: Adding RT @ as a filter will hide all of those cross-posted retweets from your timeline.
To get the local ID for a Mastodon status on another instance, use the search API, or the search bar in your web client.
Searching for a status URL (like https://mastodon.social/
In that vein, great to see https://bsd.network/
Hello, from the same boat! 👋
I’ve been trying to switch it around by cross-posting from Mastodon to Twitter instead, which has helped moved my primary feed over here a little. Still getting more response on the other side, though.
Congratulations on your first plugin! It might be nice to check the interface style on BufEnter, so you can switch to dark mode and have Vim switch the background even if it was already open.
I checked how the darkmode-aware background colors worked the other day, and it seems to be an application default. In custom themes, the only way I found to get toggling background colors is not to configure any. I’ll try doing that in my theme, to see if that’d still look good, sometime soon.
For glare, I usually switch to the light version of my terminal theme. Since Dim uses the same syntax colors for dark and light backgrounds, that just means swapping the text and background colors. I think the easiest way to get a higher contrast would be to use a higher contrast terminal theme.
@Netlify Do you expose access logs for hosted sites? I’d love to be able to parse them myself to extract visitor counts without having to use an external (JavaScript-based) analytics package.
I’ve tried showing off with macros in the past, but with my weak macro skills, that usually turns into a comedy act more than anything else.
I’ve been planning on learning more about macros, though. Thanks, great suggestion!
Also, the autowrite and autowriteall options save the file when switching buffers or quitting, which covers cases where the file is changed without switching modes.
Ideally, it’d just save whenever &modified is 1, but I haven’t found a way to hook in yet. 🤔
In that category; my ,s and ,S both pre-fill the ex command with :%s///, but the former places the cursor in the search pattern, and the later in the replacement.
nnoremap ,s :%s///<left><left>
vnoremap ,s :s///<left><left>
nnoremap ,S :%s///<left>
vnoremap ,S :s///<left>
Exactly the kind of tips I’m looking for, thanks! I have :wq and :q! in my muscle memory, but I’ll be sure to try these.
I’ve been meaning to auto-save for a while too but I’d like to always save (like on InsertLeave too), so I don’t need to worry about saving myself.
None of the suggestions are too basic. I’m specifically looking for tips that go easily unnoticed (like o in a visual selection), because they have the biggest chance of sticking and being useful. Thanks for reminding me of ⌃a and ⌃x (I always forget), and g ⌃a is amazing!
You mean setting macros with q<letter><commands>q, right? Not much experience with macros, because they always take a lot of time to get right for me. 😅
They’ve been on top of my list to properly figure out for years, though.
Macros have been near the top of the list I’ve been planning to properly figure out for years now, I just never get around to it. I always have a hard time blindly recording macros with q<letter><commands>q.
I love the idea of writing macros in command mode, and having them available in the command history. That article looks great, too. Great suggestion!
This is why I was hoping you’d chime in. Awesome suggestion, and definitely something I’ve missed in the past. Thanks!
I use vim-tmux-navigator to switch between Vim and tmux splits, configure Vim to use the unnamed paste buffer, and use reattach-to-user-namespace to do the same in tmux (although that doesn’t seem to be required anymore).
I’ll try the built-in terminal again sometime soon, though!