FEATURE REQUEST : Disable Autocomplete/Formatting during macro recording
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 15.2k
- Forks
- 1.5k
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 6
Description
Recording macros in vscode vim. intellisense/emmet autocomplete texts in insert mode and places cursor at the right the place. When using the macro the autocomplete works but the cursor is not placed at the same place as during the recording.
Expected Behaviour
The macros that I record should have the exact same behaviour when I'm recording as when I'm running them.
How to reproduce
- Create an empty html file
- Write a word
- Start recording a macro
- copy the word | yw
- insert in a new line | o
- create h1 tags with emmet | h1 tab
- the cursor is placed in the middle of the tags
- Exit insert mode | Esc
- paste the word | p
- the word is correctly placed between the tags like this :
<h1>word</h1> - stop recorgin the macro | q
- run the macro
- the word in incorrectly placed after the tags like this:
<h1></h1>word
Proposed Solution
It seems the Visual Studio vim extension had a similar issue with macros and intellisense. Their proposed solution was to add a setting to disable all form of autocomplete/formating during macro recording.
Environement
- Extension (VsCodeVim) version: v0.10.13 (2018-01-23)
- VSCode version: 1.20.0
- OS version: macOS High Sierra 10.13.2 (17C88)
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 macro mismatch in an empty HTML file using the listed Emmet and insert-mode steps. Then trace the extension's macro recording and replay behavior alongside autocomplete and formatting, and define completion as a setting or mechanism that makes replay match recording without those interventions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100