Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove draw "0" under cursor #9

Merged
merged 1 commit into from
Feb 14, 2012
Merged

Remove draw "0" under cursor #9

merged 1 commit into from
Feb 14, 2012

Conversation

nevar
Copy link
Contributor

@nevar nevar commented Jan 14, 2012

vim --servername xxx --remote-expr yyy adds stdout to current buffer under
cersor. Added >/dev/null for Linux and >NUL for Windows for that command to
remove this behavior.

vim --servername xxx --remote-expr yyy adds stdout to current buffer under
cersor. Added >/dev/null for Linux and >NUL for Windows for that command to
remove this behavior.
@moorec
Copy link

moorec commented Feb 8, 2012

I also found a case where a 0 was making it onto the screen and only a redraw! would remove it. I tracked it down to the asynccommand#done function. It has no explicit return statement, so it returns 0 and somewhere along the way it makes it onto the screen. Adding a return '' made the symptom go away but I'm not sure if this is the right thing to do.

I wish I had more details to reproduce but I currently have a pretty hacked-up version of the script running to emulate flymake...

idbrii pushed a commit that referenced this pull request Feb 14, 2012
Remove draw "0" under cursor in console vim
@idbrii idbrii merged commit 576d83c into idbrii:master Feb 14, 2012
@idbrii idbrii mentioned this pull request May 10, 2012
idbrii pushed a commit that referenced this pull request Aug 9, 2012
While AsyncCommand uses remote-expr, we don't actually want any output
to be displayed, so always return an empty string.

As moorec commented on #9, it's possible for this function to output a 0
and for that to make it on the screen. Presumably that's not a problem
with vim because it's consistent enough about redrawing the screen. Gvim
doesn't let the output slip by.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants