You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What steps will reproduce the problem?
1. choose a dark colorscheme
2. maximize the window
What is the expected output? What do you see instead?
On the right side and bottom there will be a border that is the GTK default
border color. You may need to change the font size to see it properly, since
the border is the left-over space after gvim has filled the screen with the
maximum number of lines/cols that will fit in the window.
The ideal behavior would be that this border would be set to the same color as
the background of your color scheme, and changed when you change color schemes.
The border will still be there, but will be less of an eyesore.
In the discussions linked below people have also mentioned it would be nice if
vim was centered inside the available space rather than positioned at the
top-left, so the borders would be equal left-right and top-bottom. This sounds
good as well, but I would consider it secondary to the primary issue of the
border color.
What version of the product are you using? On what operating system?
gVim on Ubuntu 14.04
:version
VIM - Vi IMproved 7.4 (2013 Aug 10, compiled Jan 2 2014 19:39:47)
Included patches: 1-52
Modified by pkg-vim-maintainers@lists.alioth.debian.org
Compiled by buildd@
Huge version with GTK2-GNOME GUI ...
Please provide any additional information below.
Here's a good discussion of the issue:
http://vim.1045645.n5.nabble.com/Empty-lines-at-bottom-and-right-side-when-on-Fu
llscreen-td5709762.html
Also https://groups.google.com/forum/#!topic/vim_dev/hfN-kMZDAEY,
https://wiki.archlinux.org/index.php/Vim#Empty_space_at_the_bottom_of_gVim_windo
ws, and
http://stackoverflow.com/questions/12763692/paddings-around-the-actual-vim-windo
w-in-gvim
Original issue reported on code.google.com by jacksene...@gmail.com on 26 Mar 2015 at 8:35
Original issue reported on code.google.com by
jacksene...@gmail.com
on 26 Mar 2015 at 8:35Attachments:
The text was updated successfully, but these errors were encountered: