Lukáš Zachar

> This is question. On first singht, I can imagine that TMT will interpret the value, but another is, that it is semantic of FMF, so that it should be...

> BTW, this disussion is closer to FMF/TMT config/profiles (#196) than we should allow :-), it allows you to configure/override default FMF behaviour, I beg do differ - for me...

Hm, I'll leave the `mark-non-leaf` feature to the future. As it changes the flow of creating the tree a lot -- if I understood correctly such nodes will be effectively...

Could you please create a new issue, @LecrisUT ? What I have in mind is this: ``` . ├── bar │   └── main.fmf ├── .fmf │   └── version ├── foo.fmf...

> You mean the opposite right? non-leaf `/` and `/foo`, `/bar` are leaves (in the current implementation, and discussion does not touch the current implementation right?) Right you are, I...

PR rebased, in the end I went with 'select' as directive name as it made more sense in the docs.

We need to document - implementation sorts keys - https://github.com/teemtee/fmf/blob/29190c78e4065adf98cbb3ccf747b01973d761e2/fmf/base.py#L222C1-L222C50

Ack, coverage should be added as mistakes in refactor might happen.

So `re.sub` doesn't work as expected, or? I'd assume that it intention is to 'undo' the escaping. BTW it would be really good to see this covered in unit tests......

+1 for this, should be very useful