Starting GVim maximized

[Salman Halim]

Hello,

I recently switched from Windows GVim 32-bit to 64-bit and noticed that if I put 'simalt ~x' to start the window maximized, the tab bar at the top disappears. I have to restore/unmaximize to make it show up.

If I start GVim 64-bit unmaximized, let the window come up and THEN maximize it, either using the window or simalt ~x, then it's fine.

The menu and toolbar aren't affected by this, only the tab bar.

Is anybody else seeing this?

Thank you.

--

 
Salman

I, too, shall something make and glory in the making.

[meine]

On Mon, Dec 12, 2022 at 09:27:13AM -0500, Salman Halim wrote:
> Hello,
>
> I recently switched from Windows GVim 32-bit to 64-bit and noticed that if
> I put 'simalt ~x' to start the window maximized, the tab bar at the top
> disappears. I have to restore/unmaximize to make it show up.
>
> If I start GVim 64-bit unmaximized, let the window come up and THEN
> maximize it, either using the window or simalt ~x, then it's fine.
>
> The menu and toolbar aren't affected by this, only the tab bar.
>
> Is anybody else seeing this?

This behaviour probably is from the window manager of your operating system, not caused by Vim.

//meine

[Salman Halim]

It didn't happen with 32-bit GVim, only 64-bit. Could still be Windows, but seems odd. 

Salman

--
--
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+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/Y7V2mMm4r5%2BBQWBu%40trackstand.

[Alessandro Antonello]

Hi, 

First, sorry for top posting. I'm using a mobile version of Gmail and it didn't allow me to answer after the last message.

Windows 32 and Windows 64 are completely different APIs. So is really possible to have different behaviors on both GVim.

Also is possible that the behavior is caused by the 'simalt ~X' command been used too earlier. Try putting it in a timer, like 400ms after the GUIEnter autocommand. I had a similar problem when trying to open a NERDtree window automatically and solved that way.

To view this discussion on the web visit https://groups.google.com/d/msgid/vim_use/CANuxnEcqMinpu4PTxnzCEC7G1unMw8Ha-N%2BQ9Xxvfi5QnODkvw%40mail.gmail.com.

[Salman Halim]

On Wed, Jan 4, 2023 at 6:51 PM Alessandro Antonello <antone...@gmail.com> wrote:

Hi, 

First, sorry for top posting. I'm using a mobile version of Gmail and it didn't allow me to answer after the last message.

Yes, it's *really* difficult to do inline responses from the phone GMail app. In this day and age of smartphones being ubiquitous, I think we should relax our email list's rule against top-posting. The only reason I did all the cleanup here to remove the boilerplate signatures and older responses is that I'm on my laptop right now, from where it's much easier to select and delete text.

 

Windows 32 and Windows 64 are completely different APIs. So is really possible to have different behaviors on both GVim.

It still seems like a bit of a bug to me because it behaves fine in 32-bit, but hides the tab bar until I resize the window a second time. It's entirely possible the bug is in Windows and not Vim, as suggested by meine.

 

Also is possible that the behavior is caused by the 'simalt ~X' command been used too earlier. Try putting it in a timer, like 400ms after the GUIEnter autocommand. I had a similar problem when trying to open a NERDtree window automatically and solved that way.

Simply put, genius! I was able to put it in a timer, just like you said, but I noticed that timers don't fire until Vim is ready, so I was able to do this with a timer delay of 0. (I started with 400 and kept reducing it, figuring I would stop when it started failing.)

I did also try VimEnter instead of GuiEnter, but that didn't solve it, so I stuck with GuiEnter.

Thank you, Alessandro, and everybody else who took the time to indulge me. Much appreciated.

All the best,

Salman