@Kazunobu Kuriyama: Interesting post. I checked my dwm config.h and it is set to ignore size hints. I don't know what i3 does about this. But because it was easy, I changed the dwm config.h to respect those hints, rebuilt it, and restarted X with dwm as the wm. With this setup, gvim exhibits the same incorrect behavior when the font size is changed. As with i3, toggling the window state to floating and then back to tiled fixes the problem. But the point is that setting dwm to respect size hints does not fix the problem, as it apparently did when you tried this with Awesome.
/Don On Tue, Mar 10, 2015 at 8:24 AM, Donald Allen <[email protected]> wrote: > On Mon, Mar 9, 2015 at 11:05 AM, Christian Brabandt <[email protected]> > wrote: >> Am 2015-03-09 15:49, schrieb Donald Allen: >> >>> It turns out that the behavior I described in my original post >>> (shrinking the inner pane rather than displaying more text in the >>> full-sized pane when a smaller font-size is selected) appears to be >>> caused by tiling window managers and vim's interaction with them. The >>> original behavior was seen on an up-to-date 64-bit Arch Linux system >>> using just the xmonad window manager (no desktop system). On a hunch, >>> I tried the same thing (reducing the font size) while running fvwm >>> instead of xmonad and got exactly the behavior I wanted (the size of >>> the window and the text rectangle within it was unchanged and more >>> text was displayed). I then tried the same experiment with i3, another >>> tiling window manager like xmonad, and the behavior was the same as >>> observed with xmonad. So for this particular case, based on a small >>> amount of data, it appears that vim and tiling window managers are >>> conspiring to produce poor and unexpected behavior. It is possible to >>> do this correctly with tiling window managers; I just tested gedit and >>> emacs with i3, and making the font smaller works correctly in both >>> cases. >> >> >> Well, if you know more details, about the expected behaviour for tiling >> window managers (perhaps ask the xmonad/i3/awesome developers) and >> you can give us a clue, what would be expected, we might be able to fix >> that behavior. > > I've given you examples of other editors -- gedit and emacs -- that > handle this correctly. Their code is a major clue. > > Asking me to check with wm developers doesn't strike me as the best > way to approach this problem. I am not an expert on X client/X > server/window manager interactions. I also have not written this > editor; you (Bram and Co.) have, and therefore have the domain > knowledge. > > Despite my qualms about your suggestion, I did send an email to > Michael Stapelberg, the author of i3. I did so because I have > corresponded with him in the past and he is always helpful. His > response was that he suspected that finding this problem would require > "X11 wire-level protocol tracing". -- -- 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.
