feature request: Vim windows (position) management improvement ?

37 views
Skip to first unread message

chris

unread,
Oct 6, 2012, 2:44:05 AM10/6/12
to Vim-dev
Here is the discussion.

https://github.com/xuhdev/SingleCompile/issues/16


--
[ stardiviner ] ^^&^^ {I hate all of you ! Leave me alone}
IRC(freenode): stardiviner \\ Twitter: @numbchild \\
GnuPG Key fingerprint
>>> 9BAA 92BC CDDD B9EF 3B36 CB99 B8C4 B8E5 47C3 2433
signature.asc

Christian Brabandt

unread,
Oct 6, 2012, 5:14:49 AM10/6/12
to Vim-dev
Hi chris!

On Sa, 06 Okt 2012, chris wrote:

> Here is the discussion.
>
> https://github.com/xuhdev/SingleCompile/issues/16

Can you be a little bit more specific, what your problem is and what you
like to be improved?

regards,
Christian
--
Eltern verzeihen ihren Kindern die Fehler am schwersten, die sie ihnen
selbst anerzogen haben.
-- Marie von Ebner-Eschenbach

chris

unread,
Oct 6, 2012, 5:27:17 AM10/6/12
to vim...@googlegroups.com
Excerpts from [ Christian Brabandt ] //// On [2012-10-06 11:14:49 +0200]:

> Hi chris!

> On Sa, 06 Okt 2012, chris wrote:

> > Here is the discussion.

> > https://github.com/xuhdev/SingleCompile/issues/16

> Can you be a little bit more specific, what your problem is and what you
> like to be improved?

Hmm, sorry, I do not know how to improve it, I just feel current Vim windows
position management is weak.
There is another example, If you use plugin `minibufexplr`, it should at top of
all windows. But when you execute command `:help` then the help window will be
at top of this `minibufexplr` window. This is not good, even though this is not
a big problem.

I guess the problem is `minibufexplr` can not always keep it's position on
top. I report this in Tagma_buffer_manage (a plugin similar with minibufexplr)
issues, but the author said it can not be changed. So now, I suggest vim-dev can
improve it. About how, and what on earth ? I guess I do not know. I'm sorry for
this bad implicit post.

> regards,
> Christian
> --
> Eltern verzeihen ihren Kindern die Fehler am schwersten, die sie ihnen
> selbst anerzogen haben.
> -- Marie von Ebner-Eschenbach

> --
> You received this message from the "vim_dev" 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
signature.asc

ZyX

unread,
Oct 6, 2012, 5:29:49 AM10/6/12
to vim...@googlegroups.com, cbl...@256bit.org
суббота, 6 октября 2012 г., 13:14:56 UTC+4 пользователь Christian Brabandt написал:
> Can you be a little bit more specific, what your problem is and what you
> like to be improved?

Annoying behavior of quicklist appearance: just like the OP, I would like to quickfix at the bottom of the current window, not at the bottom of rightmost window or at the bottom of all windows.

Note: according to the doc, `belowright copen` should make quickfix window appear at the bottom of the *current* window, but it still opens at the bottom of rightmost one. `belowright new` works as intended. Guess it needs to be a bug report in a separate thread (in the linked page nobody mentioned belowright).

chris

unread,
Oct 6, 2012, 5:56:05 AM10/6/12
to vim...@googlegroups.com
Excerpts from [ ZyX ] //// On [2012-10-06 02:29:49 -0700]:
I checked out command `:help :belowright`. I found it doesn't work for
`:execute` and `:normal`. Plugin SingleCompile code use `rightbelow` in `exec`.

> --
> You received this message from the "vim_dev" 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

signature.asc

ZyX

unread,
Oct 6, 2012, 6:12:34 AM10/6/12
to vim...@googlegroups.com
суббота, 6 октября 2012 г., 13:58:18 UTC+4 пользователь Pain Nagato написал:
> I checked out command `:help :belowright`. I found it doesn't work for
> `:execute` and `:normal`. Plugin SingleCompile code use `rightbelow` in `exec`.
False. It is meant there that

belowright execute 'new'
is not guaranteed to work (in fact it does not), but it was never meant that

execute 'belowright new'
won’t work.
Reply all
Reply to author
Forward
0 new messages