> ---
> If vsplit could split the file into another window, that'd be great!
>
> But I want to be able to arrange the windows side-by-side -- maybe 1
> on each side or, rarely, maybe 2 on each side (one above another).
>
> Trying to simulate all of this in 1 window is near impossible,
> but being able to view multiple files at the same time in
> some side-by-side or one-on-top seems like a fairly basic
> desire. Right now, I have 10 different copies of gvim running,
> each with 2 files (c++ source & header) and another 4 copies
> with other work/projects in them. At times I have 6-8 gvim's
> open on my desktop each w/different files that I move between
> to analyze call paths between different modules.
>
> In this case, sometimes I want to view the header & c++ source
> side-by-side in two windows and when done, I'd like to move
> the header-file-window back into a tab of the source-file-window.
>
> When I have to make code changes in multiple windows, it is
> a hassle that I don't have the same history list in common
> so I can repeat commands in each window instead of having to type
> them, afresh, in each window.
>
> People who do development get larger screens and multiple screens
> so they can have multiple files and projects open at the same
> time.
>
> Does that help understand my use case?
>
> Thanks!
> Linda
How many windows do you need ? I've got 16 here in one frame.
Remember window size can be controlled by auto commands, i.e. automatically increase size when the cursor moves into it.
--
--
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.
Wednesday, April 5, 2017
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment