config csslintrc path with command line

[popomore]

Is there any option in command line, I can use global .csslintrc.

Something like

csslint --config path/to/csslinrc

[apennebaker]

csslint automatically attempts to load command line flags from a .csslintrc file in the current working directory. No need to specify --config path/to/csslintrc.

https://github.com/stubbornella/csslint/wiki/Command-line-interface#configuration-files

See my .csslintrc for a working example.

[popomore]

I mean the global .csslintrc used by all project, not the working directory.

[apennebaker]

@popomore That's a neat idea, I like it.

If no .csslintrc file is found in the current directory, could csslint look up parent directories, until it gets to HOME (~) or root (/)? JSHint does this, and it's wonderful.

[popomore]

Year, that's good. 

Jshint also support --config that could place jshintrc to any other directory.
—
Sent from Mailbox for iPhone

On Fri, Jan 17, 2014 at 12:36 AM, apennebaker notifications@github.com
wrote:

@popomore That's a neat idea, I like it.

If no .csslintrc file is found in the current directory, could csslint look up parent directories, until it gets to HOME (~) or root (/)? JSHint does this, and it's wonderful.

Reply to this email directly or view it on GitHub:
#449 (comment)

[alexilyaev]

I was just going to open a ticket for that :-).

Considering a case where different css files are located in different folders, it would be logical to have a global .csslintrc file at the root of the project (similar to how it's done with a .jshintrc file).

That would require CSSLint to search not only in the current working directory, but also go up the directory tree to find the config file. As in JSHint:

In case of .jshintrc, JSHint will look for this file in the current working directory and, if not found, will move one level up the directory tree all the way up to the filesystem root.

http://www.jshint.com/docs/

Note that JSHint also supports a --config flag to point to the config file manually, which is what was requested by @popomore.

[aparajita]

Most linters start from the linted files's directory or the current working directory and traverse up to root. If the config file is not found, then they look in $HOME.

[aparajita]

But in concert with this it's important to have a --config option in case the user wants to use some other location.

[apennebaker]

Maybe we should separate these into two different feature requests:

• By default, look for and apply .csslintrc configuration in the current
  directory up to the user's home directory, or the root directory, whichever
  comes first.
• Offer a command line option to manually specify a path to configuration.

On Wed, Jan 22, 2014 at 4:51 PM, Aparajita Fishman <notifications@github.com

wrote:

But in concert with this it's important to have a --config option in case
the user wants to use some other location.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/449#issuecomment-33072503
.

Cheers,

Andrew Pennebaker
apennebaker@42six.com

[popomore]

Any response?

[blatyo]

I would love a --config option. My specific use case is that I'm bundling up a bunch of style checkers with their configuration into a gem which my company uses on it's projects. The configuration would be in the gem, which would not be in any parent directories or home.

Using sublime Text, I would like to be able to put a .csslintrc config in my project root, but that wont work with sublime-linter because it runs csslint from the directory of the document being linted. So if csslint could look back up along the document tree to my project root to find the config file, things would work much better with sublime-linter.
As people have already mentioned, this is the way jshint does it, and it works great with sublime-linter.

[popomore]

ping @stubbornella