This repository has been archived by the owner. It is now read-only.

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no lon... #713

Closed
jbiason opened this Issue Jun 25, 2015 · 47 comments

Comments

Projects
None yet
@jbiason

jbiason commented Jun 25, 2015

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 0.211.0
System: Ubuntu 14.04.2
Thrown From: vim-mode package, v0.53.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /home/julio.biason/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
  at Error (native)
  at /home/julio.biason/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
  at Emitter.module.exports.Emitter.emit (/home/julio.biason/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
  at VimState.module.exports.VimState.pushOperations (/home/julio.biason/.atom/packages/vim-mode/lib/vim-state.coffee:213:18)
  at atom-text-editor.commands.(anonymous function) (/home/julio.biason/.atom/packages/vim-mode/lib/vim-state.coffee:196:45)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/atom/resources/app.asar/src/command-registry.js:241:29)
  at /opt/atom/resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/opt/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:520:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/opt/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:355:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/opt/atom/resources/app.asar/src/window-event-handler.js:180:20)

Commands

     -0:24.9.0 vim-mode:activate-command-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:24.5.0 editor:move-to-end-of-screen-line (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -0:24 vim-mode:insert-after-end-of-line (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -0:23.2.0 vim-mode:activate-command-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:23 ex-mode:open (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -0:23 blur (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -0:22.8.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  4x -0:22.8.0 blur (atom-text-editor.editor.mini.is-focused)
  2x -0:03.4.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.command-mode.is-focused)
     -0:01.6.0 vim-mode:put-after (atom-text-editor.editor.vim-mode.command-mode.is-focused)
     -0:01.1.0 vim-mode:delete (atom-text-editor.editor.vim-mode.command-mode.is-focused)
     -0:01.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:01.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:00.4.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.command-mode)
  3x -0:00.4.0 blur (atom-text-editor.editor.vim-mode.is-focused.command-mode)
     -0:00.0 vim-mode:activate-insert-mode (atom-text-editor.editor.vim-mode.is-focused.command-mode)

Config

{
  "core": {
    "disabledPackages": [
      "atom-pair",
      "cute-cursor",
      "language-syntax-settings",
      "minimap",
      "block-cursor",
      "editorconfig"
    ],
    "audioBeep": false,
    "autoHideMenuBar": true,
    "themes": [
      "one-dark-ui",
      "mustang"
    ]
  },
  "vim-mode": {
    "useClipboardAsDefaultRegister": true
  }
}

Installed Packages

# User
clang-format, v1.14.0
docblockr, v0.7.2
docs-snippets, v0.8.0
emmet, v2.3.10
ex-mode, v0.5.1
highlight-line, v0.11.0
language-cmake, v0.1.4
language-yang, v0.2.0
linter, v1.0.4
linter-clang, v2.26.0
linter-pep8, v0.2.0
mustang, v0.1.0
tab-control, v0.6.6
vim-mode, v0.53.0

# Dev
No dev packages
@yriveiro

This comment has been minimized.

Show comment
Hide comment
@yriveiro

yriveiro Aug 31, 2015

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 1.0.9
System: Mac OS X 10.10.5
Thrown From: vim-mode package, v0.59.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/yriveiro/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
  at Error (native)
  at /Users/yriveiro/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
  at Emitter.module.exports.Emitter.emit (/Users/yriveiro/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
  at VimState.module.exports.VimState.pushOperations (/Users/yriveiro/.atom/packages/vim-mode/lib/vim-state.coffee:225:18)
  at atom-text-editor.commands.(anonymous function) (/Users/yriveiro/.atom/packages/vim-mode/lib/vim-state.coffee:207:45)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:245:29)
  at /opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:524:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:347:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:177:20)

Commands

     -0:34.8.0 core:paste (atom-text-editor.editor.vim-mode.insert-mode.is-focused)
  2x -0:34.6.0 core:save (atom-text-editor.editor.vim-mode.insert-mode.is-focused)
     -0:07.9.0 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.insert-mode.is-focused)
  2x -0:07.5.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:06.9.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:06.6.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  4x -0:06.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.2.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  2x -0:05.0 blur (atom-text-editor.editor.mini)
     -0:04.4.0 snippets:next-tab-stop (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.4.0 snippets:expand (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.4.0 docblockr:parse-tab (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.4.0 editor:indent (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.3.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:00.5.0 vim-mode:activate-insert-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "disabledPackages": [
      "autocomplete",
      "meteor-api",
      "meteor-helper",
      "meteor-snippets",
      "git-tab-status",
      "color-tabs",
      "hyperclick",
      "sourcegraph-atom",
      "racer"
    ],
    "themes": [
      "atom-dark-ui",
      "seti-syntax"
    ]
  },
  "vim-mode": {
    "useClipboardAsDefaultRegister": true
  }
}

Installed Packages

# User
atom-beautify, v0.28.11
atom-cli-diff, v1.1.0
atom-html-preview, v0.1.11
atom-jade, v0.3.0
autocomplete-paths, v1.0.2
autocomplete-php, v0.3.7
autocomplete-phpunit, v1.0.2
color-picker, v2.0.11
css-color-underline, v1.0.1
docblockr, v0.7.3
file-icons, v1.6.9
git-diff-details, v0.20.0
go-plus, v3.5.1
highlight-line, v0.11.0
inline-messenger, v1.2.8
language-rust, v0.4.4
linter, v1.4.3
linter-jsonlint, v0.1.4
linter-php, v1.0.3
linter-rust, v0.2.8
linter-shellcheck, v1.0.1
local-history, v3.2.3
markdown-format, v2.5.1
minimap, v4.13.2
minimap-git-diff, v4.1.8
php-debug, v0.1.3
phpunit, v1.1.1
pigments, v0.12.0
pretty-json, v0.4.1
rust-api-docs-helper, v0.5.1
seti-syntax, v0.4.0
sort-lines, v0.11.0
synced-sidebar, v0.4.0
tool-bar, v0.1.8
travis-ci-status, v0.17.0
vim-mode, v0.59.0
wakatime, v4.0.16

# Dev
No dev packages

yriveiro commented Aug 31, 2015

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 1.0.9
System: Mac OS X 10.10.5
Thrown From: vim-mode package, v0.59.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/yriveiro/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
  at Error (native)
  at /Users/yriveiro/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
  at Emitter.module.exports.Emitter.emit (/Users/yriveiro/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
  at VimState.module.exports.VimState.pushOperations (/Users/yriveiro/.atom/packages/vim-mode/lib/vim-state.coffee:225:18)
  at atom-text-editor.commands.(anonymous function) (/Users/yriveiro/.atom/packages/vim-mode/lib/vim-state.coffee:207:45)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:245:29)
  at /opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:524:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:347:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/opt/homebrew-cask/Caskroom/atom/latest/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:177:20)

Commands

     -0:34.8.0 core:paste (atom-text-editor.editor.vim-mode.insert-mode.is-focused)
  2x -0:34.6.0 core:save (atom-text-editor.editor.vim-mode.insert-mode.is-focused)
     -0:07.9.0 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.insert-mode.is-focused)
  2x -0:07.5.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:06.9.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:06.6.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  4x -0:06.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.2.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  2x -0:05.0 blur (atom-text-editor.editor.mini)
     -0:04.4.0 snippets:next-tab-stop (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.4.0 snippets:expand (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.4.0 docblockr:parse-tab (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.4.0 editor:indent (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.3.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:00.5.0 vim-mode:activate-insert-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "disabledPackages": [
      "autocomplete",
      "meteor-api",
      "meteor-helper",
      "meteor-snippets",
      "git-tab-status",
      "color-tabs",
      "hyperclick",
      "sourcegraph-atom",
      "racer"
    ],
    "themes": [
      "atom-dark-ui",
      "seti-syntax"
    ]
  },
  "vim-mode": {
    "useClipboardAsDefaultRegister": true
  }
}

Installed Packages

# User
atom-beautify, v0.28.11
atom-cli-diff, v1.1.0
atom-html-preview, v0.1.11
atom-jade, v0.3.0
autocomplete-paths, v1.0.2
autocomplete-php, v0.3.7
autocomplete-phpunit, v1.0.2
color-picker, v2.0.11
css-color-underline, v1.0.1
docblockr, v0.7.3
file-icons, v1.6.9
git-diff-details, v0.20.0
go-plus, v3.5.1
highlight-line, v0.11.0
inline-messenger, v1.2.8
language-rust, v0.4.4
linter, v1.4.3
linter-jsonlint, v0.1.4
linter-php, v1.0.3
linter-rust, v0.2.8
linter-shellcheck, v1.0.1
local-history, v3.2.3
markdown-format, v2.5.1
minimap, v4.13.2
minimap-git-diff, v4.1.8
php-debug, v0.1.3
phpunit, v1.1.1
pigments, v0.12.0
pretty-json, v0.4.1
rust-api-docs-helper, v0.5.1
seti-syntax, v0.4.0
sort-lines, v0.11.0
synced-sidebar, v0.4.0
tool-bar, v0.1.8
travis-ci-status, v0.17.0
vim-mode, v0.59.0
wakatime, v4.0.16

# Dev
No dev packages
@jacekkopecky

This comment has been minimized.

Show comment
Hide comment
@jacekkopecky

jacekkopecky Aug 31, 2015

Contributor

@yriveiro do you, by any chance, have a way of reproducing this, please?

Contributor

jacekkopecky commented Aug 31, 2015

@yriveiro do you, by any chance, have a way of reproducing this, please?

@yriveiro

This comment has been minimized.

Show comment
Hide comment
@yriveiro

yriveiro Aug 31, 2015

I'm sorry but no :( , it was a random error when pasting code with [dd + p] combination.

yriveiro commented Aug 31, 2015

I'm sorry but no :( , it was a random error when pasting code with [dd + p] combination.

@rinkpijpker

This comment has been minimized.

Show comment
Hide comment
@rinkpijpker

rinkpijpker Oct 28, 2015

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 1.0.19
System: Mac OS X 10.11.1
Thrown From: vim-mode package, v0.62.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/rinkpijpker/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
  at Error (native)
  at /Users/rinkpijpker/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
  at Emitter.module.exports.Emitter.emit (/Users/rinkpijpker/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
  at VimState.module.exports.VimState.pushOperations (/Users/rinkpijpker/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
  at atom-text-editor.commands.(anonymous function) (/Users/rinkpijpker/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:245:29)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:524:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:347:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:184:20)

Commands

     -2:31.4.0 command-palette:toggle (atom-text-editor.editor.mini.is-focused)
     -2:30 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -2:30 core:cancel (atom-text-editor.editor.mini.is-focused)
     -2:28.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -1:59.1.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -0:17.2.0 fuzzy-finder:toggle-file-finder (div.settings-view.pane-item)
     -0:15.8.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:15.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:12 core:close (div.settings-view.pane-item)
     -0:04.6.0 vim-mode:find (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:03.6.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:03.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:02.2.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:02.2.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:01.7.0 vim-mode:till (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.6.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "themes": [
      "nucleus-dark-ui",
      "batman-syntax"
    ]
  }
}

Installed Packages

# User
batman-syntax, v1.0.1
emmet, v2.3.13
file-type-icons, v0.7.3
linter, v1.9.1
minimap, v4.15.0
nucleus-dark-ui, v0.6.6
pigments, v0.18.1
vim-mode, v0.62.0

# Dev
No dev packages

rinkpijpker commented Oct 28, 2015

[Enter steps to reproduce below:]

  1. ...
  2. ...

Atom Version: 1.0.19
System: Mac OS X 10.11.1
Thrown From: vim-mode package, v0.62.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/rinkpijpker/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
  at Error (native)
  at /Users/rinkpijpker/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
  at Emitter.module.exports.Emitter.emit (/Users/rinkpijpker/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
  at VimState.module.exports.VimState.pushOperations (/Users/rinkpijpker/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
  at atom-text-editor.commands.(anonymous function) (/Users/rinkpijpker/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
  at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:245:29)
  at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
  at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:524:16)
  at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:347:22)
  at HTMLDocument.module.exports.WindowEventHandler.onKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:184:20)

Commands

     -2:31.4.0 command-palette:toggle (atom-text-editor.editor.mini.is-focused)
     -2:30 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -2:30 core:cancel (atom-text-editor.editor.mini.is-focused)
     -2:28.5.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  2x -1:59.1.0 core:select-all (atom-text-editor.editor.mini.is-focused)
     -0:17.2.0 fuzzy-finder:toggle-file-finder (div.settings-view.pane-item)
     -0:15.8.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:15.8.0 core:cancel (atom-text-editor.editor.mini.is-focused)
     -0:12 core:close (div.settings-view.pane-item)
     -0:04.6.0 vim-mode:find (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:03.6.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:03.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:02.2.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:02.2.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:01.7.0 vim-mode:till (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.6.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "themes": [
      "nucleus-dark-ui",
      "batman-syntax"
    ]
  }
}

Installed Packages

# User
batman-syntax, v1.0.1
emmet, v2.3.13
file-type-icons, v0.7.3
linter, v1.9.1
minimap, v4.15.0
nucleus-dark-ui, v0.6.6
pigments, v0.18.1
vim-mode, v0.62.0

# Dev
No dev packages
@skandl

This comment has been minimized.

Show comment
Hide comment
@skandl

skandl Dec 8, 2015

Sorry, no new info except that it occurs on the current version.

Atom Version: 1.2.4
System: Mac OS X 10.10.5
Thrown From: vim-mode package, v0.63.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/kandls1/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/kandls1/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/kandls1/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/kandls1/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/kandls1/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:533:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:356:22)
    at KeymapManager.module.exports.KeymapManager.terminatePendingState (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:507:14)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:383:23)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:99:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

  8x -0:18.9.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:17.4.0 vim-mode:insert-after-end-of-line (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:14 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
  2x -0:13.8.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:13.4.0 vim-mode:activate-linewise-visual-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:12.8.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.visual-mode)
     -0:12.6.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:12.2.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:11.8.0 core:save (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:02.8.0 vim-mode:replace (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:02.8.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:02.6.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.5.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:01.5.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:01.3.0 vim-mode:activate-insert-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "disabledPackages": [
      "whitespace"
    ],
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ],
    "openEmptyEditorOnStart": false
  }
}

