           # Therefore it picks the end of the next word here (which is [3,3])
           # to start looking for the next word, which is also the end of the
           # buffer so the cursor never advances.
+          #
+          # See atom/vim-mode#3
           keydown('w', element: editor[0])
           expect(editor.getCursorScreenPosition()).toEqual([3,0])
 

          # FIXME: The definition of Cursor#getMovePreviousWordBoundaryBufferPosition
          # will always stop on the last word in the buffer. The question is should
          # we change this behavior.
          keydown('b', element: editor[0])
          expect(editor.getCursorScreenPosition()).toEqual [0,0]


      keydown('\\', element: editor[0])
      expect(editor.getText()).toEqual('')

    # FIXME: See atom/vim-mode#2
    xit "does not allow the cursor to be placed on the \n character, unless the line is empty", ->
      editor.setText("012345\n\nabcdef")
      editor.setCursorScreenPosition([0, 5])
