Tuesday, March 14, 2017

Re: Vim maximise weirdness

On 14 March 2017 at 10:19, Christian Brabandt <cblists@256bit.org> wrote:
> Hi A.!
>
> On Di, 14 Mär 2017, A. S. Budden wrote:
>
>> This is probably one of the most minor problems I've ever had with
>> vim, but I thought I'd report it in case anyone understands what's
>> going on here.
>>
>> I've just (finally) decided to upgrade to Vim 8. I initially
>> installed the Windows executable version from
>> https://vim.sourceforge.io/download.php#pc but found it didn't support
>> python, so have compiled my own version.
>>
>> When I start gvim, I often want to immediately maximise the window and
>> have tended to do this with a simple mapping ("map ,x :simalt ~x<CR>")
>> - start gvim and hit ,x - this is pretty instinctive now! I know
>> there are probably other alternatives, but I like the default being
>> non-maximised and a quick key combination changing to maximised.
>>
>> With the newly compiled version of vim (details below), `:simalt ~x`
>> doesn't do quite what I was expecting: the window gets bigger but the
>> drawn area doesn't - https://snag.gy/3VfqUe.jpg
>>
>> Pressing Ctrl-L sorts it out, it's just slightly odd that it's not
>> redrawing to fill the screen. Clicking on the maximise icon in the
>> top right hand corner of the window works correctly - it's just simalt
>> ~x that doesn't. Note that this was all tested with -u NONE -U NONE.
>> With the current executable from the website (8.0.69), the behaviour
>> is correct.
>>
>> I know this is a really minor gripe; I just thought it was worth mentioning.
>>
>> The compiler configuration I use is made up of two scripts,
>> configure_vim.cmd (http://pastebin.com/QwKtCHvy) and build_vim.cmd
>> (http://pastebin.com/apxqsz6f). The :version information is here:
>> http://pastebin.com/raw/Gfusk1Fw
>
> Sounds familiar
> https://groups.google.com/d/msg/vim_dev/1vNlh9tBnCk/oP75NAT8AAAJ
>
> Unfortunately, there is no patch yet.

Aha, thanks Christian. Glad it's not just something I did when I
compiled Vim. Hopefully a patch will appear from someone who knows
their way round the vim source in due course.

Al

--
--
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.

No comments: