Postmodern

`max_nesting` is not an appropriate solution, since GitHub sets that value.

Last I heard, [GitHub was still using RedCarpet](https://github.com/blog/832-rolling-out-the-redcarpet). 2-3 levels is extremely low, also I question the reasoning behind not allowing arbitrary nesting. To my knowledge, no other markdown parser...

@mattr- Ah. Still, they are using RedCarpet's code-base. Not sure if they pull in upstream patches from RedCarpet.

You would have to override `#select` to wrap the result in a new `AttributeSet`. While it would be nice to retain the methods in `AttributeSet`, `#select` traditionally returns an `Array`...

@maniSHarma7575 as indicated in my issue, I'm not using `rails db:drop`. I am directly calling `ActiveRecord::Base.establish_connection` and directly invoking the migrations using `ActiveRecord::MigrationContext.new(['path/to/db/migrate'])`. I discovered this limitation when trying to...

@maniSHarma7575 why? It does not have to raise an error, it can simply create the parent directories using `FileUtils.mkdir_p`. I don't see any benefit for having such a limitation. This...

I would lean towards a bundler style syntax: ``` chruby '1.9.3' do gem 'foo' end chruby '1.9.3', 'jruby' do gem 'foo' end ```

I don't know how LWRPs work, but I would favour the least repetitious / "blocky" syntax.

Actually this is an artifact of how chruby sets `GEM_HOME`. chruby doesn't take into account `RUBY_PATCHLEVEL`, in order to allow re-using gems between patch-level upgrades.

Correct. `GEM_HOME` is defined as `$HOME/.gem/$RUBY_ENGINE/$RUBY_VERSION`.