Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of suggestions to replace all occurrences #23

Closed
libinvarghese opened this issue Jan 22, 2020 · 2 comments
Closed

List of suggestions to replace all occurrences #23

libinvarghese opened this issue Jan 22, 2020 · 2 comments
Assignees
Labels
1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature 3-fixed Issue resolution: Issue has been fixed on the develop branch

Comments

@libinvarghese
Copy link

I usually have multiple instances of the same error. Instead of individually fixing them, it would be great to have an option to replace all occurrence with a fix.

For instance some the errors I usually encounter are:

  1. Consider using an m-dash if you do not want to join two words.
  2. Please add a punctuation mark at the end of paragraph.
  3. This sentence does not start with an uppercase letter
  4. In British English, for some verbs, both ~s and ~z spellings are possible. By default, the rule for Oxford spelling is on for verbs.
@libinvarghese libinvarghese added the 1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature label Jan 22, 2020
@valentjn valentjn self-assigned this Feb 15, 2020
@valentjn
Copy link
Owner

@libinvarghese Great suggestion. This is implemented in the upcoming release of LTEX. To trigger, select a range of text, which contains the LanguageTool diagnostics, and execute Command Palette (usually Ctrl+P) → Quick Fix..., i.e., don't hover with your mouse over the text (you would only be able to fix individual diagnostics this way). You can also use the direct shortcut Ctrl+. instead of Ctrl+PQuick Fix....

@valentjn valentjn added the 3-fixed Issue resolution: Issue has been fixed on the develop branch label Feb 15, 2020
@valentjn
Copy link
Owner

Fixed in 4.7.8.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1-feature-request ✨ Issue type: Request for a desirable, nice-to-have feature 3-fixed Issue resolution: Issue has been fixed on the develop branch
Projects
None yet
Development

No branches or pull requests

2 participants