Welcome to vscode-ltex Discussions!

[valentjn]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

Check out our website for the documentation of LT_EX. Follow these steps if you have a feature request or bug report. If you have a question about LT_EX, read the FAQ at our website and open a discussion in the Q&A category.

If you like, you can comment below with an introduction of yourself and tell us about what you do with this community.

[valentjn]

Hi! I'm the maintainer and main author of LT_EX (which consists of the two repositories vscode-ltex and ltex-ls).

I started LT_EX out of frustation that no good L^AT_EX-capable LanguageTool (LT) frontend was available at that time for VS Code. There was a “LanguageTool extension for VS Code,” but it didn't support L^AT_EX (only Markdown), and the project had been abandoned after the passing of its author Adam Voss. So I forked that extension, which proved to be a great starting point, and after a few days, I had a rudimentary and very basic, but working L^AT_EX parser. LT_EX, as the fork soon was called by combining “LT” and “L^AT_EX”, has seen so many changes since. Its features have become much more extensive, but in its core, Adam's idea of using the Language Server Protocol (LSP) to send documents and receive corrections still lives on.

As the maintainer, I'm responsible for managing issues and pull requests, pushing releases, etc., but as the main author, I'm also working on improving LT_EX by implementing new features and squashing bugs. Just keep in mind that I'm doing this in my spare time 😉