Idk, writing POSIX-compliant shell is so miserable that I avoid doing it when I can. You can use Bash on BSD and all other unixes, so it’s still a relatively portable solution.
Alt account of @Badabinski
Just a sweaty nerd interested in software, home automation, emotional issues, and polite discourse about all of the above.
Idk, writing POSIX-compliant shell is so miserable that I avoid doing it when I can. You can use Bash on BSD and all other unixes, so it’s still a relatively portable solution.
I was waiting for someone to come along with this response lmao
I’m terrible at remembering shell string operation syntax, but this is the ultimate answer.
no pipe necessary, just
sed -E 's/TH|[EL ]|DO//g' <<<"$line"


I seem to recall hearing that there were genetic/epigenetic components that predispose some folks to those personality disorders. I’m not disagreeing with you and I don’t know if the research I saw was corroborated. I just think it’s an interesting idea that you’re not born with NPD, but you can be more vulnerable to developing it.


It does! The ease of exporting/importing mod packs as codes is part of what really sold me on it. r2modman’s UX around that task leaves something to be desired imo


If you’re using r2modman, you should check out Gale. It’s basically a drop-in replacement that’s WAY faster and has far better UX in my opinion.
I think a good doctor would provide this explanation to the patient. Be like “Okay, let’s get you fixed up! The medications and techniques we use change if you’re pregnant, so can you tell me when your last period is?” Only takes a second. Doctors should be aware that women often feel ignored and mistreated in a medical context (given the body of literature and studies demonstrating such), so like, they should work to correct that issue. It shouldn’t be difficult to do. It just requires a wee little bit of empathy.
If you want more help with Bash in the future, this is the best resource I’ve found in 13 years of writing bash professionally: https://mywiki.wooledge.org/EnglishFrontPage
Bash FAQs and pitfalls are the primary sections to look at there.
Thank you for providing the easiest and most portable answer. This will handle files with special characters perfectly unlike most of the responses here which rely on a while loop (to say nothing of a for loop ).
Shell scripts are one of the worst possible applications of an LLM. They’re trained on shit fucking GitHub scripts, and they give you shit in return.
You may have a bit of a hard time finding something that’s completely FLOSS that’s not on the older side (the sar visualizer being a Java desktop application being a consequence of that age). There are various ways to dump resource usage into a time series database like Prometheus (Apache2), InfluxDB (Apache2/MIT), or VictoriaMetrics (Apache2) and then visualize it with a frontend (Grafana, APGL). The database is going to be the tricky part. All of the time series DBs I’m aware of are permissively licensed. Grafana may be a good fit for you, however. It’s written in Go so it’s relatively light, although it obviously requires a browser to interact with.


Arch is a pretty good one if you want to control and tinker. I have personally found it to be very reliable over the years, and the AUR is exceptionally powerful (although you NEED to review your PKGBUILDs, there’s nothing stopping someone from putting malware on the AUR again). The packaging format is so simple and easy that I actually build a few performance-critical packages locally so I can tweak compiler flags (gimmie that -march native).
Nix is cool and kinda crazy, but honestly? I’d hold off until you’re comfortable with Arch. Same with Gentoo.
It does, the repo is tagged as AGPL.


You mean code completion that just parses a file into an AST and does fuzzy string matching against tokens used to build that AST? I would not personally classify that as AI. It’s code that was written by humans and is perfectly understandable by humans. There is no probabilistic component present, there is no generated matrix, there’s no training process, it’s just simple parsing and string matching.
It’s early and I’m tired and probably in a poor mood and being needlessly fussy, so I apologize if this completely misses the point of your comment. I agree that there’s other stuff we’ve been using for ages which could be reasonably classified as “AI,” but I don’t feel like traditional code completion systems fit there.


Yep, this is why we use GPL! Using a permissive license is like lending money to a friend—you should never, ever expect to get your money back. “Good” companies aren’t altruistic, they’re ruthlessly self-interested. They’re not going to give back to your project unless there’s a damn good reason for them to do so. There are times when permissive licenses are totally fine (like when writing some kinds of libraries), but if you care about freedom of an application then you should stay the fuck away from MIT, Apache, BSD, or any other permissive license. Just use the GPL, folks.
edit: Using GPL from the getgo would have prevented this atrocity from occurring: https://github.com/coredevices/libpebble3/commit/35853d45cd0ec51cb732be866f6f72467653a613
They couldn’t have relicensed the project without community approval if it had been using a copyleft license in the first place.
Also, fuck off with your fucking AGPL license with a copyright transfer CLA bullshit. I’d love to see a new version of the AGPL that expressly prohibits copyright transfers. Never let a company take your rights away from you. A copyright license makes even the GPL effectively meaningless if the company wants to rug pull at a later date.


Yeah, that’s a “block and move on with your day” sort of account for sure.


Yep, and it’s still used in some new ones.

OP is in the US, so no 3 phase power unfortunately ):
Was this done according to proper clean-room design principles? If so, then imo the GPL is still working as intended. The company had to spend a fuckton of money and time getting one engineer to read the source and describe what was done to other engineers, and then ensure that one engineer never ever worked on the project again.
If they didn’t do that then they violated the GPL and someone should report them to the SFLC.
idk who downvoted you, it’s a very common sentiment. I advocate for
<<<, but a pipe is often fine when performance doesn’t matter.