Installed Packages

# User
atom-beautify, v0.28.19
build, v0.50.0
close-other-tabs, v0.1.0
floobits, v0.29.3
vim-mode, v0.63.0

# Dev
No dev packages

skandl commented Dec 8, 2015

Sorry, no new info except that it occurs on the current version.

Atom Version: 1.2.4
System: Mac OS X 10.10.5
Thrown From: vim-mode package, v0.63.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/kandls1/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/kandls1/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/kandls1/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/kandls1/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/kandls1/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:533:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:356:22)
    at KeymapManager.module.exports.KeymapManager.terminatePendingState (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:507:14)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:383:23)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:99:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

  8x -0:18.9.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:17.4.0 vim-mode:insert-after-end-of-line (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:14 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
  2x -0:13.8.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:13.4.0 vim-mode:activate-linewise-visual-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:12.8.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.visual-mode)
     -0:12.6.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:12.2.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:11.8.0 core:save (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:04.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:02.8.0 vim-mode:replace (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:02.8.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:02.6.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.5.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:01.5.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:01.3.0 vim-mode:activate-insert-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "disabledPackages": [
      "whitespace"
    ],
    "themes": [
      "atom-dark-ui",
      "atom-dark-syntax"
    ],
    "openEmptyEditorOnStart": false
  }
}

Installed Packages

# User
atom-beautify, v0.28.19
build, v0.50.0
close-other-tabs, v0.1.0
floobits, v0.29.3
vim-mode, v0.63.0

# Dev
No dev packages
@kennbrodhagen

This comment has been minimized.

Show comment
Hide comment
@kennbrodhagen

kennbrodhagen Feb 7, 2016

This happened to me during the following sequence of operations on Mac OSX 10.11.3:

  1. I had another program with focus and Cmd-Tabbed over to atom.
  2. executed typed ,t which is bound to the following:
'atom-text-editor.vim-mode:not(.insert-mode)':
  ', t': 'fuzzy-finder:toggle-file-finder'
  1. The error appeared.
  2. Executing the command again afterward now continues to display the error and does not open the fuzzy finder.

I restarted atom and now when I try the keybinding it doesn't do anything the first few times and then results in the error. When I first set the binding up and tested it was working. I'm not sure what might have changed in between.

kennbrodhagen commented Feb 7, 2016

This happened to me during the following sequence of operations on Mac OSX 10.11.3:

  1. I had another program with focus and Cmd-Tabbed over to atom.
  2. executed typed ,t which is bound to the following:
'atom-text-editor.vim-mode:not(.insert-mode)':
  ', t': 'fuzzy-finder:toggle-file-finder'
  1. The error appeared.
  2. Executing the command again afterward now continues to display the error and does not open the fuzzy finder.

I restarted atom and now when I try the keybinding it doesn't do anything the first few times and then results in the error. When I first set the binding up and tested it was working. I'm not sure what might have changed in between.

@davideg

This comment has been minimized.

Show comment
Hide comment
@davideg

davideg Feb 17, 2016

I am able to reproduce this error by moving my cursor onto a letter and typing g, Shift + u, m.

