Note that `git rebase --update-refs` lets you just rebase the last branch and the entire stack gets updated. You just need to know which branches to forcepush.
404 karma · joined March 30, 2018
https://meet.hn/city/gb-London
Socials: - github.com/liskin - linkedin.com/in/pivnik - reddit.com/user/Liskni_si
Interests: Cycling, Fitness, Gaming, Hacking, Hiking, Open Source, Outdoor Activities, Programming, Remote Work, Running
---
Note that `git rebase --update-refs` lets you just rebase the last branch and the entire stack gets updated. You just need to know which branches to forcepush.
My .gitconfig has:
[pretty]
co-authored-by = Co-authored-by: %an <%ae>
[alias]
co-authored-by = log -1 --pretty=co-authored-by --regexp-ignore-case --author
Now `git co-authored-by Tom` generates a Co-authored-by: trailer for the last person named Tom who committed to the repo. Typically I'd just do `:r !git co-authored-by Name` in vim (mapped to \gc to save typing).Layout and the shape of keys are orthogonal concepts.
But yeah, you're right that there aren't many options these days, and the T25 is getting old. :-(
Keys can easily be remapped in software, so all you really is the physical keys layout (full size arrows + two keys on either side of the up arrow) and the trackpoint. Menu or PrintScreen or whatever doesn't really matter much.
> PageUp above Left, PageDown above Right: to me, that's the most important thing ever!
> PrintScreen between right Alt and right Ctrl: very important too
That's not a proper ThinkPad keyboard at all. That's the new 6-row fake which has 10 fewer keys than a proper ThinkPad keyboard, which is this one: https://laptopkeys.com/uploads/704_1348778226_Lenovo%20t410s...
Documentation for the nvidia module claims [0] runtime pm is supported even when the module _is_ loaded for GPUs since Turing, but I haven't been able to test that (mine is older than that).
[0] https://download.nvidia.com/XFree86/Linux-x86_64/435.17/READ...
Not sure how that's useful as the form factor doesn't really allow for a 7-row keyboard, or full-sized arrow keys. Which is a real missed opportunity in my opinion: a laptop (any computer, really) is primarily a device with inputs (keyboard, touchpad) and outputs (display) so naturally you want those to be as good as possible (and if there isn't a 99.9+% consensus on what that means, modular/configurable) as that's what you'll end up using for hours every day. Why compromise on a single "pretty" layout of physical keys?
That's not true, though. You absolutely can merge a single commit, via git push, there's just no button in the GitHub UI for it.
Out of those persistance ideas, I'm still very much in favor of simply separating the compositor/WM into separate unix processes. Feels like the right thing to do.
Can you perhaps share some of those ideas? Might be something I haven't thought about. :-)
> wlroots was my choice, because I like the guys and worked with them on the project. Other libraries (most relevant probably libweston) are a bit more "fully featured" but also slightly less flexible.
Is that still the case today? I mean, I haven't really spent any considerable time researching the Wayland landscape, but I was under the impression that wlroots gained considerable momentum in recent years while weston is still just the reference compositor, but not really used in any well-known Wayland compositor.