bob VS homebrew-core

That depends on the debian stable repo what version of Neovim they provide. My suggestion would be to check out bob, which as far as I'm concerned it's the easiest way of installing Neovim and gives you the ability to switch between stable and nightly.

Config details: 0. Distribution: AlmaLinux 9 (what I'm forced to use at work) 1. Also requires: git, curl, clang, rustup, fzf 2. neovim version manager: https://github.com/MordechaiHadad/bob 3. I'd like to use the LazyVim setup 4. using an nvims() shell function to switch between setups (default & LazyVim, for now) (see https://gist.github.com/elijahmanor/b279553c0132bfad7eae23e34ceb593b)

Auto-install of Bob Neovim version manager (optional)

I personally use bob, ($ cargo install bob-nvim), and it's been great for ease of version management, including nightly

Honest just use bob on non-bleeding edge distro

There's already bob (Version manager for Neovim)

I use on all platforms: https://github.com/MordechaiHadad/bob

current stable is 0.8.3 maybe try the unstable ppa or appimage or bob.nvim

If you want to peek at it now, you could try a neovim version manager like bob... https://github.com/MordechaiHadad/bob I've been using it recently and it makes experimenting with new stuff a bit easier. Then if you run into issues you can switch back to a stable release. I'm considering doing a video on this too since I think it would be helpful to some... and I don't think it's very well known

$ 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