Postmodern

I think we'll need a more extendable solution for distro/release specific package names. We've ran into this in the past with Ubuntu and Debian. The simple solution I've tried to...

I'm curious how RedHat's shift to CentOS Stream might change this?

Is this still an issue? 0.8.2 added better logic for when and when-not-to use `sudo` with `brew`. See 093608aed1d189ec6f8a919fe95b9b7e1812e252

Closing this as it was an issue with zenmap.

Was going to submit a bug about this. I found it odd that `sord --rbs` cannot output the type of constants, even when they have literal values (ex: a literal...

I'm messing around in the 1.0.0 branch with extracting the `trap DEBUG`/`preexec_functions` hook as a generic `chruby_hook` function that calls other functions added to `chruby_hooks`. This would allow adding other...

Currently `chruby_hooks` is the Array of function names, and `chruby_hook` is the entry point function that get's added to `trap DEBUG`/`preexec_functions`. Could also rename `chruby_hook` to `chruby_call_hooks`, or rename `chruby_hooks`...

Closing this since the rubys `bin/` and rubygems `bin/` directories must be prepended to the path in order to override system `ruby`, `rake`, `irb`, or any other system gems. As...

@eregon like we have discussed on multiple occasions, changing the path of the `GEM_HOME` is a breaking change and would cause chruby users to suddenly lose all of their installed...

Just like to point out that [rack-session-2.0.0](https://rubygems.org/gems/rack-session) now requires `rack >= 3.0.0`, however [sinatra-3.0.5](https://rubygems.org/gems/sinatra/versions/3.0.5) still requires `rack ~> 2.2`, which makes the `rack-session-2.0.0` gem incompatible with `sinatra