feature request: `noqa: option` to ignore a specific option of a specific line

[tdegeus]

feature request: `noqa: option` to ignore a specific option of a specific line

[cmhughes]

I present two options, both give your desired output.

option 1

Use noIndentBlock as in https://latexindentpl.readthedocs.io/en/latest/sec-fine-tuning.html?highlight=href#lst-href3

onlyOneBackUp: 1
defaultIndent: '    '
removeTrailingWhitespace: 1

modifyLineBreaks:
  commands:
    label:
      CommandStartsOnOwnLine: 1

noIndentBlock:
   subfloat:
     begin: \\subfloat\h*\{\h*\\label\{
     body: [^}]*?
     end: \}\h*\}

option 2

Using the replacement switch as in https://latexindentpl.readthedocs.io/en/latest/sec-replacements.html

onlyOneBackUp: 1
defaultIndent: '    '
removeTrailingWhitespace: 1

modifyLineBreaks:
  commands:
    label:
      CommandStartsOnOwnLine: 1

replacements:
  -
    when: after
    substitution: |-
        s/(\\subfloat\{)\s*(\\label)/$1$2/sg

[tdegeus]

Thanks for the solution! I agree that it is quite nice, and that it could be used in multiple circumstances.

However, I would still plea that the suggestion that I make here is quite nice too. In particular, it does not warrant the user to figure out a regex for every 'edge'-case it wants to ignore for some (but not all) feature of latexindent. Of course, it could be that the implementation of latexindent makes this option very hard?

[cmhughes]

So you want the user to be able annotate lines in their file using a comment such as % noqa: modifyLineBreaks?

[tdegeus]

That is indeed my suggestion, per similarity with common use in Python e.g. with flake8, see e.g. https://stackoverflow.com/questions/45346575/what-does-noqa-mean-in-python-comments .

It is true that latexindent.pl is extremely versatile (likely much more than similar tools used e.g. for Python code). So it seems that even weird edge-cases can be treated in .latexindent.yaml. However, finding the right regular expressions can be more cumbersome than just ignoring a line.

[cmhughes]

OK, understood, it's on the list :)

[cmhughes]

I'm hoping to get to this soon, apologies for the delay :)

Do you have a sense for what the YAML user interface might look like for this?

[cmhughes]

I'm sorry, Tom, but I don't think that this is going to go anywhere.

My experience with the text wrap routine has made me very hesitant to implement a feature that seems simple but actually has a great number of subtleties,and leads to a number of questions, issues, edge cases.

If you, or anyone else, feels like taking this on, then do feel encouraged to submit a pull request. But, for the moment, I'm going to close this.