Florian Schanda

@phiwuu I think two options make sense: 1. (my preferred) broaden this to cover any and all names, so it would also cover type names, enumeration literals, record fields, etc....

You can add an `options` file to the test and specify `--no-detailed-info` See https://github.com/bmw-software-engineering/trlc/blob/main/tests-system/lint-vcg-strings/options for an example.

Can you provide a bit more to reproduce this please? I assume this is API related?

Obsoleted by https://github.com/bmw-software-engineering/trlc/pull/87

I think instead of just coding something it would be good to first define on #12 what this actually means. I can think of several interfaces: * a section iterator,...

Excellent, thank you for the detailed answer! So just to confirm, you're not following the [ferrocene lrm](https://public-docs.ferrocene.dev/main/specification/index.html) in any way? I suppose if they want to have Kani support, then...

Sounds like an interesting idea. It's been a while since I touched the indent code so not sure how easy it'll be but I'll see what can be done.

Right now this is not possible, but I think there are two options that could be implemented: * an exclude_file config entry * a pragma comment to ignore the entire...

This should be easy to do, and honestly I thought it would work like that already.

This was kinda intentional, to allow people to do horizontal layout, e.g. ```matlab [1, 500 2, 0] ``` We could have a better or configurable rule that lays things out...