Friday, November 18, 2011

Re: Bug with tab drop and vertical splits?

On Nov 17, 10:40 pm, hsitz <hes...@gmail.com> wrote:
> Unless I'm misunderstanding something, tab drop is broken when there's
> a vertical split in the tab where the target file is.   Using Vim73.
> Here are steps to reproduce what I'm seeing, which seems like it can't
> be desired behavior:
>
> 1. edit mynewfile
> 2. vsplit
> 3. tab drop mynewfile
>
> Instead of moving to window that has mynewfile (or even staying in
> current window), the tab drop command opens up a new tab with
> mynewfile.  Subsequently issuing tab drop on the new tabs will open
> yet another tab with mynewfile, despite fact that each of those tabs
> has only single window.
>


I can reproduce this in 7.3.353 (Vim without Cream) build on Windows
XP 64-bit.

However, additionally, if the current buffer is the empty one from Vim
startup, no new tab is opened; :tab drop just opens it in the current
window.

Also, using my normal Vim config, but not when using gvim -N -u NONE -
i NONE, if I used vnew instead of vsp, the correct tab was jumped to
but the file was loaded in the empty buffer instead of the cursor
being positioned on the existing window.

> Behavior is as expected when the split in the windows is horizontal:
> tab drop stays on current tab.
>

I don't see this, with gvim -N -u NONE -i NONE, or with my normal Vim
config. Horizontal splits also break. But with my normal Vim config,
if I use :new instead of :sp, and if I move the :new window to the
bottom, then Vim correctly jumps to the correct buffer. However, the
window jumped to by :tab drop (with the correct buffer) has swapped
positions with this :new window, so that it is always on the bottom.

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

No comments: