Looper config default filename: start with a dot?

[nsheff]

Right now, we made the default looper config named .looper.yaml. I'm wondering if having it start with a dot is a good idea.

Pros:

• it sorts alphabetically at the top
• indicates visually that this file is special

Cons:

• it's hidden by many file managers
• it's also not visible by default with ls, you have to use ls -a.

What do others do? There's a mix; for example, git uses a .git folder, and .gitignore files. Also, there's .readthedocs.yaml. But many tools use files without a dot prefix, such as mkdocs (mkdocs.yaml), and poetry uses pyproject.toml.

Should we keep it as .looper.yaml or switch to looper.yaml ?

[donaldcampbelljr]

What about removing the dot but adjust it to be in capital case? LOOPER.yaml It would signal that this file is important.

[nsheff]

Ok, but I don't love all caps because I can't think of any other tools that use all caps... I guess there's the "README.md" and "LICENSE" but those seem somehow different...

[nsheff]

every tool I can think of that uses a configuration file uses lowercase.

[khoroshevskyi]

In my point of view, .looper.yaml is a file that is pointing to actual looper_config.yaml file. We were doing same with PEP, .pep.yaml. eg. .pep.yaml . So now, I pushed to dev same configuration, .looper.yaml is file that is pointing to actual config. Related to: #410 Additionally, same configuration was in looper==1.4.X What do you think about that?

[khoroshevskyi]

And how you can run it: if you have .looper.yaml (File that is pointing to actual looper_config), then you can do this: looper run if you have only looper config, then: looper run --looper-config {path_to_looper_config}

[nsheff]

No, this makes no sense to me.

The .looper.yaml file is the looper config file. It doesn't point to the looper config file. It is the looper config file. To me, there is no value whatsoever in separating these, and it adds a lot of confusion and extra overhead.

We were doing it that way with the PEP because the looper config file is not the same thing as the PEP config file.

[nsheff]

A lot of this was already discussed and decided a few months ago, please see #344 and #342

[nsheff]

I don't really see a compelling reason to change, so let's just leave it as .looper.yaml. for future reference, I think I have a slight preference for _looper.yaml, but maybe not enough to change the way it is.