aprescott

@mpapis that's awesome, thanks! I'm :+1: on `set -T`, even before I had that workaround, since I don't think this will apply to many people.

`set -T` seems to only fix Bash. I have a [test in my fork's branch](https://github.com/aprescott/chruby/compare/postmodern:0.4.0...subshell-auto-switching) that fails for zsh: ``` SHELL=`which bash` ./test/runner >>> Running tests under /bin/bash in interactive-mode...

@postmodern does @mpapis's approach avoid the keyword splitting problem you were facing?

I came to the list of issues for this project with similar concerns. Particularly around maintaining the copyright attribution notice as part of the requirements.

For what it's worth, as a developer looking at the license terms, when I read "this license", the meaning was/is not at all clear to me. The phrase "this license"...

(IANAL, for all this, by the way, I'm just coming at this from a developer perspective.) Personally I think a separate AUTHORS file is a bit too costly and unnecessary...

Hi @beauby! Thanks for the quick reply. There may be some design decisions to make around how to allow defining codes. For our application, we can enforce `errors.add(:foo, :bar)` using...

A small edge case, in case anyone tries this: note that using `errors.details`, as in my example code, can expose duplicate errors, whereas `errors.messages` (and `errors.keys` + `errors.full_messages_for`, which the...

I've been looking at trying to implement this, for either revision key or even just build timestamp. It isn't for a stand-alone plugin, but rather for detecting when a new...

If it helps anyone else: for now, I worked around this with a project that uses ember-cli-deploy-lightning-pack, by appending a `` element at the end of `` at the _server_...