On Thu, Jan 14, 2016 at 8:44 AM, Nikolay Aleksandrovich Pavlov
<zyx.vim@gmail.com> wrote:
>
> Firefox manages multiple X windows by one instance, and it was originally
> developed for graphical environment. Gvim has one process (and one instance)
> per one X window, doing no management of its windows. Vim originally
> developed for terminals and many GUI features are missing simply because
> they are not possible in terminal (though still there are such features,
> there are not much).
>
So if a feature is useful in the graphical version (i.e. gvim) but is
not doable in the console vim, it wont be implemented? That argument
seems a bit backward. From a user perspective, they are two different
programs and it is ok to have a feature in one but in the other.
> I would though ask why do you need this functionality in first place. I
> never had enough tabs open to want detaching, perhaps you are misusing this
> feature.
>
When I code in large C++ projects, I have many tabs open in one gvim
window. This window spans across one whole monitor. Now when writing
new code to call a function, I want to split two tabs from this window
and move them to the second monitor. These tabs typically contain the
header file, another C++ file where a function was used before. This
way I can look at the API, sample usage and add code in the current
window.
thanks
raju
--
Kamaraju S Kusumanchi | http://raju.shoutwiki.com/wiki/Blog
--
--
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
---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
No comments:
Post a Comment