That loop of config hell is real! It has subsided recently because I got enticed into writing my own widgets. Also, yes to rainbow pastel (tho I’m using gruvbox as a base/reference color theme).
Just an ordinary myopic internet enjoyer.
Can also be found at lemm.ee, lemmy.world, and Kbin.social.
That loop of config hell is real! It has subsided recently because I got enticed into writing my own widgets. Also, yes to rainbow pastel (tho I’m using gruvbox as a base/reference color theme).
Can’t really remember much of how it looked out of the box, since I proceeded to customize it quite heavily. However, though my memory is fuzzy, I remember it looking like a combination of Windows XP and mid 2010’s Ubuntu.
Checking with the xfce website, they have this screenshot of one of their latest versions:
KDE has sane defaults when it comes to windows: it opens a window at cursor position and whether or not it’s fullscreen or maximized depends on what it is when you last closed the window.
So for example, if the LibreOffice Calc is maximized when I last closed it, the next time I use it, it’d be maximized.
Window rules, however, can be as fairly simple or as complicated as you want it to be.
For example, this is my settings for discord:
I set it to open horizontally and vertically maximized, on any virtual desktop in the ‘Background’ activity (not really something most KDE Plasma users make use of, but I do).
I had a similar workflow with maximized screens residing on different workspaces. KDE Plasma also have window rules which you can set on a per-program/application or a per-window basis (for example, main window for a program goes fullscreen into one monitor, in a workspace you specify, and the tools window opens in a different monitor in the same workspace you specify).
I used KDE Plasma for a long time ever since I started daily-driving Linux.
I like how KDE Plasma allows quite a surprising amount of customization. I also had some experience with Gnome via Ubuntu, and XFCE. Gnome looks polished, but doesn’t allow for much customization. XFCE is a lot more customizable than Gnome, but getting it to look quite right took a lot of effort.
I might be displaying my ignorance of TTRPG systems, my Linux distro and my window manager, but here we go!
Arch Linux [uncommon armor]
manual installation process
— +2 WISArch Wiki
— +2 on arcana checksAUR
— +1 DEXsystem update
— after every long rest, roll a d20. on a nat 1, you have disadvantage on dexterity saving throws until the next long rest.I use Arch btw
— +2 on persuasion checks against people who use this same armorCustomized Hyprland [rare armor, attunement]
unlimited customization
— when attuned, +2 CHAperpetually under construction
— regardless of attunement, -1 DEXCustomized Neovim [rare weapon, attunement]
unlimited customization
— when attuned, +2 to attack rollslearning cliff
— disadvantage to attack rolls when not attuned to this weaponI use (neo)vi(m)
— regardless of attunement, +2 on persuasion checks against people who use a similar weapon to this one (DM discretion)Ventoy USB [uncommon accessory]
various installation media
— +1 CONEDIT: formatting
KDE themes are a mixed bag for me. On one hand, they can potentially provide theming for little to no effort on my part (provided I do find a pre-made theme to my liking), but on the other, I had more luck with mixing and matching (and a lot of tweaking) different theme components (that is: color theme, application style, plasma style, window decorations, icon theme, cursor theme, etc). It’s a lot of work, and the result might not exactly be coherent, but you can really tweak quite a lot.
I haven’t really tried emulating the win7 look and feel by customizing KDE Plasma, but I think it’s possible. Someone in this comment chain claimed there’s a Win7 theme available, albeit not pulling it off perfectly. I guess that can be used as a starting point.
KDE Plasma + Klassy can do that. I think you can pull off a Win7 look with just those two.
KDE Plasma can get you far with its customization options, and Klassy adds more customization on top of that, and adds the translucent/transparent effects you need to emulate the Win7 look.
As far as I understand those selectors work, using shift
as the level 3 modifier is a bad idea since …
level | combination |
---|---|
1 | key |
2 | SHIFT + key |
3 | L3 + key |
4 | SHIFT + L3 + key |
5 | L5 + key |
6 | L5 + SHIFT + key |
I suppose customizing the keyboard layout such that SHIFT
can be used as L3 modifier can be done. Otherwise, you might want to refer to /usr/share/X11/xkb/rules/evdev.lst
.
Here’s the relevant part(s):
option group:option | description |
---|---|
lv2 | Key to choose the 2nd level |
lv2:lsgt_switch | The “< >” key |
lv3 | Key to choose the 3rd level |
lv3:switch | Right Ctrl |
lv3:menu_switch | Menu |
lv3:win_switch | Any Win |
lv3:lwin_switch | Left Win |
lv3:rwin_switch | Right Win |
lv3:alt_switch | Any Alt |
lv3:lalt_switch | Left Alt |
lv3:ralt_switch | Right Alt |
lv3:ralt_switch_multikey | Right Alt; Shift+Right Alt as Compose |
lv3:ralt_alt | Right Alt never chooses 3rd level |
lv3:enter_switch | Enter on keypad |
lv3:caps_switch | Caps Lock |
lv3:caps_switch_capslock_with_ctrl | Caps Lock; Ctrl+Caps Lock for original Caps Lock action |
lv3:bksl_switch | Backslash |
lv3:lsgt_switch | The “< >” key |
lv3:caps_switch_latch | Caps Lock; acts as onetime lock when pressed together with another 3rd-level chooser |
lv3:bksl_switch_latch | Backslash; acts as onetime lock when pressed together with another 3rd level chooser |
lv3:lsgt_switch_latch | The “< >” key; acts as onetime lock when pressed together with another 3rd level chooser |
lv5 | Key to choose the 5th level |
lv5:caps_switch | Caps Lock chooses 5th level |
lv5:lsgt_switch | The “< >” key chooses 5th level |
lv5:ralt_switch | Right Alt chooses 5th level |
lv5:menu_switch | Menu chooses 5th level |
lv5:rctrl_switch | Right Ctrl chooses 5th level |
lv5:lsgt_switch_lock | The “< >” key chooses 5th level and acts as a one-time lock if pressed with another 5th level chooser |
lv5:ralt_switch_lock | Right Alt chooses 5th level and acts as a one-time lock if pressed with another 5th level chooser |
lv5:lwin_switch_lock | Left Win chooses 5th level and acts as a one-time lock if pressed with another 5th level chooser |
lv5:rwin_switch_lock | Right Win chooses 5th level and acts as a one-time lock if pressed with another 5th level chooser |
It depends on what you need on a terminal. If I just wanted a terminal, I’d go with Foot, but Konsole (on KDE Plasma) might be a good all-around solution.
Not too sure if they outright lied, but I suppose we can say that they used the change to make their drives seem larger!
That’s why I wished computer people had used a prefix system distinct from the SI ones. If we’re measuring our storage devices in yeetibytes rather than gigabytes, for example, then I suppose there’s less chance that we’ve ended up in this situation.
I realized why I didn’t think of base 2 in my previous reply. For one, hexadecimal (base 16) often used in really low-level programming, as a shorthand for working in base 2 because base 2 is unwieldy. Octal (base 8) was also used, but not so much nowadays. Furthermore, even when working in base 2, they’re often grouped into four bits: a nibble. A nibble corresponds to one hexadecimal digit.
Now, I suppose that we’re just going to use powers of two, not base-2, so maybe it’d help if we do a comparison. Below is a table that compares some powers of two, the binary prefixes, and the system I described earlier:
Decimal value | Value with corresponding binary prefix | Hexadecimal Value | Value with prefixes based on powers of 16 | |
---|---|---|---|---|
20 | 1 | 1 | 1 | 1 |
24 | 16 | 16 | 10 | 16 |
28 | 256 | 256 | 100 | 256 |
210 | 1 024 | 1 Ki | 400 | 1 024 |
212 | 4 096 | 4 Ki | 1000 | 4 096 |
216 | 65 536 | 64 Ki | 1 0000 | 1 myri |
220 | 1 048 576 | 1 Mi | 10 0000 | 16 myri |
224 | 16 777 216 | 16 Mi | 100 0000 | 256 myri |
228 | 268 435 456 | 256 Mi | 1000 0000 | 4 096 myri |
230 | 1 073 741 824 | 1 Gi | 4000 0000 | 16 384 myri |
232 | 4 294 967 296 | 4 Gi | 1 0000 0000 | 1 dyri |
236 | 68 719 476 736 | 32 Gi | 10 0000 0000 | 16 dyri |
240 | 1 099 511 627 776 | 1 Ti | 100 0000 0000 | 256 dyri |
244 | 17 592 186 044 416 | 16 Ti | 1000 0000 0000 | 4 096 dyri |
248 | 281 474 976 710 656 | 256 Ti | 1 0000 0000 0000 | 1 tryri |
250 | 1 125 899 906 842 624 | 1 Pi | 4 0000 0000 0000 | 4 tryri |
252 | 4 503 599 627 370 496 | 4 Pi | 10 0000 0000 0000 | 16 tryri |
256 | 72 057 594 037 927 936 | 64 Pi | 100 0000 0000 0000 | 256 tryri |
260 | 1 152 921 504 606 846 976 | 1 Ei | 1000 0000 0000 0000 | 4 096 tryri |
264 | 18 446 744 073 709 551 616 | 16 Ei | 1 0000 0000 0000 0000 | 1 tesri |
Each row of the table (except for the rows for 210 and 250) would be requiring a new prefix if we’re to be working with powers of 2 (four apart, and more if it’d be three apart instead). Meanwhile, using powers of 16 would require less prefixes, but would require larger numerals before changing over to the next prefix (a maximum of 164 - 1 = 216 - 1 = 65 535)
One thing that works to your argument’s favor is the fact that 1024 = 210. But I think that’s what caused this entire MiB vs. MB confusion in the first place.
However, having said all that, I would have been happy with just using an entirely different set of prefixes, and kept the values based on 210.
I guess? I just pulled that example out of my ass earlier, thinking well, hexadecimal is used heavily in computing, so maybe something with powers of 16 would do just fine.
At any rate, my point is that using a prefix system that is different and easily distinguishable from the metric SI prefixes would have been way better.
I think the biggest mistake there is using SI prefixes (such as kilo, mega, giga, tera) with bytes (or bits) to refer to the power of two near a power of ten in the first place. Had computer people had used other names for 1024 bytes and the like, this confusion between kibibytes and kilobytes could have been avoided. Computer people back then could have come up with a set of base·16 prefixes and used that for measuring data.
Maybe something like 65,536 bytes = 1,0000 (base 16) = 1 myri·byte; 4,294,967,296 bytes = 1,0000,0000 (base 16) = dyri·byte; and so on in groups of four hex digits instead of three decimal digits (16¹² = tryri·byte, 16¹⁶ = tesri·byte, etc). That’s just one system I pulled out of my ass (based on the myriad, and using Greek numbers to count groups of digits), and surely one can come up with a better system.
Anyways, while it’d take me a while to recognize one kilobyte as 1000 bytes and not as 1024 bytes, I think it’s better that ‘kilo’ always means 1000 times something in as many situations as possible.
If the earliest sports were a way to practice skills needed for hunting or warfare, then making an e-sport out of spreadsheets is going back to the roots of sports. It’s practicing skills needed for your daily job.
I’ve used Librewolf until pretty recently and I say it’s not for everyone. It’s hardened Firefox made into its own thing for people who want the benefits of hardened Firefox but don’t want to go through the effort of hardening their Firefox install.
There are some sites that wouldn’t work in the strictest settings. As far as I remember, the most problematic sites with Librewolf are those that demand way too much in terms of privacy and security, so I took it as a given that if a site doesn’t work with Librewolf (with me using the default settings), it’s not worth it to enter to begin with.
Yeah, I’m sorry. I’m biased against it, thanks to my experience with it.
Well, I can take solace in the fact that 99.9% of the packages you are using are in EndeavourOS too. So, I was mostly right. :)
Yeah, also I think EndeavourOS and Arch moved to Plasma 6 at around the same time too? I tried holding off the update to Plasma 6 for a few days but finally took the update on March 12.
I also wish we could replace Manjaro with a green themed EndeavourOS. Manjaro is the next biggest Linux honeypot after OpenOffice.
I think with enough faffing around customizing things in KDE Plasma, I think a green-themed EndeavourOS is doable. Would I recommend it? Not really, lol! From what I’ve seen, I like EndeavourOS’ default theming.
It’s just a shame EndeavourOS isn’t as known as Manjaro (at least during the time I first jumped into running Linux as a daily driver). But then again, with Manjaro shitting the bed becoming more known, I hope EndeavorOS can take the place of Manjaro as the Arch-based distro for newbies.
Converting Manjaro to Arch in place is a labour of love. I have done it myself and it is was more steps than I expected it to be. Worth it though. Good friend.
Oh yeah, I was there with him when he was doing it. I can’t do any help other than cheering him on, and to have another eye on the screen making sure he doesn’t make any stupid mistakes in the process. At few points, I reminded him of the fact that I’ve backed up my files, and if things really get FUBAR, we can just do a clean install and restore the files from backup.
I’ll add another datapoint. I’ve had to do some effort removing/disabling OEM bloatware and adware on my Xiaomi phone.
To be fair though, I bought it because it has good specs for its price, and I was already aware of all the bloat and adware that came with it. The first thing I did after unboxing the phone is to just excise all of that shit.
Global version from the Philippines, if you must know.