Loading ...
Sorry, an error occurred while loading the content.

12129Re: maxvert doesn't always "maxvert"

Expand Messages
  • Björn Winckler
    Feb 22, 2011
    • 0 Attachment
      On Feb 21, 2011, at 11:44 PM, David Whetstone wrote:
      > Good
      >
      > -[MMWindowController enterFullscreen:backgroundColor:]@660: Delay enter full screen
      > -[MMWindowController setTextDimensionsWithRows:columns:isLive:keepOnScreen:]@311: setTextDimensionsWithRows:76 columns:239 isLive:0 keepOnScreen:1
      > -[MMVimController sendMessage:data:]@336: msg=SetWindowPositionMsgID (isInitialized=1)
      > -[MMVimController sendMessage:data:]@336: msg=SetWindowPositionMsgID (isInitialized=1)
      > -[MMFullscreenWindow enterFullscreen]@136: Enter full screen now
      >
      > Borked
      >
      > -[MMWindowController enterFullscreen:backgroundColor:]@660: Delay enter full screen
      > -[MMWindowController setTextDimensionsWithRows:columns:isLive:keepOnScreen:]@311: setTextDimensionsWithRows:80 columns:239 isLive:0 keepOnScreen:1
      > -[MMVimController sendMessage:data:]@336: msg=SetWindowPositionMsgID (isInitialized=1)
      > -[MMVimView(Private) frameSizeMayHaveChanged]@891: Notify Vim that text dimensions changed from 239x80 to 239x76 (SetTextDimensionsMsgID)
      > -[MMVimController sendMessage:data:]@336: msg=SetTextDimensionsMsgID (isInitialized=1)
      > -[MMVimController sendMessage:data:]@336: msg=SetWindowPositionMsgID (isInitialized=1)
      > -[MMFullscreenWindow enterFullscreen]@136: Enter full screen now
      >
      > It's consistent. There are two cases:
      >
      > 1. If I start up MacVim with MMAutosaveRows = 76 in my prefs
      > file, the first fullscreen window shows up ok, and subsequent
      > windows are borked. MMAutosaveRows changes to 80.
      >
      > 2. If instead I start up with MMAutosaveRows = 80, the first
      > fullscreen window shows up borked, and subsequent windows are
      > good. And, you guessed it, MMAutosaveRows goes back to 76.
      >
      > So, at this point I'm in need of a little guidance. There's a lot more I can say but as I implied above, I'm not sure which information is relevant. If any of this gives you any ideas of where to look, let me know.

      You seem to be using the :winpos command somewhere in your .[g]vimrc file or plugin. The problem may go away if you remove this command. Where/how do you use it? (I may be able to reproduce the bug this way.)

      Björn

      --
      You received this message from the "vim_mac" 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
    • Show all 17 messages in this topic