I have a sway workspace indicator on the left, the right side has:
- Monitor brightness
- Volume
- Local IP address
- CPU temperature
- Keyboard layout
- Local date and time
- UTC time
- Tray
Gobbel2000
joined 1 year ago
I have also switched to Colemak and my advice is to just not do that. Just learn Colemak without looking at the keyboard, it'll make you a better typist anyway and you can get comfortable with it within a few weeks. In particular you don't want to move the little knobs on the index finger keys (F and J).
The hexagon minecraft one is neat.
That was quite the rabbit hole, and know I know that my CPU has a bug. Great.
I still don't see how having a flat subvolume layout would make that more problematic. You can still (even better in my opinion) choose what subvolumes to automatically snapshot, which to include in backups etc.
Yes, that seems correct to me. I would also say that the flat layout is preferable because it makes dealing with snapshots later easier. When snapshotting the rootfs subvolume you won't have to keep track of where exactly the home subvolume is located and it is easier to boot into a different rootfs snapshot.
Great to see the Servo project getting more support. Having more choice in this space is a very good thing. Igalia keeps doing fantastic work.
Everyone is having fun playing air guitar, though bad they may be at it. Except the beige dude who forgot his air guitar at home.
My experience is you should try to always use find over ls when writing robust scripts, and consider ls as just an end user tool, not a scripting tool.
It took roughly 10-15 minutes on a Ryzen 5800X with 32GB RAM. I have compiled other programs before, but none nearly as large and notable as the kernel. I am in fact very close to getting a computer science degree, but that is in no way required to be able to do this. If you are able to follow the wiki-page I linked, you can do it too.
You're trying to iterate over a Vec while mutating its contents in other places, which is something the borrow checker doesn't like. Altough the later cards that get their copies count increased aren't the same as the iterating reference
card, Rust forbids two mutable references into the same Vec, even if they reference different elements of the Vec.You could try to iterate over indices into the array instead of directly over array elements, then you get rid of the reference in the outer loop. This would probably require the least change to your code.
Another option would be to split apart the data structures between what needs to be mutated and what doesn't. I've solved this puzzle in Rust and had a separate mutable Vec for the number of copies of each card. Then you can iterate over and mutate both Vecs separately without having conflicting references.