I restarted Atom and created a new document to try to reproduce this. I wrote some text, moved my cursor around, and then tried the key sequence. No problem the first two times, but the third time I get the exception.

Error with new document

Atom Version: 1.3.2
System: Mac OS X 10.11.2
Thrown From: vim-mode package, v0.64.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/dginsburg/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

     -0:14 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:12.9.0 blur (atom-text-editor.editor.mini.is-focused)
  3x -0:12.4.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:10.7.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:09.8.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:09.3.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:08.4.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:08.1.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:07.4.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.9.0 vim-mode:mark (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:04.9.0 blur (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:04.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:03.4.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.3.0 vim-mode:upper-case (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:00.9.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:00.9.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)

Config

{
  "core": {
    "themes": [
      "atom-light-ui",
      "atom-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
autocomplete-emojis, v2.2.2
linter-write-good, v0.6.1
vim-mode, v0.64.0

# Dev
No dev packages

Error with existing document

Atom Version: 1.3.2
System: Mac OS X 10.11.2
Thrown From: vim-mode package, v0.64.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/dginsburg/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

  4x -0:38.7.0 vim-mode:move-to-previous-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:37.4.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:35.7.0 vim-mode:change-to-last-character-of-line (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:23.5.0 core:backspace (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:23 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:22.7.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  6x -0:22.1.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  4x -0:20.7.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:19.7.0 vim-mode:change-to-last-character-of-line (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:11.9.0 autocomplete-plus:confirm (atom-text-editor.editor.vim-mode.is-focused.insert-mode.autocomplete-active)
     -0:10.2.0 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
  2x -0:09.6.0 vim-mode:move-to-previous-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:09.1.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.6.0 vim-mode:upper-case (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.1.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:01.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)

Config

{
  "core": {
    "themes": [
      "atom-light-ui",
      "atom-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
autocomplete-emojis, v2.2.2
linter-write-good, v0.6.1
vim-mode, v0.64.0

# Dev
No dev packages

davideg commented Feb 17, 2016

I am able to reproduce this error by moving my cursor onto a letter and typing g, Shift + u, m.

I restarted Atom and created a new document to try to reproduce this. I wrote some text, moved my cursor around, and then tried the key sequence. No problem the first two times, but the third time I get the exception.

Error with new document

Atom Version: 1.3.2
System: Mac OS X 10.11.2
Thrown From: vim-mode package, v0.64.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/dginsburg/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

     -0:14 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:12.9.0 blur (atom-text-editor.editor.mini.is-focused)
  3x -0:12.4.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:10.7.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:09.8.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:09.3.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:08.4.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:08.1.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:07.4.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.9.0 vim-mode:mark (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:04.9.0 blur (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  2x -0:04.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  3x -0:03.4.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.3.0 vim-mode:upper-case (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:00.9.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:00.9.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)

Config

{
  "core": {
    "themes": [
      "atom-light-ui",
      "atom-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
autocomplete-emojis, v2.2.2
linter-write-good, v0.6.1
vim-mode, v0.64.0

# Dev
No dev packages

Error with existing document

Atom Version: 1.3.2
System: Mac OS X 10.11.2
Thrown From: vim-mode package, v0.64.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/dginsburg/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/dginsburg/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/dginsburg/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

  4x -0:38.7.0 vim-mode:move-to-previous-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  2x -0:37.4.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:35.7.0 vim-mode:change-to-last-character-of-line (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:23.5.0 core:backspace (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:23 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
     -0:22.7.0 vim-mode:move-up (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  6x -0:22.1.0 vim-mode:move-to-next-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  4x -0:20.7.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:19.7.0 vim-mode:change-to-last-character-of-line (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:11.9.0 autocomplete-plus:confirm (atom-text-editor.editor.vim-mode.is-focused.insert-mode.autocomplete-active)
     -0:10.2.0 vim-mode:activate-normal-mode (atom-text-editor.editor.vim-mode.is-focused.insert-mode)
  2x -0:09.6.0 vim-mode:move-to-previous-word (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:09.1.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.6.0 vim-mode:upper-case (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:01.1.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:01.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)

Config

{
  "core": {
    "themes": [
      "atom-light-ui",
      "atom-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
autocomplete-emojis, v2.2.2
linter-write-good, v0.6.1
vim-mode, v0.64.0

# Dev
No dev packages
@noseglid

This comment has been minimized.

Show comment
Hide comment
@noseglid

noseglid Feb 25, 2016

[Enter steps to reproduce below:]

Nothing new here either.. thought I'd paste it on the off chance it helps anyway.

Atom Version: 1.5.3
System: Mac OS X 10.11.3
Thrown From: vim-mode package, v0.64.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/noseglid/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/noseglid/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/noseglid/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/noseglid/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/noseglid/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

     -1:00.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
 28x -1:00.9.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:07.9.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.visual-mode)
     -0:06.7.0 vim-mode:delete-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:06.1.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.7.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:05.7.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  7x -0:05.1.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.1.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:03.9.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:03.9.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:03.3.0 vim-mode:till (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:03.3.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:02.9.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  9x -0:02.1.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  4x -0:00.3.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)

Config

{
  "core": {
    "audioBeep": false,
    "closeEmptyWindows": false,
    "disabledPackages": [
      "linter-checkstyle"
    ],
    "openEmptyEditorOnStart": false,
    "themes": [
      "atom-material-ui",
      "one-dark-syntax"
    ]
  },
  "vim-mode": {
    "useClipboardAsDefaultRegister": true,
    "useSmartcaseForSearch": true
  }
}

Installed Packages

# User
angularjs, v0.3.4
atom-material-ui, v1.2.0
atom-ternjs, v0.13.2
build, v0.54.1
build-cargo, v0.12.0
build-gradle, v0.6.0
build-gulp, v0.7.0
build-npm-apm, v0.8.0
editorconfig, v1.2.4
ex-mode, v0.8.0
file-icons, v1.6.15
highlight-selected, v0.11.2
language-salt, v0.4.0
linter, v1.11.3
linter-eslint, v7.0.0
linter-javac, v1.5.0
minimap, v4.19.0
minimap-git-diff, v4.1.8
minimap-highlight-selected, v4.3.1
react, v0.14.1
trailing-spaces, v0.3.2
vim-mode, v0.64.0

# Dev
No dev packages

noseglid commented Feb 25, 2016

[Enter steps to reproduce below:]

Nothing new here either.. thought I'd paste it on the off chance it helps anyway.

Atom Version: 1.5.3
System: Mac OS X 10.11.3
Thrown From: vim-mode package, v0.64.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/noseglid/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/noseglid/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/Users/noseglid/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/noseglid/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/noseglid/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:536:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:359:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/opt/homebrew-cask/Caskroom/atom/1.0.5/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

     -1:00.9.0 core:confirm (atom-text-editor.editor.mini.is-focused)
 28x -1:00.9.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:07.9.0 vim-mode:delete (atom-text-editor.editor.vim-mode.is-focused.visual-mode)
     -0:06.7.0 vim-mode:delete-right (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:06.1.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -0:05.7.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:05.7.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  7x -0:05.1.0 vim-mode:move-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.1.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:03.9.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:03.9.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:03.3.0 vim-mode:till (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:03.3.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
  3x -0:02.9.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  9x -0:02.1.0 vim-mode:move-left (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
  4x -0:00.3.0 vim-mode:move-right (atom-text-editor.editor.vim-mode.normal-mode.is-focused)

Config

{
  "core": {
    "audioBeep": false,
    "closeEmptyWindows": false,
    "disabledPackages": [
      "linter-checkstyle"
    ],
    "openEmptyEditorOnStart": false,
    "themes": [
      "atom-material-ui",
      "one-dark-syntax"
    ]
  },
  "vim-mode": {
    "useClipboardAsDefaultRegister": true,
    "useSmartcaseForSearch": true
  }
}

Installed Packages

# User
angularjs, v0.3.4
atom-material-ui, v1.2.0
atom-ternjs, v0.13.2
build, v0.54.1
build-cargo, v0.12.0
build-gradle, v0.6.0
build-gulp, v0.7.0
build-npm-apm, v0.8.0
editorconfig, v1.2.4
ex-mode, v0.8.0
file-icons, v1.6.15
highlight-selected, v0.11.2
language-salt, v0.4.0
linter, v1.11.3
linter-eslint, v7.0.0
linter-javac, v1.5.0
minimap, v4.19.0
minimap-git-diff, v4.1.8
minimap-highlight-selected, v4.3.1
react, v0.14.1
trailing-spaces, v0.3.2
vim-mode, v0.64.0

# Dev
No dev packages
@fasterthanlime

This comment has been minimized.

Show comment
Hide comment
@fasterthanlime

fasterthanlime Mar 16, 2016

I'm experiencing this too, I can reliably reproduce it by just trying to use delete till X command in vim, for example placing myself in an function call's arguments and hitting dt) to remove every argument to the right of the cursor.

Atom Version: 1.5.4
System: Debian GNU/Linux
Thrown From: vim-mode package, v0.65.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /home/amos/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /home/amos/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/home/amos/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/home/amos/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/home/amos/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:260:29)
    at /usr/share/atom/resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:570:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:378:22)
    at KeymapManager.module.exports.KeymapManager.terminatePendingState (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:551:14)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:422:21)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/usr/share/atom/resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app.asar/src/window-event-handler.js:3:61)

Commands

     -0:03.9.0 vim-mode:move-down (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:03.9.0 vim-mode:move-up (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
  2x -0:03.6.0 vim-mode:bracket-matching-motion (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:02.9.0 vim-mode:move-down (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:02.3.0 vim-mode:move-to-beginning-of-line (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
  3x -0:02.2.0 vim-mode:move-to-end-of-word (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:01.7.0 vim-mode:move-right (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:01.5.0 vim-mode:delete (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:01.3.0 vim-mode:till (atom-text-editor.editor.is-focused.vim-mode.operator-pending-mode)
     -0:01.3.0 vim-mode:move-to-next-sentence (atom-text-editor.editor.is-focused.vim-mode.operator-pending-mode)
  2x -0:01.3.0 blur (atom-text-editor.editor.mini)

Config

{
  "core": {
    "autoHideMenuBar": true,
    "themes": [
      "light-bint-ui",
      "nothrill-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
change-case, v0.6.0
color-picker, v2.1.1
colornamer, v0.3.1
fonts, v1.2.0
go-plus, v3.5.4
light-bint-ui, v1.0.4
linter, v1.11.3
linter-js-standard, v3.2.1
nothrill-light-syntax, v0.8.0
vim-mode, v0.65.0
webbox-color, v0.5.9

# Dev
No dev packages

fasterthanlime commented Mar 16, 2016

I'm experiencing this too, I can reliably reproduce it by just trying to use delete till X command in vim, for example placing myself in an function call's arguments and hitting dt) to remove every argument to the right of the cursor.

Atom Version: 1.5.4
System: Debian GNU/Linux
Thrown From: vim-mode package, v0.65.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /home/amos/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /home/amos/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (/home/amos/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/home/amos/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/home/amos/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/usr/share/atom/resources/app.asar/src/command-registry.js:260:29)
    at /usr/share/atom/resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:570:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:378:22)
    at KeymapManager.module.exports.KeymapManager.terminatePendingState (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:551:14)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/usr/share/atom/resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:422:21)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (/usr/share/atom/resources/app.asar/src/window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (/usr/share/atom/resources/app.asar/src/window-event-handler.js:3:61)

Commands

     -0:03.9.0 vim-mode:move-down (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:03.9.0 vim-mode:move-up (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
  2x -0:03.6.0 vim-mode:bracket-matching-motion (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:02.9.0 vim-mode:move-down (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:02.3.0 vim-mode:move-to-beginning-of-line (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
  3x -0:02.2.0 vim-mode:move-to-end-of-word (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:01.7.0 vim-mode:move-right (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:01.5.0 vim-mode:delete (atom-text-editor.editor.is-focused.vim-mode.normal-mode)
     -0:01.3.0 vim-mode:till (atom-text-editor.editor.is-focused.vim-mode.operator-pending-mode)
     -0:01.3.0 vim-mode:move-to-next-sentence (atom-text-editor.editor.is-focused.vim-mode.operator-pending-mode)
  2x -0:01.3.0 blur (atom-text-editor.editor.mini)

Config

{
  "core": {
    "autoHideMenuBar": true,
    "themes": [
      "light-bint-ui",
      "nothrill-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
change-case, v0.6.0
color-picker, v2.1.1
colornamer, v0.3.1
fonts, v1.2.0
go-plus, v3.5.4
light-bint-ui, v1.0.4
linter, v1.11.3
linter-js-standard, v3.2.1
nothrill-light-syntax, v0.8.0
vim-mode, v0.65.0
webbox-color, v0.5.9

# Dev
No dev packages
@hipo78

This comment has been minimized.

Show comment
Hide comment
@hipo78

hipo78 Mar 21, 2016

Hello,
I also encountered this error. For me, it happened when I attempted to use the find functionality (I pressed ctrl + f) within my html document. I re-launched atom but could not reproduce the error.

Atom Version: 1.6.0
System: Microsoft Windows 10 Pro
Thrown From: vim-mode package, v0.65.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /C:/Users/Mexx/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at file:///C:/Users/Mexx/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (C:\Users\Mexx\.atom\packages\vim-mode\node_modules\event-kit\lib\emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (file:///C:/Users/Mexx/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (file:///C:/Users/Mexx/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\command-registry.js:260:29)
    at C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:570:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:378:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\window-event-handler.js:3:61)

Commands

     -0:09.5.0 vim-mode:scroll-full-screen-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:05.5.0 vim-mode:change (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.7.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  2x -0:04.7.0 blur (atom-text-editor.editor.mini)

Config

{
  "core": {
    "themes": [
      "seti-ui",
      "monokai-seti"
    ]
  }
}

Installed Packages

# User
atom-html-preview, v0.1.18
auto-detect-indentation, v1.0.0
autoclose-html, v0.23.0
color-picker, v2.1.1
file-icons, v1.6.18
highlight-selected, v0.11.2
indent-guide-improved, v1.4.5
linter, v1.11.4
linter-csslint, v1.3.2
linter-htmlhint, v1.1.0
linter-jshint, v2.0.3
minimap, v4.21.0
minimap-highlight-selected, v4.4.0
monokai-seti, v0.7.0
open-recent, v5.0.0
pigments, v0.24.5
seti-ui, v0.9.1
sync-settings, v0.7.2
vim-mode, v0.65.0

# Dev
No dev packages

hipo78 commented Mar 21, 2016

Hello,
I also encountered this error. For me, it happened when I attempted to use the find functionality (I pressed ctrl + f) within my html document. I re-launched atom but could not reproduce the error.

Atom Version: 1.6.0
System: Microsoft Windows 10 Pro
Thrown From: vim-mode package, v0.65.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /C:/Users/Mexx/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at file:///C:/Users/Mexx/.atom/packages/vim-mode/lib/view-models/view-model.coffee:8:43
    at Emitter.module.exports.Emitter.emit (C:\Users\Mexx\.atom\packages\vim-mode\node_modules\event-kit\lib\emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (file:///C:/Users/Mexx/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (file:///C:/Users/Mexx/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\command-registry.js:260:29)
    at C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:570:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\node_modules\atom-keymap\lib\keymap-manager.js:378:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeydown (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\window-event-handler.js:97:36)
    at HTMLDocument.<anonymous> (C:\Users\Mexx\AppData\Local\atom\app-1.6.0\resources\app.asar\src\window-event-handler.js:3:61)

Commands

     -0:09.5.0 vim-mode:scroll-full-screen-down (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:05.5.0 vim-mode:change (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:04.7.0 vim-mode:mark (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  2x -0:04.7.0 blur (atom-text-editor.editor.mini)

Config

{
  "core": {
    "themes": [
      "seti-ui",
      "monokai-seti"
    ]
  }
}

Installed Packages

# User
atom-html-preview, v0.1.18
auto-detect-indentation, v1.0.0
autoclose-html, v0.23.0
color-picker, v2.1.1
file-icons, v1.6.18
highlight-selected, v0.11.2
indent-guide-improved, v1.4.5
linter, v1.11.4
linter-csslint, v1.3.2
linter-htmlhint, v1.1.0
linter-jshint, v2.0.3
minimap, v4.21.0
minimap-highlight-selected, v4.4.0
monokai-seti, v0.7.0
open-recent, v5.0.0
pigments, v0.24.5
seti-ui, v0.9.1
sync-settings, v0.7.2
vim-mode, v0.65.0

# Dev
No dev packages
@pwnall

This comment has been minimized.

Show comment
Hide comment
@pwnall

pwnall Apr 21, 2016

[Enter steps to reproduce below:]

Not sure what I was doing, but I think the command history here does. FWIW, I was issuing a flurry of commands in pretty quick succession.

Atom Version: 1.7.2
System: Mac OS X 10.11.5
Thrown From: vim-mode package, v0.65.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/pwnall/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/pwnall/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18:29
    at Emitter.module.exports.Emitter.emit (/Users/pwnall/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/pwnall/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/pwnall/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

  2x -1:01.7.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -1:01.4.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -1:01.2.0 ex-mode:open (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -1:01.2.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -1:01.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  4x -1:01.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:02.4.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.6.0 vim-mode:search (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.6.0 blur (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.2.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:01.2.0 core:cancel (atom-text-editor.editor.mini.is-focused)
  2x -0:01.2.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:00.9.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:00.7.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:00.7.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:00.5.0 vim-mode:insert-below-with-newline (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "ignoredNames": [
      ".git",
      ".hg",
      ".svn",
      ".Ds_Store",
      "._*",
      "Thumbs.db",
      "node_modules",
      "bower_modules"
    ],
    "projectHome": "/Users/pwnall/workspace",
    "themes": [
      "one-light-ui",
      "solarized-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
atom-typescript, v8.8.1
ex-mode, v0.8.0
fonts, v1.2.0
language-latex, v0.6.1
language-rust, v0.4.6
linter, v1.11.4
vim-mode, v0.65.0

# Dev
No dev packages

pwnall commented Apr 21, 2016

[Enter steps to reproduce below:]

Not sure what I was doing, but I think the command history here does. FWIW, I was issuing a flurry of commands in pretty quick succession.

Atom Version: 1.7.2
System: Mac OS X 10.11.5
Thrown From: vim-mode package, v0.65.0

Stack Trace

Uncaught NotFoundError: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?

At /Users/pwnall/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18

Error: Failed to execute 'remove' on 'Element': The node to be removed is no longer a child of this node. Perhaps it was moved in a 'blur' event handler?
    at Error (native)
    at /Users/pwnall/.atom/packages/vim-mode/lib/view-models/view-model.coffee:18:29
    at Emitter.module.exports.Emitter.emit (/Users/pwnall/.atom/packages/vim-mode/node_modules/event-kit/lib/emitter.js:71:11)
    at VimState.module.exports.VimState.pushOperations (/Users/pwnall/.atom/packages/vim-mode/lib/vim-state.coffee:227:18)
    at atom-text-editor.commands.(anonymous function) (/Users/pwnall/.atom/packages/vim-mode/lib/vim-state.coffee:209:45)
    at CommandRegistry.module.exports.CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:260:29)
    at /Applications/Atom.app/Contents/Resources/app.asar/src/command-registry.js:3:61
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:580:16)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app.asar/node_modules/atom-keymap/lib/keymap-manager.js:388:22)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:98:36)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app.asar/src/window-event-handler.js:3:61)

Commands

  2x -1:01.7.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -1:01.4.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -1:01.2.0 ex-mode:open (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -1:01.2.0 blur (atom-text-editor.editor.vim-mode.is-focused.normal-mode)
     -1:01.1.0 core:confirm (atom-text-editor.editor.mini.is-focused)
  4x -1:01.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:02.4.0 vim-mode:reset-normal-mode (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.6.0 vim-mode:search (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.6.0 blur (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:01.2.0 editor:consolidate-selections (atom-text-editor.editor.mini.is-focused)
     -0:01.2.0 core:cancel (atom-text-editor.editor.mini.is-focused)
  2x -0:01.2.0 blur (atom-text-editor.editor.mini.is-focused)
     -0:00.9.0 vim-mode:delete (atom-text-editor.editor.vim-mode.normal-mode.is-focused)
     -0:00.7.0 vim-mode:replace (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
  3x -0:00.7.0 blur (atom-text-editor.editor.vim-mode.is-focused.operator-pending-mode)
     -0:00.5.0 vim-mode:insert-below-with-newline (atom-text-editor.editor.vim-mode.is-focused.normal-mode)

Config

{
  "core": {
    "ignoredNames": [
      ".git",
      ".hg",
      ".svn",
      ".Ds_Store",
      "._*",
      "Thumbs.db",
      "node_modules",
      "bower_modules"
    ],
    "projectHome": "/Users/pwnall/workspace",
    "themes": [
      "one-light-ui",
      "solarized-light-syntax"
    ]
  },
  "vim-mode": {}
}

Installed Packages

# User
atom-typescript, v8.8.1
ex-mode, v0.8.0
fonts, v1.2.0
language-latex, v0.6.1
language-rust, v0.4.6
linter, v1.11.4
vim-mode, v0.65.0

# Dev
No dev packages

@50Wliu 50Wliu added the bug label Apr 21, 2016

@passy

This comment has been minimized.

Show comment
Hide comment
@passy

passy Sep 10, 2016

I'm pretty sure I got this by setting a bookmark with m a when this happened. Issuing the same command again afterwards worked just fine.

passy commented Sep 10, 2016

I'm pretty sure I got this by setting a bookmark with m a when this happened. Issuing the same command again afterwards worked just fine.

@smably

This comment has been minimized.

Show comment
Hide comment
@smably

smably Sep 15, 2016

I keep accidentally hitting cm and getting this error.

smably commented Sep 15, 2016

I keep accidentally hitting cm and getting this error.

@averyvery

This comment has been minimized.

Show comment
Hide comment
@averyvery

averyvery May 17, 2017

Hmm, suddenly getting this when hitting r and any key to replace a character. Might be a conflict with another package....

averyvery commented May 17, 2017

Hmm, suddenly getting this when hitting r and any key to replace a character. Might be a conflict with another package....

@robbprescott

This comment has been minimized.

Show comment
Hide comment
@robbprescott

robbprescott May 17, 2017

I also just started getting this with r to replace, or m to mark a bookmark. Surprisingly everything still seems to work, just getting an error.

robbprescott commented May 17, 2017

I also just started getting this with r to replace, or m to mark a bookmark. Surprisingly everything still seems to work, just getting an error.

@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu May 17, 2017

Member

Just a heads-up: this package has been deprecated. I would recommend installing vim-mode-plus instead.

Member

50Wliu commented May 17, 2017

Just a heads-up: this package has been deprecated. I would recommend installing vim-mode-plus instead.

@averyvery

This comment has been minimized.

Show comment
Hide comment
@averyvery

averyvery May 17, 2017

oh, thanks, I wondered about why there were two! Will do.

averyvery commented May 17, 2017

oh, thanks, I wondered about why there were two! Will do.

@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald May 20, 2017

Started getting this today, tried switching to vim-mode-plus but the lack of support for :'<,'>s/foo/bar/g makes it a non-viable solution for me. I'm also pretty non-plussed about using the command palette for ex-mode functionality — even if it had support for substitutions, the palette obscures the code I'm trying to act on.

So I found the exceptions and wrapped them in a try/catch. Made the above PR, though based on the existing PRs it looks like this may be an exercise in futility. Here's hoping — long live ex-mode!

fritzherald commented May 20, 2017

Started getting this today, tried switching to vim-mode-plus but the lack of support for :'<,'>s/foo/bar/g makes it a non-viable solution for me. I'm also pretty non-plussed about using the command palette for ex-mode functionality — even if it had support for substitutions, the palette obscures the code I'm trying to act on.

So I found the exceptions and wrapped them in a try/catch. Made the above PR, though based on the existing PRs it looks like this may be an exercise in futility. Here's hoping — long live ex-mode!

@mmagnuski

This comment has been minimized.

Show comment
Hide comment
@mmagnuski

mmagnuski May 23, 2017

I get this error whenever I try to go to specified character with vim mode, for example: fw or Fw.

mmagnuski commented May 23, 2017

I get this error whenever I try to go to specified character with vim mode, for example: fw or Fw.

@mmagnuski

This comment has been minimized.

Show comment
Hide comment
@mmagnuski

mmagnuski May 23, 2017

Oh, sorry, didn't know it was deprecated, installing vim-mode-plus now.

mmagnuski commented May 23, 2017

Oh, sorry, didn't know it was deprecated, installing vim-mode-plus now.

@rcrelia

This comment has been minimized.

Show comment
Hide comment
@rcrelia

rcrelia May 24, 2017

vim-mode-plus is not a viable alternative, unfortunately. I'm bummed that we're losing the native vim-mode support from Atom. The lack of ex mode syntax support makes vim-mode-plus pretty useless IMHO.

rcrelia commented May 24, 2017

vim-mode-plus is not a viable alternative, unfortunately. I'm bummed that we're losing the native vim-mode support from Atom. The lack of ex mode syntax support makes vim-mode-plus pretty useless IMHO.

@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu May 24, 2017

Member

At the risk of drifting slightly off-topic, have you found https://atom.io/packages/vim-mode-plus-ex-mode? It looks like it offers some ex mode support.

Member

50Wliu commented May 24, 2017

At the risk of drifting slightly off-topic, have you found https://atom.io/packages/vim-mode-plus-ex-mode? It looks like it offers some ex mode support.

@Byron-TW

This comment has been minimized.

Show comment
Hide comment
@Byron-TW

Byron-TW May 24, 2017

@rcelia To me vim-mode-plus is one of the (if not 'the') most useful vim emulation that I know, while adding useful smart features that I miss whenever I am back in the original vim. Even though I believe to understand how frustrating it is to see a feature like ex-mode missing in the only alternative, calling it useless doesn't seem factually justified. Maybe it's also because I see the work and dedication the author puts into it, which makes me choke on a work like this.

Byron-TW commented May 24, 2017

@rcelia To me vim-mode-plus is one of the (if not 'the') most useful vim emulation that I know, while adding useful smart features that I miss whenever I am back in the original vim. Even though I believe to understand how frustrating it is to see a feature like ex-mode missing in the only alternative, calling it useless doesn't seem factually justified. Maybe it's also because I see the work and dedication the author puts into it, which makes me choke on a work like this.

@rcrelia

This comment has been minimized.

Show comment
Hide comment
@rcrelia

rcrelia May 24, 2017

@50Wliu I did try out vim-mode-plus-ex-mode, it doesn't offer full ex mode functionality like the native vim-mode of Atom and the author, who is also the author of vim-mode-plus, clearly states he is not motivated to provide that full functionality. That's entirely his prerogative, but it leaves a major gap in his work as a replacement for vim-mode in Atom.

@Byron-TW that's cool, I'm not denigrating anyone. But I will reiterate: vim-mode-plus along with vim-mode-plus-ex-mode are NOT a complete replacement for the native vim-mode in Atom (and the ex-mode plugin. There is a huge gap and the author, who I'm sure is a great person and I applaud his effort, clearly states in the vim-mode-plus-ex-mode README that he does not care if the ex mode support is complete and to not bother asking him to provide that support. That attitude is unfortunate for those users like myself who count on full ex mode capabilities.

If vim-mode support ever goes missing from Atom altogether, we'll either be forced to give up a significant level of productivity or have to switch to another editor completely. That's a pretty crappy situation, IMHO.

rcrelia commented May 24, 2017

@50Wliu I did try out vim-mode-plus-ex-mode, it doesn't offer full ex mode functionality like the native vim-mode of Atom and the author, who is also the author of vim-mode-plus, clearly states he is not motivated to provide that full functionality. That's entirely his prerogative, but it leaves a major gap in his work as a replacement for vim-mode in Atom.

@Byron-TW that's cool, I'm not denigrating anyone. But I will reiterate: vim-mode-plus along with vim-mode-plus-ex-mode are NOT a complete replacement for the native vim-mode in Atom (and the ex-mode plugin. There is a huge gap and the author, who I'm sure is a great person and I applaud his effort, clearly states in the vim-mode-plus-ex-mode README that he does not care if the ex mode support is complete and to not bother asking him to provide that support. That attitude is unfortunate for those users like myself who count on full ex mode capabilities.

If vim-mode support ever goes missing from Atom altogether, we'll either be forced to give up a significant level of productivity or have to switch to another editor completely. That's a pretty crappy situation, IMHO.

@crucialfelix

This comment has been minimized.

Show comment
Hide comment
@crucialfelix

crucialfelix May 24, 2017

Simple reproducer:

  1. text is: mv4
  2. place cursor on the 4
  3. Type r 5 -- replace char with 5
  4. The Error

crucialfelix commented May 24, 2017

Simple reproducer:

  1. text is: mv4
  2. place cursor on the 4
  3. Type r 5 -- replace char with 5
  4. The Error
@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald May 24, 2017

@as-cii @50Wliu @maxbrunsfeld @plbowers @t9md @jazzpi @lloeki Pinging you all because you authored the last few commits in master either here, in vim-mode-plus, or in ex-mode. Vim in atom is awesome, thank you all for your work.

  1. This thread's exception recently started occurring very frequently (as in, every time you try to replace a character). Pull request #1092 catches the exception. Can we figure out how to get it reviewed and merged? We know, we know, "deprecated", but this is a clear regression, and according to the readme "we still want to fix regressions and keep it working."

  2. Can we talk about this whole deprecation thing? To many of us, ex-mode is absolutely core to how we work. There are plenty of things to admire about vim-mode-plus, but for us they don't come anywhere close to compensating for the loss of ex-mode. From t9md/atom-vim-mode-plus#52 it seems that true ex-mode is not on the near horizon for vim-mode-plus (the existing vim-mode-plus-ex-mode is a very limited command-palette hack). I'd be happy to start or join an effort to bring real ex-mode to vim-mode-plus (see 3.), but in the meantime, could we find a way to keep this repo at least somewhat healthy? Who's on point for keeping this repo working?

  3. From an implementation point-of-view, what would it take to bring real ex-mode to vim-mode-plus? What are the incompatibilities between t9md/vim-mode-plus and lloeki/ex-mode?

Thanks!
ZZ

fritzherald commented May 24, 2017

@as-cii @50Wliu @maxbrunsfeld @plbowers @t9md @jazzpi @lloeki Pinging you all because you authored the last few commits in master either here, in vim-mode-plus, or in ex-mode. Vim in atom is awesome, thank you all for your work.

  1. This thread's exception recently started occurring very frequently (as in, every time you try to replace a character). Pull request #1092 catches the exception. Can we figure out how to get it reviewed and merged? We know, we know, "deprecated", but this is a clear regression, and according to the readme "we still want to fix regressions and keep it working."

  2. Can we talk about this whole deprecation thing? To many of us, ex-mode is absolutely core to how we work. There are plenty of things to admire about vim-mode-plus, but for us they don't come anywhere close to compensating for the loss of ex-mode. From t9md/atom-vim-mode-plus#52 it seems that true ex-mode is not on the near horizon for vim-mode-plus (the existing vim-mode-plus-ex-mode is a very limited command-palette hack). I'd be happy to start or join an effort to bring real ex-mode to vim-mode-plus (see 3.), but in the meantime, could we find a way to keep this repo at least somewhat healthy? Who's on point for keeping this repo working?

  3. From an implementation point-of-view, what would it take to bring real ex-mode to vim-mode-plus? What are the incompatibilities between t9md/vim-mode-plus and lloeki/ex-mode?

Thanks!
ZZ

@jazzpi

This comment has been minimized.

Show comment
Hide comment
@jazzpi

jazzpi May 24, 2017

ex-mode should now work with vim-mode-plus, but I don't have the time to test extensively (and also not a lot of motivation... See lloeki/ex-mode#174). I'm not sure if a discussion on ex-mode is really on-topic in vim-mode though.

jazzpi commented May 24, 2017

ex-mode should now work with vim-mode-plus, but I don't have the time to test extensively (and also not a lot of motivation... See lloeki/ex-mode#174). I'm not sure if a discussion on ex-mode is really on-topic in vim-mode though.

@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu May 25, 2017

Member

Pull request #1092 catches the exception.

I've looked at this PR and it doesn't look mergeable. All it does is silently absorb the exception rather than fixing the root cause.

in the meantime, could we find a way to keep this repo at least somewhat healthy? Who's on point for keeping this repo working?

It was deprecated because we, the Atom team, realized that we were unable to dedicate enough time to maintaining this repository. Rather than let it languish, we decided to deprecate it so that people could move to alternatives or fork it and improve on it. Before deprecation, @maxbrunsfeld was mostly the sole maintainer.

From an implementation point-of-view, what would it take to bring real ex-mode to vim-mode-plus?

I am unable to answer this, having no previous experience with Vim, vim-mode, or vim-mode-plus. In fact, my only contributions to this repository were to make the deprecation notice more prominent when viewing the package.

Member

50Wliu commented May 25, 2017

Pull request #1092 catches the exception.

I've looked at this PR and it doesn't look mergeable. All it does is silently absorb the exception rather than fixing the root cause.

in the meantime, could we find a way to keep this repo at least somewhat healthy? Who's on point for keeping this repo working?

It was deprecated because we, the Atom team, realized that we were unable to dedicate enough time to maintaining this repository. Rather than let it languish, we decided to deprecate it so that people could move to alternatives or fork it and improve on it. Before deprecation, @maxbrunsfeld was mostly the sole maintainer.

From an implementation point-of-view, what would it take to bring real ex-mode to vim-mode-plus?

I am unable to answer this, having no previous experience with Vim, vim-mode, or vim-mode-plus. In fact, my only contributions to this repository were to make the deprecation notice more prominent when viewing the package.

@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald May 25, 2017

I tried vim-mode-plus again with the latest version of ex-mode and can confirm that it is working. I haven't tested extensively, but substitutions are functional. Which means I (and other ex-mode holdouts) can switch over to vim-mode-plus. Thanks @jazzpi!

As for the mergability of my obviously crude PR... We're all busy, this package is currently broken. This is going to come out more harsh and less appreciative than I mean it, but it seems a little weird for the repo owners to maintain nothing here but the coding standards. What about merging the PR to get it working again and then following up with a proper investigation? Or somebody knowlegeable taking a look and explaining what "the root cause" might be and how to fix it?

fritzherald commented May 25, 2017

I tried vim-mode-plus again with the latest version of ex-mode and can confirm that it is working. I haven't tested extensively, but substitutions are functional. Which means I (and other ex-mode holdouts) can switch over to vim-mode-plus. Thanks @jazzpi!

As for the mergability of my obviously crude PR... We're all busy, this package is currently broken. This is going to come out more harsh and less appreciative than I mean it, but it seems a little weird for the repo owners to maintain nothing here but the coding standards. What about merging the PR to get it working again and then following up with a proper investigation? Or somebody knowlegeable taking a look and explaining what "the root cause" might be and how to fix it?

@lloeki

This comment has been minimized.

Show comment
Hide comment
@lloeki

lloeki May 25, 2017

Contributor

What about merging the PR to get it working again and then following up with a proper investigation?

Because that's how workarounds that end up not getting fixed get merged into the codebase, resulting into an unmaintainable mess. As maintainers we have the responsibility to think not just about ourselves but also the next developer and the future life of the project, and making the code a mess, while it looks like helping in the short term, does not on the long run: it's just driving the project into the ground. Such decisions are not lightly taken but if one wants the code to be taken over to new maintainership it has to be reasonably clean, else no one will step up. I know this may sound absurd as right now the thing is unusable but this is how pressure accretes into someone stepping up for either a proper PR or maintainership (which generally follows a proper PR, the latter serving as a sort of baton passing).

Contributor

lloeki commented May 25, 2017

What about merging the PR to get it working again and then following up with a proper investigation?

Because that's how workarounds that end up not getting fixed get merged into the codebase, resulting into an unmaintainable mess. As maintainers we have the responsibility to think not just about ourselves but also the next developer and the future life of the project, and making the code a mess, while it looks like helping in the short term, does not on the long run: it's just driving the project into the ground. Such decisions are not lightly taken but if one wants the code to be taken over to new maintainership it has to be reasonably clean, else no one will step up. I know this may sound absurd as right now the thing is unusable but this is how pressure accretes into someone stepping up for either a proper PR or maintainership (which generally follows a proper PR, the latter serving as a sort of baton passing).

@t9md

This comment has been minimized.

Show comment
Hide comment
@t9md

t9md May 25, 2017

Contributor

Great work @jazzpi.
From the very first release of vmp(about 2 years ago), adding vmp support into ex-mode was not difficult.
But as everyone already mentioned I myself don't need ex-mode, and another reason is I'm already overwhelmed as maintainer of vim-mode-plus.

Most of OSS developers spend their FREE time to do something fun, something good for other developer and their user.

IMO who use ex-mode should give big applause to creator of ex-mode @lloeki.
And current maintainer @jazzpi.

For vim-mode-plus, I couldn't start vim-mode-plus from scratch, it's just fork of already great vim-mode.
Someone who is not happy with my vim-mode-plus, can start another vim-mode-plus-plus if they want 😉

Contributor

t9md commented May 25, 2017

Great work @jazzpi.
From the very first release of vmp(about 2 years ago), adding vmp support into ex-mode was not difficult.
But as everyone already mentioned I myself don't need ex-mode, and another reason is I'm already overwhelmed as maintainer of vim-mode-plus.

Most of OSS developers spend their FREE time to do something fun, something good for other developer and their user.

IMO who use ex-mode should give big applause to creator of ex-mode @lloeki.
And current maintainer @jazzpi.

For vim-mode-plus, I couldn't start vim-mode-plus from scratch, it's just fork of already great vim-mode.
Someone who is not happy with my vim-mode-plus, can start another vim-mode-plus-plus if they want 😉

@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald May 25, 2017

@lloeki Just to keep things in perspective:

screenshot 2017-05-25 00 11 29

Yes, my PR is a troll. I think it should be merged. I'm happy to learn the ways and dig into how to do this correctly over the weekend, but seriously.

https://increment.com/on-call/when-the-pager-goes-off/

fritzherald commented May 25, 2017

@lloeki Just to keep things in perspective:

screenshot 2017-05-25 00 11 29

Yes, my PR is a troll. I think it should be merged. I'm happy to learn the ways and dig into how to do this correctly over the weekend, but seriously.

https://increment.com/on-call/when-the-pager-goes-off/

@rcrelia

This comment has been minimized.

Show comment
Hide comment
@rcrelia

rcrelia May 26, 2017

Just looping back, I installed vim-mode-plus along with the updated version of ex-mode and I'm seeing full ex command capabilities that I didn't before... so thanks for that and the integration work. Cheers!

rcrelia commented May 26, 2017

Just looping back, I installed vim-mode-plus along with the updated version of ex-mode and I'm seeing full ex command capabilities that I didn't before... so thanks for that and the integration work. Cheers!

fritzherald added a commit to fritzherald/vim-mode that referenced this issue May 28, 2017

Create safeRemove method for normal-mode-input-element
normal-mode-input-element's @confirm, blur listener, and viewModel's
onDidFailToCompose handler can result in redundant calls to remove the
normal-mode-input-element. This commit makes removal idempotent.

Fixes #713
@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald Jun 3, 2017

@50Wliu @maxbrunsfeld I believe my PR is up to standards at this point (see commit ^^^). Please take another look.

fritzherald commented Jun 3, 2017

@50Wliu @maxbrunsfeld I believe my PR is up to standards at this point (see commit ^^^). Please take another look.

@mickenorlen

This comment has been minimized.

Show comment
Hide comment
@mickenorlen

mickenorlen Jun 9, 2017

i get this error whenever i use "r" to replace any single character.

mickenorlen commented Jun 9, 2017

i get this error whenever i use "r" to replace any single character.

@sarink

This comment has been minimized.

Show comment
Hide comment
@sarink

sarink Jun 15, 2017

I get this when I use "f" to jump to a character in a line

sarink commented Jun 15, 2017

I get this when I use "f" to jump to a character in a line

@maxbrunsfeld

This comment has been minimized.

Show comment
Hide comment
@maxbrunsfeld

maxbrunsfeld Jun 15, 2017

Contributor

@fritzherald I would go ahead and merge your PR, but our CI is failing, so I don't have a quick way to verify that it doesn't break anything.

Instead of putting any effort into this codebase, please use vim-mode-plus instead. It is very solid and well maintained, and it should be very easy to switch over. This package is deprecated. I'm sorry that we don't have the resources to maintain it, but we're a small team, there's a lot to do, and it just doesn't make sense when there is a great replacement out there already.

Contributor

maxbrunsfeld commented Jun 15, 2017

@fritzherald I would go ahead and merge your PR, but our CI is failing, so I don't have a quick way to verify that it doesn't break anything.

Instead of putting any effort into this codebase, please use vim-mode-plus instead. It is very solid and well maintained, and it should be very easy to switch over. This package is deprecated. I'm sorry that we don't have the resources to maintain it, but we're a small team, there's a lot to do, and it just doesn't make sense when there is a great replacement out there already.

@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald Jun 15, 2017

@maxbrunsfeld I don't see how my PR could break it any more than it's already broken — this is very easy to verify by using the current master version and then my version. I understand not wanting to put energy into maintaining a deprecated repo, but this is more like actively keeping a bug that breaks everything in order to force hundreds of thousands of installs to have to migrate whenever they happen to upgrade Atom, which could be in the middle of an insane work week as it was for me. Leaving this broken on purpose is not so cool, and definitely not in keeping with the deprecation notice in the readme.

The handling of this issue has given me serious questions about the future of Atom in general when so little regard is shown for the core experience for so many users. Please reconsider bringing down my changes, testing them, and merging my PR. Please also consider implementing a migration process that doesn't rely on breaking the editor.

fritzherald commented Jun 15, 2017

@maxbrunsfeld I don't see how my PR could break it any more than it's already broken — this is very easy to verify by using the current master version and then my version. I understand not wanting to put energy into maintaining a deprecated repo, but this is more like actively keeping a bug that breaks everything in order to force hundreds of thousands of installs to have to migrate whenever they happen to upgrade Atom, which could be in the middle of an insane work week as it was for me. Leaving this broken on purpose is not so cool, and definitely not in keeping with the deprecation notice in the readme.

The handling of this issue has given me serious questions about the future of Atom in general when so little regard is shown for the core experience for so many users. Please reconsider bringing down my changes, testing them, and merging my PR. Please also consider implementing a migration process that doesn't rely on breaking the editor.

@rcrelia

This comment has been minimized.

Show comment
Hide comment
@rcrelia

rcrelia Jun 15, 2017

@fritzherald I can understand your frustration. I was initially just as frustrated because I knew that ex-mode didn't work with vim-mode-plus. However, I recently did re-try using vim-mode-plus with the updated ex-mode and have been pleasantly surprised and have not experienced any loss of functionality. I made the switch a couple of weeks ago and it's been seamless. So, maybe that's the path of least resistance. Good luck!

rcrelia commented Jun 15, 2017

@fritzherald I can understand your frustration. I was initially just as frustrated because I knew that ex-mode didn't work with vim-mode-plus. However, I recently did re-try using vim-mode-plus with the updated ex-mode and have been pleasantly surprised and have not experienced any loss of functionality. I made the switch a couple of weeks ago and it's been seamless. So, maybe that's the path of least resistance. Good luck!

@maxbrunsfeld

This comment has been minimized.

Show comment
Hide comment
@maxbrunsfeld

maxbrunsfeld Jun 15, 2017

Contributor

definitely not in keeping with the deprecation notice in the readme.

Good point. I have updated the README to explain that we're not maintaining this package anymore.

so little regard is shown for the core experience for so many users.

Sorry for not communicating to you the extent to which we've abandoned this package. That was uncool. I get that you put in some work on this and so for you personally, it'd be nice to see it merged.

But we've been watching what has happened with vim-mode-plus. Overall, it's been great for us and our users that @t9md has taken the lead on maintaining Atom's vim mode. I don't think it's true what you are suggesting - that "many users" are severely impacted by having to apm remove vim-mode && apm install vim-mode-plus. I'm pretty confident that the vast majority of our users would prefer that I spend as much time as possible improving Atom's performance and building new features, not maintaining packages for which better replacements already exist.

Contributor

maxbrunsfeld commented Jun 15, 2017

definitely not in keeping with the deprecation notice in the readme.

Good point. I have updated the README to explain that we're not maintaining this package anymore.

so little regard is shown for the core experience for so many users.

Sorry for not communicating to you the extent to which we've abandoned this package. That was uncool. I get that you put in some work on this and so for you personally, it'd be nice to see it merged.

But we've been watching what has happened with vim-mode-plus. Overall, it's been great for us and our users that @t9md has taken the lead on maintaining Atom's vim mode. I don't think it's true what you are suggesting - that "many users" are severely impacted by having to apm remove vim-mode && apm install vim-mode-plus. I'm pretty confident that the vast majority of our users would prefer that I spend as much time as possible improving Atom's performance and building new features, not maintaining packages for which better replacements already exist.

@fritzherald

This comment has been minimized.

Show comment
Hide comment
@fritzherald

fritzherald Jun 15, 2017

Thanks for your response. I can see two solutions that are both far superior in my mind to letting thousands of users figure it out when everything breaks:

  1. Fix the immediate issue and add an alert when the plugin loads that includes a deprecation notice and the migration command
  2. Make this repo a mirror of vim-mode-plus (possibly combined with a deprecation notice)

This is not about me personally feeling good about getting a PR merged, it's about giving users a tangible heads-up and at least a token amount of consideration for the effect that finding your editor completely broken can have on a work day. Issues like this can seriously erode faith in the platform.

fritzherald commented Jun 15, 2017

Thanks for your response. I can see two solutions that are both far superior in my mind to letting thousands of users figure it out when everything breaks:

  1. Fix the immediate issue and add an alert when the plugin loads that includes a deprecation notice and the migration command
  2. Make this repo a mirror of vim-mode-plus (possibly combined with a deprecation notice)

This is not about me personally feeling good about getting a PR merged, it's about giving users a tangible heads-up and at least a token amount of consideration for the effect that finding your editor completely broken can have on a work day. Issues like this can seriously erode faith in the platform.

@maxbrunsfeld

This comment has been minimized.

Show comment
Hide comment
@maxbrunsfeld

maxbrunsfeld Jun 15, 2017

Contributor

Adding a deprecation notice is a good idea. I think we could just use atom.notifications inside of the activate hook.

Contributor

maxbrunsfeld commented Jun 15, 2017

Adding a deprecation notice is a good idea. I think we could just use atom.notifications inside of the activate hook.

@johanneserber

This comment has been minimized.

Show comment
Hide comment
@johanneserber

johanneserber Jun 18, 2017

@maxbrunsfeld really good idea. I didn't even know vim-mode it is deprecated until I ran into this error and read the issue here. The package description is probably going be missed out easily. A notification (popup) would be better.

johanneserber commented Jun 18, 2017

@maxbrunsfeld really good idea. I didn't even know vim-mode it is deprecated until I ran into this error and read the issue here. The package description is probably going be missed out easily. A notification (popup) would be better.

@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu Jun 20, 2017

Member

I am 👍 on adding a notification. However, we should probably only notify occasionally (maybe once per week?) so as to not annoy people 😀.

Member

50Wliu commented Jun 20, 2017

I am 👍 on adding a notification. However, we should probably only notify occasionally (maybe once per week?) so as to not annoy people 😀.

@jimmyhchan

This comment has been minimized.

Show comment
Hide comment
@jimmyhchan

jimmyhchan Aug 7, 2017

For those who just scrolled to the bottom:

  • vim-mode is dead
  • use vim-mode-plus instead
  • apm remove vim-mode && apm install vim-mode-plus

jimmyhchan commented Aug 7, 2017

For those who just scrolled to the bottom:

  • vim-mode is dead
  • use vim-mode-plus instead
  • apm remove vim-mode && apm install vim-mode-plus
@lagerratrobe

This comment has been minimized.

Show comment
Hide comment
@lagerratrobe

lagerratrobe Feb 6, 2018

Just my 2 cents.

  1. It's ridiculous to leave stupid bug in place like this when someone has gone through the work to find and code a fix for it - deprecated package or not. [Edit: ESPECIALLY when you can still download and install the package. What kind of definition of "deprecated" is that?]

  2. I am about to (attempt to) implement fritzherald's fix locally to get rid of the annoying and pointless error msg that pops up when I do a character replacement.

  3. This is a great reason for me to explore other IDEs

If there was ANY chance of getting me to move over to vim-mode-plus, or to keep using Atom, this issue pretty solidly has convinced me to just move on. I'm going to fix the issue locally just as an exercise to see whether it actually is as easy to take care of as it appears to be. [Edit: Yup, it's that easy to fix.]

Good day to you all.

lagerratrobe commented Feb 6, 2018

Just my 2 cents.

  1. It's ridiculous to leave stupid bug in place like this when someone has gone through the work to find and code a fix for it - deprecated package or not. [Edit: ESPECIALLY when you can still download and install the package. What kind of definition of "deprecated" is that?]

  2. I am about to (attempt to) implement fritzherald's fix locally to get rid of the annoying and pointless error msg that pops up when I do a character replacement.

  3. This is a great reason for me to explore other IDEs

If there was ANY chance of getting me to move over to vim-mode-plus, or to keep using Atom, this issue pretty solidly has convinced me to just move on. I'm going to fix the issue locally just as an exercise to see whether it actually is as easy to take care of as it appears to be. [Edit: Yup, it's that easy to fix.]

Good day to you all.

@50Wliu

This comment has been minimized.

Show comment
Hide comment
@50Wliu

50Wliu Feb 7, 2018

Member

We do not have the resources to maintain this package and cannot ensure that a potential fix will work as intended (though in this case I have no doubt that fritzherald's change works) or that we will be able to guarantee that it does not regress in the future. Therefore rather than merge PRs that we know we will be unable to support, we have been directing people to use vim-mode-plus, which has many more features than what vim-mode offered. In this way, potential contributors can consolidate their efforts to help make vim-mode-plus an even better package.

I see the next deprecation steps as:

  1. Adding a one-time or recurring notification to install vim-mode-plus (I will get on this shortly).
  2. Unpublishing vim-mode (though this will not affect current installs, which is why we have not unpublished it yet and went with adding a deprecation warning to the package description).
  3. Archiving this repository.

To reiterate migration instructions from above:

  • vim-mode is dead
  • use vim-mode-plus instead
  • apm remove vim-mode && apm install vim-mode-plus
Member

50Wliu commented Feb 7, 2018

We do not have the resources to maintain this package and cannot ensure that a potential fix will work as intended (though in this case I have no doubt that fritzherald's change works) or that we will be able to guarantee that it does not regress in the future. Therefore rather than merge PRs that we know we will be unable to support, we have been directing people to use vim-mode-plus, which has many more features than what vim-mode offered. In this way, potential contributors can consolidate their efforts to help make vim-mode-plus an even better package.

I see the next deprecation steps as:

  1. Adding a one-time or recurring notification to install vim-mode-plus (I will get on this shortly).
  2. Unpublishing vim-mode (though this will not affect current installs, which is why we have not unpublished it yet and went with adding a deprecation warning to the package description).
  3. Archiving this repository.

To reiterate migration instructions from above:

  • vim-mode is dead
  • use vim-mode-plus instead
  • apm remove vim-mode && apm install vim-mode-plus
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.