New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Perhaps to consider: new subcommands, "gem enable" and "gem disable" #1616

ghost opened this Issue May 12, 2016 · 0 comments


None yet
2 participants

ghost commented May 12, 2016

I would like to suggest a feature.

This issue is related to:

  • Enabling a (gem) library
  • Disabling a (gem) library

Here are my current environment details:

Operating System: GNU/Linux
OS Bit Type: x86_64
CPU Model: Intel(R) Celeron(R) CPU G1630 @ 2.80GHz, 2 cores
CFLAGS in use: -O2 -fPIC -fno-strict-overflow -Wno-error
RAM: 7858728 kB RAM (7674.5 MB) (7.5 Gig)
Screen Resolution: 1920x1080
GCC Version: 5.3.0
Glibc Version: 2.22
Kernel Version: 4.4.0
Ruby Version: 2.3.1p112 (2016-04-26 revision 54768) [x86_64-linux]
Rubygems Version: 2.6.4

I was thinking of a new subcommand called "gem disable" and "gem enable".

This would just temporarily disable a gem. That gem can be re-enabled again.

Now you can rightfully say that one can uninstall, and reinstall a gem. But I
as thinking more of a lightweight alternative that would work in a really
simple method, looking at the local sources ONLY.

It probably is already possible with the existing commands, but I found that
a new subcommand would be nice.


gem list

*** LOCAL GEMS ***

bigdecimal (default: 1.2.8)
coderay (1.1.0)
did_you_mean (1.0.0)

Next I want to do:

> gem disable did_you_mean

Then I want to run some ruby code to see how things are changed.

Afterwards I want to re-enable the did you mean it gem again though.

> gem enable did_you_mean

I am not sure if this is really useful, but if it is not, just close it as your leisure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment