VSCodeVim / VSCodeVim/Vim

`:y` command marks file as dirty/unsaved

Open
#4,964 1 comment 0 reactions 1 assignee View on GitHub

@J-Fields is already working on this.

Since Jun 24, 2020.

area/neovim kind/bug
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

Describe the bug
Using the :y command (or similar, e.g.: :%y) marks a file as dirty/unsaved, despite not altering its contents in any way.

To Reproduce

  1. Open or create a file with some content
  2. Make sure that the file is saved (:w)
  3. Use the :y command
  4. File is now marked as not saved
  5. Use :q
  6. E37: No write since last change (add ! to override)

Expected behavior
Using the :y command should keep the file in whatever state it currently is as it does not alter its contents in any way.

Environment (please complete the following information):

  • Extension (VsCodeVim) version: 1.14.5
  • VSCode version: 1.46.1
  • OS: Ubuntu 20.04

Additional context
Using the regular y keybind (rather than the command :y) does not have this issue.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.