search

lalitmetkar / vim

Automatically exported from code.google.com/p/vim
0 stars 0 forks source link

wincmd inside of if block #53

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
- What steps will reproduce the problem?
:if 0 | wincmd p | endif

- What is the expected output? What do you see instead?
It is expected that the comand executes and return to normal mode. Instead it 
remains in command mode waiting for 'endif'.
The fault doesn't happen with the following commands:

:if 1 | wincmd p | endif

:if 0 | exe "wincmd p" | endif

In the documentation there is a patch that solves a similar problem, which is 
possibly incomplete:

    Patch 6.1.177 (depends on 6.1.141)
    Problem:    ":wincmd" does not allow a following command. (Gary Johnson)
    Solution:   Check for a following " | cmd".  Also give an error for trailing
           characters.
    Files:      src/ex_docmd.c

Best regards,
mMontu

Original issue reported on code.google.com by marcmo...@gmail.com on 29 Feb 2012 at 2:50

GoogleCodeExporter commented 9 years ago 
I cannot reproduce the problem.
What is your version of Vim?

Original comment by br...@google.com on 29 Feb 2012 at 4:07

GoogleCodeExporter commented 9 years ago 
I've tested on Vim 7.2 (Huge version without GUI - Cygwin) and Vim 7.3 (Big 
version with GUI - ms windows).

I've tried starting Vim with '$vim -N -u -U NONE' to ensure that there is no 
script interfering with this behavior but the fault still occurs.

Original comment by marcmo...@gmail.com on 29 Feb 2012 at 4:53

GoogleCodeExporter commented 9 years ago 
The problem also happens with the newest gVim on www.vim.org ('PC: MS-DOS and
MS-Windows' - gvim73_46.exe) with no _vimrc or vimfiles).

Original comment by marcmo...@gmail.com on 29 Feb 2012 at 5:02

GoogleCodeExporter commented 9 years ago 
This was supposed to be fixed in patch Patch 7.3.217.
It appears all the versions you tried are older than that.

Original comment by brammool...@gmail.com on 29 Feb 2012 at 8:32

GoogleCodeExporter commented 9 years ago 
The last patch mentioned on the versions I've tested is Patch 7.2.446, so it
probably doesn't contains the solution you mentioned.

If there is already a patch for this problem this issue may be closed.
I'll wait for the next version.

Thanks!

Original comment by marcmo...@gmail.com on 29 Feb 2012 at 8:56

GoogleCodeExporter commented 9 years ago 
Let's assume this was fixed by Patch 7.3.217.

Original comment by brammool...@gmail.com on 29 Feb 2012 at 9:23