You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please note that this is not bug reporting, but just a suggestion.
Currently, some commands that may open quickfix window, if there's some error, cursor must be moved to first error or quickfix window itself (behavior depends on with bang or not) .
How about to add option (or as default behavior) not to be stealed cursor even if such command occurs some error?
Accoding to #1293 , I guess such feature was implemented in the past but currently not. If it is making senses, I'll try to create patch.
Thanks!
The text was updated successfully, but these errors were encountered:
bhcleek
added a commit
to bhcleek/vim-go
that referenced
this issue
Mar 29, 2019
What did you do? (required. The issue will be closed when not provided.)
I called
:GoBuild
or:GoMetaLinter
commands that will open quickfix on error.What did you expect to happen?
I don't want to lose focus from editing buffer.
What happened instead?
Cursor moves on first error (without bang) or moves to quickfix window (with bang).
Configuration (MUST fill this out):
17d4c08 (From master's latest at Mar 29, 2019)
vimrc
you used to reproduce (use a minimal vimrc with other plugins disabled; do not link to a 2,000 line vimrc):I use dein to manage plugin.
I'm sorry to say that this vimrc doesn't include installation of dein itself.
:version
):go version
):go env
):Remarks
Please note that this is not bug reporting, but just a suggestion.
Currently, some commands that may open quickfix window, if there's some error, cursor must be moved to first error or quickfix window itself (behavior depends on with bang or not) .
How about to add option (or as default behavior) not to be stealed cursor even if such command occurs some error?
Accoding to #1293 , I guess such feature was implemented in the past but currently not. If it is making senses, I'll try to create patch.
Thanks!
The text was updated successfully, but these errors were encountered: