cheshirekow

`--config-file` takes multiple arguments. My guess is you wrote something like: ``` cmake-format --config-file /tmp/cmake-format.py /tmp/bad.cmake ``` But you should use ``` cmake-format --config-file /tmp/cmake-format.py -- /tmp/bad.cmake ``` (note the...

This is quite possible.

I was in the process of implementing this and it seems kind of silly to add a configuration option for such a specific case. I also don't like introducing any...

Personally I don't particularly mind single hash though I don't generally write uncommented function definitions. Regardless, for this feature: Would the desired behavior be: > Insert `n` spaces before a...

Hi, thanks for the contribution! I think the layout model is a little different than you've understood it. This acts a little bit like cmake-format did in it's first version,...

Dealing with this specific formatting has actually been quite challenging. The problem is that it's really hard to come up with appropriate rules using only the position in the argument...

Sorry about that. I think I fixed the package. `v0.6.13` is uploaded to pypi and the problem appears to be resolved. I'll leave the issue open for a little while...

Hm... I'll need to think about this a bit. Honestly, I would consider this lint, it can be addressed by, e.g.: ``` set(_base_url https://gitlab-mirror-ir.long.corporate.domain.com/longgroup) ExternalProject_Add( mything GIT_REPOSITORY ${_base_url}/path/to/somewhere/myteam/mything.git GIT_SHALLOW ON...

> It's the same as long links for cmake-format (#195, #182), No, this is really different. Those other issues are about whether or not `cmake-format` should modify existing text content,...

Some notes (mostly to self): Currently this check is implemented during the first phase of checks before even lexing the input file. In order to implement this feature, this check...