On Mon, Oct 29, 2018 at 11:25 AM Tony Mechelynck < [email protected]> wrote:
> On Mon, Oct 29, 2018 at 2:26 AM Kazunobu Kuriyama > <[email protected]> wrote: > > As far as X11 is concerned, whether or not attaching the task bar or the > title window to the window dedicated to gvim proper is determined by the > window manager in use with that gvim. Accordingly, if the window manager > is able to distinguish maximization from full screen, and if, by the user, > it is configured or set up properly to work differently for each > enlargement mode, gvim will/should behave as expected. Gvim itself doesn't > know about task bars or title windows which are to be used with it at all, > thus having no control over them, though it can provide some information > such as the file name in the current buffer to the window manager when > asked. > > > > Best regards, > > Kazunobu > > Well, in my current window manager (I think it is kdm but I'm not > sure) when I hit F11 (or when I use the menuitem View→Full Screen) in > a maximized SeaMonkey (which still has a titlebar, a menubar and a > statusbar) it becomes even bigger, taking up the whole screen, even > covering the clock topbar, the virtual desktops sidebar and the > applications footer bar normally provided by the window manager (or > something) and which "normally" maximized windows reach but don't > cover. (In that mode I can still change virtual desktops by hitting > Ctrl-Alt-Up, Ctrl-Alt-Down, or Ctrl-F1 to Ctrl-F8.) At the same time > the window decorations (titlebar etc.) disappear, and the whole > browser chrome becomes reduced to just a URL bar with a few buttons at > its right end to go back to normal operation. Menu bar, toolbars, etc. > disappear but the tab bar is still shown. This browser is compiled > with GTK3 GUI (its configure settings include > --enable-default-toolkit=cairo-gtk3 as shown on its about:buildconfig > page). So it is possible to program it, at least in a GTK3 program in > this particular window manager. I won't bet about other GUIs and/or > other WMs. > I think this is another issue different from the maximize/fullscreen issue we've been discussing. Rather, it's asking for a new feature that has gvim modify 'guioptions' automatically in accordance with a given enlargement mode at runtime, e.g., while keeping 'go' unchanged for maximization, do :set go-=m automatically for full screen, and revert to the normal user settings when it gets back to normal. Note that all gvim can control is those GUI components that are listed in :h 'go'. For them, I bet it is possible to add such a new feature with a programming on our side if the GUI toolkit used with gvim notifies the latter of the current enlargement mode via a GUI event. For other components, we definitely need the help of WMs. Best regards, Kazunobu > I still have no idea about the quantity of programming necessary to > make such a capability available in as many as possible of the GUIs I > mentioned in my previous post (when running in a WM that can do it). I > expect it to be a huge lot of work but I would be happy to be proved > false in this matter. > > Best regards, > Tony. > > -- > -- > You received this message from the "vim_dev" 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_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
