oscar

I will sound really nit-picky buy the biggest thing keeping me away from using KDE is that accent-colored bar on each window in the taskbar, and the different coloring of open/focused/minimized windows. I want it sleek but not cluttery.

I've tried about a dozen themes but I couldn't find any that got rid of that and looked good. I tried fixing it myself but editing svg files was too difficult for me.

I hope plasma 6 adds more options for this but I'm not holding my breath.

Depends on the devs but I reckon they won't use the API.

Something i especially appreciate about winget us that it will "index" (or whatever you want to call it) software that was installed outside of it. For example if I install app XYZ through an .msi setup file, I can update it using winget.

So it seems I can also use scoop or chocolatey to install new software and then keep managing them through winget.

To me it looks like it's the officers fist that broke the window, not the kids face. Hopefully he wasn't badly hurt.

I'm 24 hours in and I didn't even know there were acts lol, but I assume I'm also on act 1. I've pretty much only done side missions.

Of course they weren't asked as often, there's significantly less number of users on Linux. 96.21% of the users asked was on Windows.

You can self host GitLab CE for free.

I don't think it's available on android. But if it is, then I would expect it to be it's own separate app that can coexist with the regular firefox. That's how it is on PC.

There default settings are highly unsecure.

There is a Firefox fork called librewolf which addresses that.

I haven't gone though it in detail but something that stood out to me is the complexity of process_content().

If you at some point end up with a large function, or if you have deeply nested blocks, it can help readability to split it up into smaller functions with more clear goals, even if they are only called once. In your case you could keep process_content() as a sort of parent function for calling smaller ones.

I'm guilty of large functions too because it's easier to just add stuff to a single function while developing and debugging, but before I submit stuff I tend to go through and clean up by doing this.

Though I guess this is sort of opinionated too!

Good point. But then if both the script and the command have the same filename, it will be important to make sure the script has a higher precedence in the PATH. Adding it to the end of .bashrc should be enough I think.

You could write a shell script:

#!/usr/bin/env sh

export SOME_ENV_VAR=value

command

Then place it on your path, for example /usr/local/bin/command_with_env.

I avoided overriding the command itself and naming the script the same, because then I think it would try to invoke itself.