Using Vim/Gvim with multiple GUI windows
Is it possible to have 2 or more (G)vim windows for the same session, or at least share some buffers. Here, "window" refers to a Gnome(or KDE, or Windows etc.) window, not a VIM window.
I use two monitors with xinerama and want to open two separate GUI windows instead of having a huge single one that spans multiple screens.
multiple-monitors vim multiple-instances
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
add a comment |
Is it possible to have 2 or more (G)vim windows for the same session, or at least share some buffers. Here, "window" refers to a Gnome(or KDE, or Windows etc.) window, not a VIM window.
I use two monitors with xinerama and want to open two separate GUI windows instead of having a huge single one that spans multiple screens.
multiple-monitors vim multiple-instances
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
have you tried :sp <filename> or :vsp <filename> ? This are vim's window splitting commands and they're great. Here's some documentation
– Tom Stephens
Jan 19 '11 at 3:53
2
@Tom Stephens: and that helps .. how? OP wants to position the vim-windows of ONE vim instance across his monitors. OP does not want ONE vim instance spanned across all monitors.
– akira
Jan 19 '11 at 8:28
1
This is important; the editor should not really be doing it's own window management.
– Sam Watkins
Oct 2 '12 at 2:40
add a comment |
Is it possible to have 2 or more (G)vim windows for the same session, or at least share some buffers. Here, "window" refers to a Gnome(or KDE, or Windows etc.) window, not a VIM window.
I use two monitors with xinerama and want to open two separate GUI windows instead of having a huge single one that spans multiple screens.
multiple-monitors vim multiple-instances
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
Is it possible to have 2 or more (G)vim windows for the same session, or at least share some buffers. Here, "window" refers to a Gnome(or KDE, or Windows etc.) window, not a VIM window.
I use two monitors with xinerama and want to open two separate GUI windows instead of having a huge single one that spans multiple screens.
multiple-monitors vim multiple-instances
multiple-monitors vim multiple-instances
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
asked Jan 18 '11 at 13:21
Atilla Filiz
3723919
3723919
have you tried :sp <filename> or :vsp <filename> ? This are vim's window splitting commands and they're great. Here's some documentation
– Tom Stephens
Jan 19 '11 at 3:53
2
@Tom Stephens: and that helps .. how? OP wants to position the vim-windows of ONE vim instance across his monitors. OP does not want ONE vim instance spanned across all monitors.
– akira
Jan 19 '11 at 8:28
1
This is important; the editor should not really be doing it's own window management.
– Sam Watkins
Oct 2 '12 at 2:40
add a comment |
have you tried :sp <filename> or :vsp <filename> ? This are vim's window splitting commands and they're great. Here's some documentation
– Tom Stephens
Jan 19 '11 at 3:53
2
@Tom Stephens: and that helps .. how? OP wants to position the vim-windows of ONE vim instance across his monitors. OP does not want ONE vim instance spanned across all monitors.
– akira
Jan 19 '11 at 8:28
1
This is important; the editor should not really be doing it's own window management.
– Sam Watkins
Oct 2 '12 at 2:40
have you tried :sp <filename> or :vsp <filename> ? This are vim's window splitting commands and they're great. Here's some documentation
– Tom Stephens
Jan 19 '11 at 3:53
have you tried :sp <filename> or :vsp <filename> ? This are vim's window splitting commands and they're great. Here's some documentation
– Tom Stephens
Jan 19 '11 at 3:53
2
2
@Tom Stephens: and that helps .. how? OP wants to position the vim-windows of ONE vim instance across his monitors. OP does not want ONE vim instance spanned across all monitors.
– akira
Jan 19 '11 at 8:28
@Tom Stephens: and that helps .. how? OP wants to position the vim-windows of ONE vim instance across his monitors. OP does not want ONE vim instance spanned across all monitors.
– akira
Jan 19 '11 at 8:28
1
1
This is important; the editor should not really be doing it's own window management.
– Sam Watkins
Oct 2 '12 at 2:40
This is important; the editor should not really be doing it's own window management.
– Sam Watkins
Oct 2 '12 at 2:40
add a comment |
4 Answers
4
active
oldest
votes
Currently gVim cannot have separate 'toplevel' windows for the same process/session. There is a TODO item to implement an inter-process communication system between multiple Vim instances to make it behave as though the separate processes are unified. (See :help todo and search for "top-level".)
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
1
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
add a comment |
Take a look at GNU screen used in conjunction with Vim.
First window, start up gnu screen and vim
xterm
screen -S edit
vim
Second window, connect to screen session:
xterm
screen -x edit
Incredibly useful over large xinerama desktops, multiple virtual screens, or VNC sessions. One session of Vim, with lots of tabs, is all you need.
-- Tom
answered Dec 11 '11 at 2:31
Tom
311
1
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
add a comment |
It's been some time since you asked your question and many things have improved. Nvidia has much better driver support for multiple monitors on Linux.
I've now stopped using Gvim since I moved over to KDE: Now I'm using vim-qt. It allows you to open multiple instances, in case you don't want to use vim in the terminal.
edit:
answered Nov 12 '12 at 10:06
jollyroger
294
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
5
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
add a comment |
You can have as many vi(m) sessions as you want by using separate terminal windows for each.
As for not having them span across, I assume you are putting them to full screen and then it is expanding across both monitors as it is set to an extend the desktop. Don't maximize it and manually adjust the terminal or gvim window size.
If I missed the mark please try to elaborate a little more.
What do you mean by vim window?
edit: 
Hopefully Heptite hit it, because I was kind of lost with this one.
answered Jan 18 '11 at 14:17
Dan M.
1,656117
1
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f234708%2fusing-vim-gvim-with-multiple-gui-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
Currently gVim cannot have separate 'toplevel' windows for the same process/session. There is a TODO item to implement an inter-process communication system between multiple Vim instances to make it behave as though the separate processes are unified. (See :help todo and search for "top-level".)
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
1
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
add a comment |
Currently gVim cannot have separate 'toplevel' windows for the same process/session. There is a TODO item to implement an inter-process communication system between multiple Vim instances to make it behave as though the separate processes are unified. (See :help todo and search for "top-level".)
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
1
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
add a comment |
Currently gVim cannot have separate 'toplevel' windows for the same process/session. There is a TODO item to implement an inter-process communication system between multiple Vim instances to make it behave as though the separate processes are unified. (See :help todo and search for "top-level".)
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
Currently gVim cannot have separate 'toplevel' windows for the same process/session. There is a TODO item to implement an inter-process communication system between multiple Vim instances to make it behave as though the separate processes are unified. (See :help todo and search for "top-level".)
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
answered Jan 18 '11 at 18:53
Heptite
14.8k54157
14.8k54157
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
1
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
add a comment |
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
1
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
7 years later, Vim8, this is still in the todo list.
– Al.G.
Apr 1 '18 at 22:10
1
1
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
Donate to the Vim charity and get votes, then vote for the feature: vim.org/sponsor/index.php
– Heptite
Apr 1 '18 at 22:13
add a comment |
Take a look at GNU screen used in conjunction with Vim.
First window, start up gnu screen and vim
xterm
screen -S edit
vim
Second window, connect to screen session:
xterm
screen -x edit
Incredibly useful over large xinerama desktops, multiple virtual screens, or VNC sessions. One session of Vim, with lots of tabs, is all you need.
-- Tom
answered Dec 11 '11 at 2:31
Tom
311
1
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
add a comment |
Take a look at GNU screen used in conjunction with Vim.
First window, start up gnu screen and vim
xterm
screen -S edit
vim
Second window, connect to screen session:
xterm
screen -x edit
Incredibly useful over large xinerama desktops, multiple virtual screens, or VNC sessions. One session of Vim, with lots of tabs, is all you need.
-- Tom
answered Dec 11 '11 at 2:31
Tom
311
1
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
add a comment |
Take a look at GNU screen used in conjunction with Vim.
First window, start up gnu screen and vim
xterm
screen -S edit
vim
Second window, connect to screen session:
xterm
screen -x edit
Incredibly useful over large xinerama desktops, multiple virtual screens, or VNC sessions. One session of Vim, with lots of tabs, is all you need.
-- Tom
answered Dec 11 '11 at 2:31
Tom
311
Take a look at GNU screen used in conjunction with Vim.
First window, start up gnu screen and vim
xterm
screen -S edit
vim
Second window, connect to screen session:
xterm
screen -x edit
Incredibly useful over large xinerama desktops, multiple virtual screens, or VNC sessions. One session of Vim, with lots of tabs, is all you need.
-- Tom
answered Dec 11 '11 at 2:31
Tom
311
answered Dec 11 '11 at 2:31
Tom
311
answered Dec 11 '11 at 2:31
Tom
311
answered Dec 11 '11 at 2:31
Tom
311
311
1
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
add a comment |
1
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
1
1
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
Points for the quick and brief tutorial, although I would call this only slightly useful, because I cannot edit different buffers of the same session this way.
– Atilla Filiz
Dec 12 '11 at 10:04
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
interestingly this is a point where screen wins over tmux, - in tmux attaching to the same session from a different client means you just see things mirrored across both instances... I'm considering some unholy combination of the two but haven't quite figured out what I want to do yet!
– Jonny Leeds
Jan 10 '18 at 13:21
add a comment |
It's been some time since you asked your question and many things have improved. Nvidia has much better driver support for multiple monitors on Linux.
I've now stopped using Gvim since I moved over to KDE: Now I'm using vim-qt. It allows you to open multiple instances, in case you don't want to use vim in the terminal.
edit:
answered Nov 12 '12 at 10:06
jollyroger
294
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
5
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
add a comment |
It's been some time since you asked your question and many things have improved. Nvidia has much better driver support for multiple monitors on Linux.
I've now stopped using Gvim since I moved over to KDE: Now I'm using vim-qt. It allows you to open multiple instances, in case you don't want to use vim in the terminal.
edit:
answered Nov 12 '12 at 10:06
jollyroger
294
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
5
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
add a comment |
It's been some time since you asked your question and many things have improved. Nvidia has much better driver support for multiple monitors on Linux.
I've now stopped using Gvim since I moved over to KDE: Now I'm using vim-qt. It allows you to open multiple instances, in case you don't want to use vim in the terminal.
edit:
answered Nov 12 '12 at 10:06
jollyroger
294
It's been some time since you asked your question and many things have improved. Nvidia has much better driver support for multiple monitors on Linux.
I've now stopped using Gvim since I moved over to KDE: Now I'm using vim-qt. It allows you to open multiple instances, in case you don't want to use vim in the terminal.
edit:
answered Nov 12 '12 at 10:06
jollyroger
294
edited Nov 23 '12 at 15:07
answered Nov 12 '12 at 10:06
jollyroger
294
answered Nov 12 '12 at 10:06
jollyroger
294
answered Nov 12 '12 at 10:06
jollyroger
294
294
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
5
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
add a comment |
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
5
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
I am trying it now, how do I use these multiple instances? It looks like regular gvim with a slightly different face to me.
– Atilla Filiz
Nov 14 '12 at 8:16
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
You can just start two instances of vim-qt so you can have one window for each of your screens and alt-tab betwen them, or assign hotkeys to each window. Vim-qt is written for qt, so qt-based desktop environments like KDE can utilize the windows better. That means you get to have several different graphical windows open and that your graphical vim windows can be full screen. Which was not possible with regular gvim.
– jollyroger
Nov 23 '12 at 14:53
5
5
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
Thanks for taking the time but this is not what I wanted. I wanted to access the same buffers from two separate GUI windows. And this is not possible as buffer sharing is still in to-do list of vim(see the accepted answer).
– Atilla Filiz
Nov 26 '12 at 10:28
add a comment |
You can have as many vi(m) sessions as you want by using separate terminal windows for each.
As for not having them span across, I assume you are putting them to full screen and then it is expanding across both monitors as it is set to an extend the desktop. Don't maximize it and manually adjust the terminal or gvim window size.
If I missed the mark please try to elaborate a little more.
What do you mean by vim window?
edit:
Hopefully Heptite hit it, because I was kind of lost with this one.
answered Jan 18 '11 at 14:17
Dan M.
1,656117
1
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
add a comment |
You can have as many vi(m) sessions as you want by using separate terminal windows for each.
As for not having them span across, I assume you are putting them to full screen and then it is expanding across both monitors as it is set to an extend the desktop. Don't maximize it and manually adjust the terminal or gvim window size.
If I missed the mark please try to elaborate a little more.
What do you mean by vim window?
edit:
Hopefully Heptite hit it, because I was kind of lost with this one.
answered Jan 18 '11 at 14:17
Dan M.
1,656117
1
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
add a comment |
You can have as many vi(m) sessions as you want by using separate terminal windows for each.
As for not having them span across, I assume you are putting them to full screen and then it is expanding across both monitors as it is set to an extend the desktop. Don't maximize it and manually adjust the terminal or gvim window size.
If I missed the mark please try to elaborate a little more.
What do you mean by vim window?
edit:
Hopefully Heptite hit it, because I was kind of lost with this one.
answered Jan 18 '11 at 14:17
Dan M.
1,656117
You can have as many vi(m) sessions as you want by using separate terminal windows for each.
As for not having them span across, I assume you are putting them to full screen and then it is expanding across both monitors as it is set to an extend the desktop. Don't maximize it and manually adjust the terminal or gvim window size.
If I missed the mark please try to elaborate a little more.
What do you mean by vim window?
edit:
Hopefully Heptite hit it, because I was kind of lost with this one.
answered Jan 18 '11 at 14:17
Dan M.
1,656117
edited Jan 18 '11 at 19:01
answered Jan 18 '11 at 14:17
Dan M.
1,656117
answered Jan 18 '11 at 14:17
Dan M.
1,656117
answered Jan 18 '11 at 14:17
Dan M.
1,656117
1,656117
1
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
add a comment |
1
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
1
1
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
That is exactly what I am doing now, manually resize them to span two monitors and then :vsplit but it looks ugly and sometimes I want to see some buffers on different virtual desktops, or cover one monitor with something else. What I want is to use two differnet terminals ans still access the same buffers from both of them.
– Atilla Filiz
Jan 19 '11 at 9:00
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
I understand now. Glad to see Heptite answered that for you.
– Dan M.
Jan 19 '11 at 13:23
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f234708%2fusing-vim-gvim-with-multiple-gui-windows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
have you tried :sp <filename> or :vsp <filename> ? This are vim's window splitting commands and they're great. Here's some documentation
– Tom Stephens
Jan 19 '11 at 3:53
2
@Tom Stephens: and that helps .. how? OP wants to position the vim-windows of ONE vim instance across his monitors. OP does not want ONE vim instance spanned across all monitors.
– akira
Jan 19 '11 at 8:28
1
This is important; the editor should not really be doing it's own window management.
– Sam Watkins
Oct 2 '12 at 2:40