. . . cricket sounds . . .

The party died without golinux here

The system I tested on I only installed the standard system tools or utilities whatever it's called.  You know the tasksel menu on the devuan/debian installer. No DE or anything else. It was the only thing selected.

of course then I manually installed the xserver, jwm, and more.

Thanks yeti!

You are correct,  use a colon for groups, and no colon for usernames.

Why did it work for me? you're not gonna believe it. I belong to a group with the same name as as my username. What are the odds. lol.

As I said I usually use groups instead of a username, and since my test with usernames worked with the colons I assumed that was the correct way.

Still my other 2 points are valid. use the full path and the args did not work form me.  .  . and yes I did test the args after removing the colon.

Great news!

OK! Who are you and what did you with the the real zapper. LOL

Seriously though, You have a good point. It's next to impossible to have an absolute stance on libre software and have a full functioning machine. To much hardware depends on blobs. The best you can do is minimize the usage of blobs, and try to use hardware that does not depend on them.

Not to mention being force to compromise on these issues when collaborating with others.  For example, on a recent project I've been force to use systemd.  Yuch!

Warning! My Long winded opinion

This question hits at the heart of the matter.  The truth is any type of software package, archive, etc can be used to spread malicious content. An appimage isn't any less secure than a .deb.  The real concern is not the format, it's the source. You really can't go wrong if it comes from the Debian/Devuan repository. I only use these formats as a last resort. To be honest they are probably safer than using random packages from the AUR. At least the portable formats attempt to sandbox the software. Just a thought, not defending these formats.

I'm not going to limit myself to only the software provided in my distro’s repository, but on the flip-side I am skeptical, and examine foreign packages carefully.  A stance I believe many, if not most people take.  JWMKit is not in the Debian repository, but I can proudly say it is used by many. Quite a number of users directly use the packages provided on my sourceforge. I am very transparent and not only provide the project code, but also the methods used to create packages.  I think this kind of transparency encourages trust between users and developers.

My concern for these formats is more about not wanting to have corporate junk pushed onto me, and having unnecessary service running in the background. As for the security of these formats I think it’s an issue that can be resolved by pooling the resources of the community.

...but to be honestly I’m still hoping snaps and flatpaks fail.

I find that searching the AUR is a great way to find software, and there are a lot of circuit simulator listed. Just follow the links to the upstream source (github, etc). You may even find a few are already available in debian.

AUR Search for circuit simulator

While not a simulator, my favorite circuit tool is DIY Layout Creator.  It's excellent for designing you own guitar pedals and it should be since originally that was it's intended purpose.

DIY Layout Creator

Q: Why did the old man let out a groan?
A: He was catching up on the Devuan forum joke thread.

@Iggy64 Great work!

I wonder if this has something to do with why Firefox is silent with sndio when using alsa-sndio? Firefox creates a sndio stream and you can control it. It's just silent. I'll have to test if I can use libasound's pre-amp with it.

Thanks for reporting back with your findings. I believe you've provided some useful information.

WOW!
Quickfur, that has to be the ultimate Geek/nerd joke. Dare I say a dad geek joke?

@quickfur
I had the thought of creating a dictionary for terminals and the parameter.  If a terminal was not in the dictionary just don't set the title. For now I think I'll just not set the title.

@The-Amnesiac-Philosopher
To be clear this is not about "general" settings for the terminal, but for a creating a launcher that starts the terminal and a specific task.

My goal was to set the title to the name of the task the terminal would be running. To clarify I mean the actual name, not the executable name.   Most terminal will set the title to the executable name. Which is close enough. So it's not worth writing a bunch of code to implement.

Not everyone uses the same terminal, so if I share code with others that launches the user's default terminal emulator then that code needs to be compatible with as many terminals as possible, hopefully all of them.  If the parameters used are not consistent across all terminals then the code will break.

Setting the title is only cosmetic and is not that important.  For the sake of compatibility I guess I'll just leave ti out for now.