vim - What is the most lovely layout of the editor window?
習慣沉默2017-05-16 16:41:12
0
11
1524
What is the best and most practical window layout when stacking?
Is it double columns, double rows, multiple rows and multiple columns, grid, or vertical T?
Or something else?
It doesn’t matter how many rows there are, nor does it matter what auxiliary windows are around it
The important thing is: there must be a girl behind you
Is there any girl who can see her combat power doubled? ! The code yields 1,800 per mu!
Well, I think as long as the editor layout can be changed by yourself and you remember that the layout can be changed, then after the code is written, you will naturally adjust the layout to what is most comfortable for you. Doing it deliberately will not improve efficiency
This is purely a matter of preference, and it often depends on the current local environment.
As a Vim fan, I don’t have any specific layout preferences. Anyway, Vim is very flexible in handling these, so I can use them wherever I want. When I go out, I only carry my laptop with me, and the screen is too small. I like large fonts, so I try to keep one file and one window full screen; I use Buffers/Tabs/CtrlP, etc. to handle multiple files. I occasionally use vertical split screen, and currently The active window will remain 80 columns wide. I don't really like the horizontal split screen, because the wide screen is relatively short, and you can't see many lines when you split it horizontally. I only split it horizontally when reading the help document.
If you have a big screen to serve you at home or in the office, you can do whatever you want. There won’t be any obstacles, and you won’t find any layout particularly attractive. I am writing code, not building a house...
Tmux will be turned on when doing Remote/Pair, but it is not necessary.
I think it depends on the needs. If the single file is relatively short, a single screen is enough.
If the file is long and you need to take care of both ends, open dual screens, with one screen above the file and one screen below the file.
If you need to take care of multiple files at the same time, open multiple screens.
I think the multiple screens should be used to make it easier to view files and improve efficiency.
Normally, I have dual screens. The laptop screen is too small. If it is divided too much, my eyes will not be able to see clearly!
Under vim, just use the command linevs, and in iTerm, just open tmux.
Writing code is not about being cool, just write good code!
It’s completely a personal preference. I like to make a file full screen, and my attention can be focused on the file I am editing. File explorers like nerdtree in vim don't like to keep opening them, and now I have given up using plug-ins to manage buffers. Tags don't like to be displayed all the time. I just need a shortcut key to call them out when needed.
The number of rows is more important, as is the convenience of switching. I prefer the design of zed editor. Up to three equal screens. Use ctrl+0 to switch, and ctrl+3 to create 3 rows. ctrl+2 creates 2 rows, ctrl+1 creates 1 row.
Actually, 1 row is used. I used two rows a few days ago because I wrote a code that needed to be rewritten, so I separated the old and new codes on both sides, and then reviewed and modified them. . .
Hide the file list view and the toolbar, leaving only the editing area. Then make the edit box full screen (similar to sublime's full screen function). In this way, the entire screen is just your code, without any interference. The world is clean and you can write your code with peace of mind.
If possible, you can configure a vertical monitor to increase the visible code space on one screen and reduce the constant scrolling of code.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
It doesn’t matter how many rows there are, nor does it matter what auxiliary windows are around it
The important thing is: there must be a girl behind you
Is there any girl who can see her combat power doubled? ! The code yields 1,800 per mu!
Well, I think as long as the editor layout can be changed by yourself and you remember that the layout can be changed, then after the code is written, you will naturally adjust the layout to what is most comfortable for you. Doing it deliberately will not improve efficiency
Full screen or dual column
This is purely a matter of preference, and it often depends on the current local environment.
As a Vim fan, I don’t have any specific layout preferences. Anyway, Vim is very flexible in handling these, so I can use them wherever I want. When I go out, I only carry my laptop with me, and the screen is too small. I like large fonts, so I try to keep one file and one window full screen; I use Buffers/Tabs/CtrlP, etc. to handle multiple files. I occasionally use vertical split screen, and currently The active window will remain 80 columns wide. I don't really like the horizontal split screen, because the wide screen is relatively short, and you can't see many lines when you split it horizontally. I only split it horizontally when reading the help document.
If you have a big screen to serve you at home or in the office, you can do whatever you want. There won’t be any obstacles, and you won’t find any layout particularly attractive. I am writing code, not building a house...
Tmux will be turned on when doing Remote/Pair, but it is not necessary.
I think it depends on the needs. If the single file is relatively short, a single screen is enough.
If the file is long and you need to take care of both ends, open dual screens, with one screen above the file and one screen below the file.
If you need to take care of multiple files at the same time, open multiple screens.
I think the multiple screens should be used to make it easier to view files and improve efficiency.
Normally, I have dual screens. The laptop screen is too small. If it is divided too much, my eyes will not be able to see clearly!
Under vim, just use the command line
vs, and in iTerm, just open tmux.Writing code is not about being cool, just write good code!
It’s completely a personal preference. I like to make a file full screen, and my attention can be focused on the file I am editing. File explorers like nerdtree in vim don't like to keep opening them, and now I have given up using plug-ins to manage buffers. Tags don't like to be displayed all the time. I just need a shortcut key to call them out when needed.
The number of rows is more important, as is the convenience of switching. I prefer the design of zed editor. Up to three equal screens. Use ctrl+0 to switch, and ctrl+3 to create 3 rows. ctrl+2 creates 2 rows, ctrl+1 creates 1 row.
Actually, 1 row is used. I used two rows a few days ago because I wrote a code that needed to be rewritten, so I separated the old and new codes on both sides, and then reviewed and modified them. . .
Hide the file list view and the toolbar, leaving only the editing area. Then make the edit box full screen (similar to sublime's full screen function). In this way, the entire screen is just your code, without any interference. The world is clean and you can write your code with peace of mind.
If possible, you can configure a vertical monitor to increase the visible code space on one screen and reduce the constant scrolling of code.
Single screen, divide it into one for reference, divide it into two for reference
It doesn’t matter how you lay it out, the key is to put the monitor up.
Whoever uses it knows.