fix ltrs

[cxwx]

What does this PR do?

ltrs running bug

#334

Checklist

• If I'm adding a new builtin (linter, formatter, code action, etc.), I
  understand it should be contributed to
  nvimtools/none-ls-extras.nvim
  instead
• I've written tests for these changes

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository. Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 92aa3c1c-4f98-4e52-8916-e381f378434f

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[mochaaP]

could you provide the commit where ltrs changed behavior and include it in the commit msg? thanks

[cxwx]

could you provide the commit where ltrs changed behavior and include it in the commit msg? thanks能否提供 ltrs 更改行为的提交记录，并将其包含在提交信息中？谢谢。
I'm new to LTRS and can't find more information, sorry.

install languagetool-rust by homebrew,
I cannot find the '-m' argument

╰─ ltrs  check  --help
Check text using LanguageTool server

Usage: ltrs check [OPTIONS] [FILENAMES]...

Arguments:
  [FILENAMES]...
          Optional filenames from which input is read

Options:
  -r, --raw
          If present, raw JSON output will be printed instead of annotated text. This has no effect if `--data` is used, because it is never annotated

      --max-length <MAX_LENGTH>
          Sets the maximum number of characters before splitting

          [default: 1500]

      --split-pattern <SPLIT_PATTERN>
          If text is too long, will split on this pattern

          [default: "\n\n"]

      --max-suggestions <MAX_SUGGESTIONS>
          Max. number of suggestions kept. If negative, all suggestions are kept

          [default: 5]

      --type <TYPE>
          Specify the files type to use the correct parser.

          If set to auto, the type is guessed from the filename extension.

          Possible values:
          - auto:     Auto
          - raw:      Raw text
          - markdown: Markdown
          - html:     HTML
          - typst:    Typst

          [default: auto]

  -h, --help
          Print help (see a summary with '-h')

  -V, --version
          Print version

Request options:
  -t, --text <TEXT>
          The text to be checked. This, `data`, or `[FILENAMES...]` cannot be passed simultaneously. If nothing is specified, input will be read from `stdin`

  -d, --data <DATA>
          The text to be checked, given as a JSON document that specifies what's text and what's markup. This or 'text' is required.

          Markup will be ignored when looking for errors. Example text: ```html A <b>test</b> ``` JSON for the example text: ```json {"annotation":[ {"text": "A "},
          {"markup": "<b>"}, {"text": "test"}, {"markup": "</b>"} ]} ``` If you have markup that should be interpreted as whitespace, like `<p>` in HTML, you can have it
          interpreted like this:

          ```json {"markup": "<p>", "interpretAs": "\n\n"} ``` The 'data' feature is not limited to HTML or XML, it can be used for any kind of markup. Entities will need
          to be expanded in this input.

  -l, --language <LANGUAGE>
          A language code like `en-US`, `de-DE`, `fr`, or `auto` to guess the language automatically (see `preferredVariants` below).

          For languages with variants (English, German, Portuguese) spell checking will only be activated when you specify the variant, e.g. `en-GB` instead of just `en`.

          [default: auto]

  -u, --username <USERNAME>
          Set to get Premium API access: Your username/email as used to log in at languagetool.org

          [env: LANGUAGETOOL_USERNAME=]

  -k, --api-key <API_KEY>
          Set to get Premium API access: your API key (see <https://languagetool.org/editor/settings/api>)

          [env: LANGUAGETOOL_API_KEY=]

      --dicts <DICTS>
          Comma-separated list of dictionaries to include words from; uses special default dictionary if this is unset

      --mother-tongue <MOTHER_TONGUE>
          A language code of the user's native language, enabling false friends checks for some language pairs

      --preferred-variants <PREFERRED_VARIANTS>
          Comma-separated list of preferred language variants.

          The language detector used with `language=auto` can detect e.g. English, but it cannot decide whether British English or American English is used. Thus this
          parameter can be used to specify the preferred variants like `en-GB` and `de-AT`. Only available with `language=auto`. You should set variants for at least
          German and English, as otherwise the spell checking will not work for those, as no spelling dictionary can be selected for just `en` or `de`.

      --enabled-rules <ENABLED_RULES>
          IDs of rules to be enabled, comma-separated

      --disabled-rules <DISABLED_RULES>
          IDs of rules to be disabled, comma-separated

      --enabled-categories <ENABLED_CATEGORIES>
          IDs of categories to be enabled, comma-separated

      --disabled-categories <DISABLED_CATEGORIES>
          IDs of categories to be disabled, comma-separated

      --enabled-only
          If true, only the rules and categories whose IDs are specified with `enabledRules` or `enabledCategories` are enabled

      --level <LEVEL>
          If set to `picky`, additional rules will be activated, i.e. rules that you might only find useful when checking formal text

          Possible values:
          - default: Default level
          - picky:   Picky level

          [default: default]

Server options:
  -v, --verbose...
          Increase logging verbosity

  -q, --quiet...
          Decrease logging verbosity