When target doesn't exist, no error, and command is put into undo history

[jsit]

Say I have this line, because I just installed targets.vim and am playing:

asdf;asdf;asdf;asdf;asdf;asdf;asdf;asdf;asdf;asdf;asdf

With my cursor somewhere in that line, I start typing da; over and over again until I end up with this:

asdf;asdf

Pressing da; again doesn't do anything, of course, because there is only one semicolon left. But there is no error, and the command is entered into the undo history. For instance, if at this point I (ineffectively) hit da; three times, I have to hit u three times to "actually start undoing" and get my text back to where it was before the last successful da;.

[wellle]

You are right, it should not be put into the undo history. I will have to look into it and see how to avoid that.

I wouldn't say that there should be an error message though. Stock Vim doesn't complain about missing text objects either.

[jsit]

If not a message, then at least a bell (which I do hear for missing standard text objects).

On Fri, Feb 7, 2014 at 11:19 AM, Christian Wellenbrock <
notifications@github.com> wrote:

You are right, it should not be put into the undo history. I will have to
look into it and see how to avoid that.

I wouldn't say that there should be an error message though. Stock Vim
doesn't complain about missing text objects either.

Reply to this email directly or view it on GitHubhttps://github.com//issues/4#issuecomment-34460385
.

[wellle]

Oh that's a good point. I have turned the bell off in my terminal, that's why I didn't notice. Thank you!