

I’m so glad you can automate QA jobs
Silly cat :3
Sharkey: @backhdlp@woem.men
Mastodon: @backhdlp@tech.lgbt
pronouns.page: @BackHDLP
Old account: @backhdlp@lemmy.blahaj.zone
I’m so glad you can automate QA jobs
There’s a python library for everything
Pretty sure that money is for the people employed by the GNOME Foundation, they don’t just pay every contributor.
Might be an afternoon of CSS, or might be 2+ weeks of React
read the code and pretend you understand it (real understanding will slowly come with that)
I haven’t tried last.fm but I like ListenBrainz for that stuff.
To determine the current WM in Wayland, neofetch first tries getting the process connected to the current Wayland display. If that fails, it checks all running processes against a hardcoded list of known WMs (which includes river).
In practice, it seems to prefer the value of XDG_CURRENT_DESKTOP, but idrk, neofetch is magic.
You might’ve seen people use fastfetch, which should just get it right, but is also magic, tho at least c and not bash.
you just like me frfr (I’d post here if I’d customize my bar)
wdym “just started”, it looks like you’re done
your desktop looks like a lock screen with the clock lol
false
tar: You must specify one of the '-Acdtrux', '--delete' or '--test-label' options
Try 'tar --help' or 'tar --usage' for more information.
zsh: exit 2 tar
If you put a decimal in your statistic, it becomes 82.6% more believable.
There’s a pinned post at the top of this very comm
Only for you
Your launcher link to rofi-wayland saying fuzzel doesn’t work.
Meanwhile Rust: you might get an error at line 45 word 3 because it assumes variable foo is an int32 but it could be (whatever else idk), let’s not compile this before you correct this by changing line 43 in this specific way. Here’s the before and after code snippets so you can just copy-paste the fix.
I think we’ve all been at a point like this
don’t need an extra guy