LT_EX Extension for VS Code: Grammar/Spell Checker with LanguageTool and L^AT_EX/Markdown Support

LT_EX provides offline grammar checking of various markup languages in Visual Studio Code using LanguageTool (LT). LT_EX currently supports L^AT_EX and Markdown documents.

The difference to regular spell checkers is that LT_EX not only detects spelling errors, but also many grammar and stylistic errors such as:

• This is an mistake.
• The bananas is tasty.
• We look forward to welcome you.
• Are human beings any different than animals?

A classic use case of LT_EX is checking scientific L^AT_EX papers in VS Code, but why not check your next blog post, book chapter, or long e-mail before you send it to someone else?

Find more information and documentation about LT_EX on the official website.

LT_EX is a successor (since it's a fork) of the abandoned LanguageTool for Visual Studio Code extension by Adam Voss^†.

Features

• Checks L^AT_EX and Markdown documents
• Comes with everything included, no need to install Java or LanguageTool
• Supports over 20 languages
• Issue highlighting with hover description
• Replacement suggestions via quick fixes
• User dictionaries
• Multilingual support with babel commands or magic comments
• Possibility to use external LanguageTool servers
• Extensive documentation

Requirements

• 64-bit operating system
• VS Code 1.39 or newer
• Optional:
  • If you want to check L^AT_EX documents: LaTeX Workshop Extension for VS Code

How to Use

1. Install the requirements listed above
2. Install this extension (see download options)
3. Reload the VS Code window if necessary
4. Open a L^AT_EX or a Markdown document, or open a new file and change the language mode to LaTeX or Markdown (open the Command Palette and select Change Language Mode)
5. Wait until ltex-ls and Java have been found; if necessary, LT_EX downloads both for you. Alternatively, you can choose offline installation.
6. Grammar/spelling errors will be displayed! (if there are any)

Information & Documentation

• General Information
  • Overview
  • Download — VS Marketplace
  • Code/Issues — GitHub
• Documentation
  • Installation and Usage
    • Requirements
    • Download Providers
    • How to Install and Use
    • Offline Installation
      • First Alternative: Download the Offline Version of LT_EX
      • Second Alternative: Download ltex-ls/Java Manually
  • Advanced Usage
    • Multi-Scope Settings
    • External Setting Files
    • Magic Comments
    • Multilingual L^AT_EX Documents with the babel Package
    • Hiding False Positives with Regular Expressions
    • LanguageTool HTTP Servers
  • Settings
    • ltex.enabled
    • ltex.language
    • ltex.dictionary
    • ltex.disabledRules
    • ltex.enabledRules
    • ltex.hiddenFalsePositives
    • ltex.bibtex.fields
    • ltex.latex.commands
    • ltex.latex.environments
    • ltex.markdown.nodes
    • ltex.configurationTarget
    • ltex.additionalRules.enablePickyRules
    • ltex.additionalRules.motherTongue
    • ltex.additionalRules.languageModel
    • ltex.additionalRules.neuralNetworkModel
    • ltex.additionalRules.word2VecModel
    • ltex.ltex-ls.path
    • ltex.ltex-ls.languageToolHttpServerUri
    • ltex.ltex-ls.logLevel
    • ltex.java.path
    • ltex.java.forceTrySystemWide
    • ltex.java.initialHeapSize
    • ltex.java.maximumHeapSize
    • ltex.sentenceCacheSize
    • ltex.diagnosticSeverity
    • ltex.checkFrequency
    • ltex.clearDiagnosticsWhenClosingFile
    • ltex.statusBarItem
    • ltex.trace.server
  • Commands
    • LTeX: Check Selection
    • LTeX: Check Current Document
    • LTeX: Check All Documents in Workspace
    • LTeX: Clear Diagnostics in Current Document
    • LTeX: Clear All Diagnostics
    • LTeX: Show Status Information
    • LTeX: Report Bug in LTeX
    • LTeX: Request Feature for LTeX
  • FAQ
    • What's the difference between vscode-ltex, ltex-ls, and LanguageTool?
    • What happened to the Language Support Extensions?
    • How can I prevent LT_EX from redownloading ltex-ls and Java after every update?
    • Why does LT_EX have such a high CPU load?
    • Where does LT_EX save its settings (e.g., dictionary, false positives)?
    • How can I check multiple languages at once?
    • How can I fix multiple spelling errors at the same time?
    • How can I prevent \text{...} in math mode from producing false positives?
    • What does LT_EX stand for?
    • Where can I ask a question that's not answered here?
  • Changelog
  • Contributing Code/Issues
    • Ways of Contribution
    • How to Report Bugs
      • Known Issues and Limitations
    • How to Request Features
    • How to Contribute Code
      • Branches & Pull Requests
      • Code Checks
      • Versioning
      • Pre-Releases
      • Documentation
      • Internationalization (I18n)
    • Contribution Guidelines
      • Guidelines About Issues
      • Guidelines About Versioning
      • Guidelines About Fundamental Changes
  • Code of Conduct
    • Our Pledge
    • Our Standards
    • Enforcement Responsibilities
    • Scope
    • Enforcement
    • Enforcement Guidelines
      • 1. Correction
      • 2. Warning
      • 3. Temporary Ban
      • 4. Permanent Ban
    • Attribution
  • Acknowledgments
    • LanguageTool Extension for Visual Studio Code
    • ltex-ls