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
Hi, I am reporting a similar behavior to #184 : redo is taking me to the top of the file.
Do you want to request a feature or report a bug?
Report a bug.
What is the current/expected behavior?
Current behavior:
When I press u after :Prettier, the cursor correctly stays where the last change was made. However when I press Ctrl-r after that the cursor jumps to the top line.
Expected behavior:
The cursor stays where the change was made.
What version of vim-prettier are you using - (output of :PrettierVersion) ?
1.0.0-alpha
What version of prettier are you using - (output of :PrettierCliVersion) ?
1.19.1
What is your prettier executable path - (output of :PrettierCliPath) ?
./node_modules/.bin/prettier
Did this work in previous versions of vim-prettier and/or prettier ?
No, I've been experiencing this issue since 2017. (version 0.2.6)
Hi, I am reporting a similar behavior to #184 : redo is taking me to the top of the file.
Do you want to request a feature or report a bug?
Report a bug.
What is the current/expected behavior?
Current behavior:
When I press
u
after:Prettier
, the cursor correctly stays where the last change was made. However when I pressCtrl-r
after that the cursor jumps to the top line.Expected behavior:
The cursor stays where the change was made.
What version of vim-prettier are you using - (output of :PrettierVersion) ?
1.0.0-alpha
What version of prettier are you using - (output of :PrettierCliVersion) ?
1.19.1
What is your prettier executable path - (output of :PrettierCliPath) ?
./node_modules/.bin/prettier
Did this work in previous versions of vim-prettier and/or prettier ?
No, I've been experiencing this issue since 2017. (version 0.2.6)
Here is my
vim --version
:And I am attaching screencast doing the following:
:Prettier
u
Ctrl-r
The text was updated successfully, but these errors were encountered: