Skip to content
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

Make --no-color in ~/.rspec should project settings #737

Closed
dolzenko opened this issue Nov 23, 2012 · 2 comments
Closed

Make --no-color in ~/.rspec should project settings #737

dolzenko opened this issue Nov 23, 2012 · 2 comments

Comments

@dolzenko
Copy link

E.g. if I have

/home/dolzenko/ $ cat .rspec
--no-color

/home/dolzenko/myproject/ $ cat .rspec
--color

and I run specs for myproject I would expect RSpec not to use colorized output, does that make sense?

@dchelimsky
Copy link
Contributor

It actually works the opposite way quite intentionally. The idea is that you set up general settings in ~/.rspec and override them locally with project-specific settings (in ./.rspec). This is similar to how at least some other command line tools work (e.g. git), though I'm sure you could find others that work the opposite way.

To solve the problem of overriding team preferences on a given project with your personal preferences, we added support for a ./.rspec-local file in rspec-2.12. The intent is that you add it to .gitignore, so it only impacts your machine.

I just added #738 to remind us to document .rspec-local (right now it's only mentioned in the Changelog.

@dolzenko
Copy link
Author

David, that's a good stuff, thanks for explanation!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants