mprocs VS homebrew-core

You might script something like that using tmux or your specific terminal app, or you might get along with mprocs.

mprocs?

I was originally looking to use something like mprocs to explicitly save commands I run often on a per-directory basis, but I like the idea of dbhistory simply tracking which commands I run. To combine the two ideas, you might add something like "pinning" to dbhistory, so I can pin commands to the top of the list, and perhaps those commands aren't removed (by default) when running -p Cleans up the database. Just an idea.

in that post I did not explain why I was asking. Basically, I was trying to write an "el cheapo" replacement for https://github.com/pvolok/mprocs -- a nifty little tool that lets you maintain a list of commands that you run frequently, and be able to start/stop them when you like, and if needed, zoom into their execution windows and interact with them.

UPDATE: mprocs is close to what I'm talking about.

Github: https://github.com/pvolok/mprocs

I'm growing interested in TUI, but I don't know if this is a good example of how to do it. I see it's drawn using echo escape sequences, but other apps I've seen (e.g. https://github.com/pvolok/mprocs) use TUI toolkits. Does anyone want to share good resources on how to get started?

Strangely the repository https://github.com/pvolok/mprocs is not given.

$ brew info eza ==> eza: stable 0.18.13 (bottled) Modern, maintained replacement for ls https://github.com/eza-community/eza Not installed From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/e/eza.rb License: MIT ==> Dependencies Build: pandoc ✘, pkg-config ✔, rust ✘ Required: libgit2 ✘ ==> Analytics install: 12,792 (30 days), 38,295 (90 days), 68,375 (365 days) install-on-request: 12,790 (30 days), 38,293 (90 days), 68,375 (365 days) build-error: 0 (30 days)

Is disabling the compromised repo the typical GitHub policy? My concern is there are monorepos used by package managers, like brew, that are a collection of thousands of projects [1]. These monorepos seem like a prime target for attack and if GitHub disables one because a malicious commit was merged then you've taken down an entire ecosystem.

[1] https://github.com/Homebrew/homebrew-core

> Correct. Though we do not appear to be affected, this revert was done out of an abundance of caution.

[1] https://github.com/Homebrew/homebrew-core/pull/167512

> right, but now you know even less about your setup when you some roadblock

This is the same with a binary though. And with homebrew, you can't follow patches or flags used or if they change.

- https://github.com/Homebrew/homebrew-core/blob/c964ad7fa53ad...

definitely be careful about using fortune in a corporate environment or public space if you don't know what dat files you are using or you might just get an extremely unwelcome surprise.

I was practicing a presentation and used to use "fortune" all the time. I forget exactly what it output but I remember being absolutely mortified about what could have happened if that had popped up during an internal company tech talk.

Kudos to brew for keeping unsuspecting people safe

https://github.com/Homebrew/homebrew-core/commit/3fb3c4c3e55...

I'm sorry to be asking this as I find it a bit silly, but it's blocking my PR [3], so could a few of you star the project on Github [1] to get my PR to run?

[1] https://github.com/laktak/chkbit-py

[2] https://brew.sh

[3] https://github.com/Homebrew/homebrew-core/pull/160018