Emilv2

> OK, I'm just thinking about being consistent: Any linux tool that I know interprets . as the current directory, and e.g. ls . will list you all the files...

I see your point, but I don't think it's inconsistent since `.*.vhd` doesn't match the directory. (I don't even think most shells (and python?) make `.*` match `.` but I'm...

I don't think this should be rushed, better take some time to decide what we want to put in and be sure it works.

Any updates on this? I personally like the way [isort](https://pycqa.github.io/isort/docs/configuration/config_files/) deals with this. VSG could do this for every file it encounters to allow for different coding standards, but is...

Do you accept contributions? What I personally would require of (both automatic discovery and supplying with `--configuration`) configuration: 1. running vsg on a file with the same configuration file should...

> -lr .vsg/rules: As VSG allows, one can define user rules. About that, it's not very clear to me yet what the difference between a `local_rules` file and a configuration...

>I can not remember why I added the file_list to the configuration. It was probably because I wanted to reduce the --filename command line option. With the number of options,...

>I'd say there is no need to implement sth. new since this feature already exists: Simply use the -oc option to dump the configuration. I would think warning about setting...

> Either explicit or implicit behavior could be inferred from the `--filename` and `--configuration` command line arguments. > > ``` > --filename | --configuration | Action > --------------------+----------------------+------------- > not...

>What are the details for finding the working copy root? I think on SVN you can get it with svn status . Checking for `.git`, `.hg` or `.svn` folders should...