Incorrect formatting with `gqq` in Markdown
Open
Nobody has claimed this yet.
help wanted
kind/bug
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
To Reproduce
- Paste the following text into a buffer:
*foo* bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar
- Press gqq and see the following (notice the leading asterisk on the second line):
*foo* bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar
*bar bar bar bar bar bar bar bar bar bar
Expected behavior
As in Vim, the result should be
*foo* bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar bar
bar bar bar bar bar bar bar bar bar bar
Environment (please complete the following information):
- Extension (VsCodeVim) version: 0.16.9
- VSCode version: 1.28.0
- OS: macOS
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the Markdown example with gqq in VSCodeVim and compare it with Vim's result. Trace the gqq formatting entry point and its Markdown handling; done means the leading asterisk is not introduced on the continuation line and the reproduction matches the expected output.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vim, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100