Consider moving all config files into .config

[joshfriend]

Then either:

• update the Makefile to provide paths into .config
• have the Makefile create symlinks to the root

[joshfriend]

I was able to move 5 files into the new .config directory:

.coveragerc
.noserc
.project
.pydevproject
Foobar.sublime-project

[jacebrowning]

@joshfriend is there any reason the *.sublime-project needs to be symlinked?

[joshfriend]

@jacebrowning not really. I just did it in the interest of moving as many files as possible out of the project root.

[jacebrowning]

@joshfriend why not keep the *.sublime-project in .config and not symlink it? Sublime doesn't care where the project file is, but might potentially get confused about relative paths if the project is symlinked.

[jacebrowning]

@joshfriend problem! The arguments for mklink are reverse that of ln.

[joshfriend]

I think i'm 👎 on this now. the only real utility in this was that there would be less files in the repo root so more of the README would show on the github page.

[jacebrowning]

I agree.