By default, Vim will refuse to replace the current buffer with another one if it contains unsaved changes. You'll need to add the option below to your vimrc if you don't want that behavior (and you don't want that):
Buffers are Vim's equivalent of documents in other programs. When you switch to another document, you switch to another buffer. ...
From :h tab-page-intro:
A tab page holds one or more windows. You can easily switch between tab
pages, so that you have several collections of windows to work on different
Usually you will see a list of labels at the top of the Vim window, one for
each tab page.
Tabs containing windows is the way Vim was designed to work. I think you ...
No you can't, here's why:
Vim use multiple concepts to handle text files:
Buffer: An in-memory version of a file. Editing a file will in fact edit the buffer before writing (i.e. saving) anything to the file on your filesystem.
Window: A view into a buffer, a representation of the buffer content. A window can switch buffer and split to display multiple ...
In alternative to the maximized window, why do not gain more space for a full vim multiwindows editing experience with an autostart FULL SCREEN mode? ;-)
FULL SCREEN screenshot of the final result (= ALL THE VIDEO pixels capacity):
In my opinion that's better than a windows maximize: a complete FULL SCREEN (as I used to do with puTTY with ALT-Enter when ...
You can do this with | (on windows, in the _vimrc file, so you have to replace it with <bar>).
nnoremap <C-[> :set columns+=1 | lines+=1<CR>
nnoremap <C-[> :set columns+=1 <bar> lines+=1<CR>
See the documentation : :help :bar
From :help 'lines':
Number of lines of the Vim window.
When Vim is running in the GUI or in a resizable window, setting this
option will cause the window size to be changed.
You can use this command to get the tallest window possible:
The columns option does the same, except for the width (in characters).
So you ...
It appears as though your needs may be met by using tabs. See :help tabpage in Vim for general help, but here are a few relevant commands:
Start Vim with vim -p filename ... to open each file in a separate tab (Though this will be limited by the tabpagemax setting).
Move to the next tab with gt and the previous with gT.
:tabe or :tabedit will open a new tab ...
You need Vim 8.1, then you can use the following command:
:below terminal ++rows=10
Normally a terminal is opened above the current window, but with below it is opened at the bottom. And in this case, the terminal should have a height of 10 rows.
See :help :terminal for additional ++-options.
You can retrieve the window number (as opposed to the window ID) and then use wincmd to close:
let winnr = win_id2win(og)
if winnr > 0
execute winnr.'wincmd c'
Keep in mind this won't work if the window isn't in the current tab page.
Unfortunately there is no easy way to fix this at the moment, the OP has opened a vim-go issue and we agree that this is something vim-go can do better. Now we just need someone to spend time fixing it :-)
In the meanwhile, you can do some things to use ALE and vim-go simultaneously.
Setting g:go_list_type = 'locationlist' will make vim-go always use the ...
Starting vim using
vim -u NONE
won't work because you need a vimrc file with
filetype plugin on
The two settings are needed because "netrw" is actually a plugin distributed with vim by default, but still a plugin.
I would reccomend you to create an alternative vimrc to confirm that the issue is due to some settings in your vimrc. You can do ...
104 columns / 51 lines = 2.04
Your calculation is skewed because the aspect ratio of each cell is vertical.
For example on Terminal.app, with 23pt font and default character spacing, each terminal cell have a width of 7px and a height of 15px for a total of 728x765px:
You cannot retrieve the font size from within Vim without invoking external commands or ...
Registers are not shared between different Vim sessions. If you want that, then you have to store and load the data from a file. I think, the Yankring plugin does something like this.
Also it should be possible to write your viminfo using :wv file after you put something into your desired register and load it from the other vim session using :rv. See also ...
I would recommend you to use for example <C-P>, since <C-[> is the same as <Esc> and <C-]> is used to jump to a definition of the keyword under the cursor.
You can just do this:
nnoremap <C-P> <Esc>:set columns+=1 lines+=1<CR>
The another way is to use the command separator |, but you have to escape it or use <...