t9md / atom-vim-mode-plus

vim-mode improved

Home Page:https://atom.io/packages/vim-mode-plus

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

replacing characters via r in .go files does not work in unsaved files

xh3b4sd opened this issue · comments

debug info
{
  "atom": "1.45.0",
  "platform": "darwin",
  "release": "19.4.0",
  "vmpVersion": "1.36.4",
  "vmpConfig": {
    "useClipboardAsDefaultRegister": false
  }
}

Relevant packages I use:

Checklist

You have to check all before open issue.

  • Provide your environment info clipped by Vim Mode Plus: Clip Debug Info command.
  • Try with latest Atom and latest vim-mode-plus.
  • Pick a descriptive and non-ambiguous subject
  • Express "what" you want(feature? config option?, behavior change?) in short sentence(not long!).
  • Contrast current behavior if you want to change current behavior, with sample text, operation(keystroke) and result.
  • Include real use case so that maintainer can understand "why" you need help.
  • Include Atom(atom --version), vim-mode-plus version, and OS version(e.g. macOS Sierra 10.12.3).
  • If keybinding issue, Read this.

what I want

reporting a bug

current vs desired behaviour

I have a simple go file, go-plus and autosave enabled. Cursor above x in the comment.

package x

// x

Hitting r and then e replaces x with e. The file changed. Again hitting r and then x does not replace e with x, but it should. When I disable either of go-plus or autosave packages the second attempt of replacing e with x works as expected.

use case

I replace a lot of characters every day and run a lot into the issue for quite some time now. I finally made the effort to report the bug.

more thoughts

I checked the key bindings and they do not seem to be the issue. I tried to debug the JS code but this is not my expertise at all so I couldn't really figure anything. I would maybe be interested in learning a bit more so I can be more helpful here since I rely heavily on vim-mode-plus. I like it a lot.

commented

Thank you for the kind comment. Btw, Have you reported this issue to go-plus?
I tried with autosave enabled, but I couldn't reproduce. So I think go-plus is somewhat related to this issue.
Plus your debug info is super short, did you pasted the clipboard result which you captured "Vim Mode Plus: Clip Debug Info" command ?

I did not report it further, but I can raise it with go-plus. I checked the debug info again and it copies the same. I do not get more out of it.

commented

OK, for the Clip Debug Info command, you are right. The length of output just depends on what amount of configuration you have changed from the default.

Created the other issue. See joefitzgerald/go-plus#1012.