Closed ghost closed 3 years ago
Right now profile names make this ambiguous (a profile could be called !include
). Potential solutions:
!
profile
prefix: profile my-profile { … }
"my-profile" { … }
Add a mandatory profile prefix: profile my-profile { … }
I think I'm going to go with this solution. See https://github.com/emersion/kanshi/issues/75
We should now be able to use the top-level include
directive safely.
Superseded by #87
Replaces #53. Could use a check on the path resolution logic to see if it's correct.