Just an ordinary myopic internet enjoyer.

Can also be found at lemm.ee, lemmy.world, and Kbin.social.

  • 0 Posts
  • 36 Comments
Joined 1 year ago
cake
Cake day: August 15th, 2023

help-circle


  • 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 WIS
    • Arch Wiki — +2 on arcana checks
    • AUR — +1 DEX
    • system 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 armor

    Customized Hyprland [rare armor, attunement]

    • attunement prerequisite: once every long rest, roll arcana with DC 25. must succeed thrice
    • unlimited customization — when attuned, +2 CHA
    • perpetually under construction — regardless of attunement, -1 DEX

    Customized Neovim [rare weapon, attunement]

    • attunement prerequisite: once every long rest, roll arcana with DC 25. must succeed thrice
    • unlimited customization — when attuned, +2 to attack rolls
    • learning cliff — disadvantage to attack rolls when not attuned to this weapon
    • I 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 CON

    EDIT: 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.



  • 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



  • 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 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.





  • 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 actually use Arch. Sorry.

    But really, I would have gone with EndeavourOS (instead of Arch) if it were not for my friend who really strongly advocated for Arch (even installing it for me—or rather, converting my Manjaro install into an Arch one).

    If I’ve had any regrets in my Linux journey, it’s choosing Manjaro instead of EndeavourOS as my introduction to Arch-based distros.


  • I’m with you on liking multi-monitor set-ups. I also have several workspaces and activities (a KDE thing—you can think of it as another set of workspaces accessible via a shortcut key), which means I’ve got tons of “space” to play around with.

    I‌ could have my e-mail program run on one workspace, then switch to my main workspace with one screen for VSCode (or whatever) and another for the browser window with lots of tabs that I can just refer to while doing work. And then in a different activity, a multi-media program might be playing a podcast or just some music to help me focus.

    My discord is usually on the same activity as my multi-media program though, as I don’t really need to refer to it as often. If there’s a new message for me, my system gives me a notification and an icon in my system tray lights up or something, indicating a new message.

    But yeah! You do you with your preferred workflow!