• 43 Posts
  • 2.32K Comments
Joined 6 years ago
cake
Cake day: May 31st, 2020

help-circle
  • To be honest, what I’m most mad about isn’t the typoes, it’s that someone generated this image and figured, yeah alright, that will clear things up.

    On some level you want to believe that even if someone does not come up with a proper concept for a visualization, that they still check what the AI shat out, so that it’s at the very least not conceptually wrong and not confusing.

    This image isn’t just shitty, it’s actively worse than having no visualization. They could’ve generated that, chuckled, and not used it. Just how do you blunder your perception check so badly that you decide to include it anyways?




  • Ephera@lemmy.mltoLinux@lemmy.mlKDE Plasma 6.6 released
    link
    fedilink
    English
    arrow-up
    1
    ·
    11 hours ago

    Yeah, I’ve done that occasionally, too, but it adds a load of friction for moving windows between screens, in particular also when un-/replugging the screen, so it’s still painful enough that I don’t bother with a second screen.

    I guess, it also plays a role that I do use lots of workspaces, so it’s 1) extra painful and 2) I don’t have as big of a need for a second screen, since I can just switch out what first screen displays very quickly.



  • Ephera@lemmy.mltoLinux@lemmy.mlKDE Plasma 6.6 released
    link
    fedilink
    English
    arrow-up
    5
    ·
    19 hours ago

    Oh boy, feature freeze for Ubuntu 26.04 is on Thursday. Hopefully, they still include this update.

    My work laptop unfortunately comes with Kubuntu LTS and I desperately want the virtual-desktops-only-on-the-primary-screen feature on there. Currently, I’m the guy that actively disables all but one screen, because my workflow does not work at all with the secondary screen switching in sync with the primary screen.


  • Ephera@lemmy.mltoLinux@lemmy.mlKDE Plasma 6.6 released
    link
    fedilink
    English
    arrow-up
    1
    ·
    19 hours ago

    I still wouldn’t assume it to actually go further than that. It’s a limitation of the EWMH standard, which is used for controlling the placement of windows.

    I don’t have in-depth knowledge of the standard, but I assume, it can only represent 1 desktop as the active desktop and stuff like that.
    Maybe you could try to be clever by e.g. always reporting the active desktop of the active screen and stuff like that, but yeah, no idea if you can do that for all aspects of the standard, and whether applications will still behave as expected.










  • What I always find frustrating about that, is that even a colleague with much more Bash experience than me, will ask me what those options are, if I slap a set -euo pipefail or similar into there.

    I guess, I could prepare a snippet like in the article with proper comments instead:

    set -e # exit on error
    set -u # exit on unset variable
    set -o pipefail # exit on errors in pipes
    

    Maybe with the whole trapping thing, too.

    But yeah, will have to remember to use that. Most Bash scripts start out as just quickly trying something out, so it’s easy to forget setting the proper options…


  • I don’t have the Bash experience to argue against that, but from a general programming experience, I want things to crash as loudly as possible when anything unexpected happens. Otherwise, you might never spot it failing.

    Well, and nevermind that it could genuinely break things, if an intermediate step fails, but it continues running.



  • Huh, so if you don’t opt for these more specific number types, then your program will explode sooner or later, depending on the architecture it’s being run on…?

    I guess, times were different back when C got created, with register size still much more in flux. But yeah, from today’s perspective, that seems terrifying. 😅