You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use VS Code problem matchers to automatically add spelling issues to the Problems Pane in VS Code based on the output of this extension. Currently, the extension will only provide a line number for the spelling error. It would be very useful to also have the column number where the misspelled word starts, so that when selecting the error in the Problems pane my cursor jumps directly to the beginning of misspelled word.
I would propose simply adding the column number to be right after the line number, and separated with a colon.
Current error message:
\path\to\mistake:3: Spell check: useable: ["usable", "use able", "use-able", "saleable", "sublease"]: This might not be useable yet
Proposed addition of column:
\path\to\mistake:3:19: Spell check: useable: ["usable", "use able", "use-able", "saleable", "sublease"]: This might not be useable yet
The text was updated successfully, but these errors were encountered:
I use VS Code problem matchers to automatically add spelling issues to the Problems Pane in VS Code based on the output of this extension. Currently, the extension will only provide a line number for the spelling error. It would be very useful to also have the column number where the misspelled word starts, so that when selecting the error in the Problems pane my cursor jumps directly to the beginning of misspelled word.
I would propose simply adding the column number to be right after the line number, and separated with a colon.
Current error message:
Proposed addition of column:
The text was updated successfully, but these errors were encountered: