On 01/12/13 07:39, Roy Fulbright wrote:
>>> au GUIEnter * simalt ~x
>>
>> I've done it in the past with a combination of
>>
>> :winpos 0 0
>> :set lines=120 columns=80
>>
> Thanks for your reply. I am running on Windows 7. I do not need
> to know how to run maximized (running maximized is my problem). I
> need to figure out how to keep from running maximized.
Well, my expectation was that, if you had other ways it might be
maximizing, you could search your (g)vimrc for those and eliminate
them if you found them.
I haven't used Win7 for more than about 10min total in my life, so I
can't tell you much about it, but on the assumption that it's
somewhat like its predecessors, it's *possible* (though unlikely)
that whatever is launching vim uses
start /max gvim %1 %2 %3 ...
or something of the sort which would cause it to be maximized upon
startup. Otherwise, check your vimrc/gvimrc for either the "simalt
~x" line or a triad of winpos/'lines'/'columns' settings that would
give you the maximized behavior. Once you find it, you can nuke it.
-tim
--
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
Saturday, January 12, 2013
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment