Drop-in Pry REPL settings meant for exploring gems.

René Maya c57010db8c Update ReadMe		%!s(int64=6) %!d(string=hai) anos
bin	261935ad7f Init ruby lab	%!s(int64=8) %!d(string=hai) anos
lib	261935ad7f Init ruby lab	%!s(int64=8) %!d(string=hai) anos
.gitignore	261935ad7f Init ruby lab	%!s(int64=8) %!d(string=hai) anos
.pryrc	9fb72747b9 Change prompt	%!s(int64=7) %!d(string=hai) anos
Gemfile	c35c3a53e7 Add Gemfile	%!s(int64=8) %!d(string=hai) anos
License.md	946562d2ac Add license	%!s(int64=6) %!d(string=hai) anos
Readme.md	c57010db8c Update ReadMe	%!s(int64=6) %!d(string=hai) anos

Ruby lab

When reading an article on Ruby is easy to pop up to the terminal and explore the code/ideas on them. Nonetheless, a lot of the times I'm too lazy to do anything else other than run pry. Which means that I miss on a lot of the articles that cover gems or require writing more code. This is my answer to stop being lazy and get coding.

The included REPL is powered by pry and has access to lib/experiment.rb. You can use any gem within the Gemfile during the REPL session.

Setting up the skeleton

Clone this repo.

git clone https://notabug.org/rem/ruby_lab.git

Get into the lab.

cd ruby_lab

Install dependencies locally to keep your box clean.

bundle install --path .bundle/gems

Whenever you start a fresh terminal session you'll have to add the bin folder to the PATH once.

export PATH="$PWD/bin:$PATH"
hash -r 2>/dev/null || true

Alternatively, create a simple shell function or alias for them.

Start the Ruby lab:

repl

You can finish your REPL session with exit.

You can add your own binstubs to bin. Alternatively, you could generate them for those gems added later which might need to run on their own terminal session.

bundle binstubs <gem_name_as_in_gemfile>

If using rbenv, rehash.

rbenv rehash

What's included in this lab?

ruby_lab/
  .gitignore
  .pryrc
  Readme.md
  Gemfile
  lib/
    experiment.rb
  bin/
    repl

.gitignore in case an experiment takes an interesting turn theres no need to commit the actual gems.

.pryrc Pry configuration file. Defaults to emacs as editor. If you add more files to lib you'll want to list them in here so they're available in the REPL session.

Gemfile list of all the gems you want available in the lab. Don't forget to bundle install whenever you add new gems.

lib/experiment.rb for whenever the experiments require defining more code than you can possibly type without making any typos. Since the lab comes packed with pry-byebug you can add binding.pry and step over the code in lib/experiment.rb

bin/repl the binstub that starts the Pry REPL session.

ruby_lab shell function

If you want to an easy way of creating a lab perhaps you should consider adding most of the steps above into a simple shell function.

Readme.md

Ruby lab

Setting up the skeleton

What's included in this lab?

ruby_lab shell function

License