Skip to content

Screen error #721

Closed
Closed

Description

@lkebin

I have extra monitor. When I start MacVim on the extra monitor, it looks like that:
screen shot 2018-08-06 at 11 41 51 am

If I drag the MacVim program window to resize it, the screen will be fine.
macvim

Activity

  1. changed the title [-]Screen deranged[/-] [+]Screen error[/+] on Aug 6, 2018
  2. mikedupuis commented on Aug 6, 2018

    @mikedupuis

    I can confirm that I'm seeing the same issue on a second monitor.

  3. lowderchris commented on Aug 6, 2018

    @lowderchris

    Running into the same issue (and resizing fix) on an external DisplayPort monitor. With the same monitor connected, when opening a macvim window on the laptop display, the window renders as expected.

  4. Paultergeist commented on Aug 6, 2018

    @Paultergeist

    The issue appeared in snapshot-150, snapshot-149 was good.

  5. fortman commented on Aug 6, 2018

    @fortman

    +1 , same issue here. Resizing window with mouse makes the window immediately snap to correct size

  6. JTMosaic commented on Aug 6, 2018

    @JTMosaic

    +1, same issue. Attempting to roll back to 149

  7. tachijuan commented on Aug 6, 2018

    @tachijuan

    +1 here. If you open on the main monitor, it works just fine. If you open it on the second (non-main) monitor you get the behavior described

  8. dctucker commented on Aug 6, 2018

    @dctucker
    Contributor

    +1 Confirmed. This is particularly troubling since I want MacVim to always launch on my rightmost monitor.

  9. ahmedelz commented on Aug 6, 2018

    @ahmedelz

    +1

  10. eirnym commented on Aug 6, 2018

    @eirnym
    Contributor

    +1

  11. muddysteel commented on Aug 7, 2018

    @muddysteel

    +1 same issue.

  12. elithecho commented on Aug 7, 2018

    @elithecho

    +1

  13. eirnym commented on Aug 7, 2018

    @eirnym
    Contributor

    The same is happening when you open a narrow window, for example, 69x42, and then open a window with local setting set width (or height) bigger than it was. Any way to force redrwaw works, including hiding MacVim or switching an app

    Build 149 didn't had this issue.

  14. fericit-bostan commented on Aug 7, 2018

    @fericit-bostan

    +1

  15. rbm-aalsaleh commented on Aug 7, 2018

    @rbm-aalsaleh

    +1

  16. 7 remaining items

  17. davidozog commented on Aug 9, 2018

    @davidozog

    +1

  18. jadeallenx commented on Aug 9, 2018

    @jadeallenx

    +1

  19. ZGainsforth commented on Aug 9, 2018

    @ZGainsforth

    +1

  20. xuyuheng commented on Aug 10, 2018

    @xuyuheng

    +1

  21. ychin commented on Aug 10, 2018

    @ychin
    Member

    I submitted a PR #727 to revert the change that introduced this bug. If someone can grab it and build locally to test it out that would be appreciated. I'm not at a place to be able to test external monitors right now.

  22. dctucker commented on Aug 10, 2018

    @dctucker
    Contributor

    Building ychin's branch solved the problem for me. Can anyone else confirm?

  23. ychin commented on Aug 12, 2018

    @ychin
    Member

    The same is happening when you open a narrow window, for example, 69x42, and then open a window with local setting set width (or height) bigger than it was. Any way to force redrwaw works, including hiding MacVim or switching an app

    @eirnym Can you explain a little more in how your repro case worked? What commands are you running?

  24. eirnym commented on Aug 12, 2018

    @eirnym
    Contributor
    1. Open a window with a random file, e.g. ~/.vim/vimrc and set some small width, like 20, next time it should open a window with the same width, you can check it by pressing Cmd-N
    2. set for some filetype specific width to use, e.g. for Python files (it doesn't matter)
    3. open file of this type, with $ vim ~/example.py or with :e ~/example.py

    Notes:
    if you don't open a file but an empty buffer on step 1, MacVim might won't save and trick won't work from command line but will with :e command in the same window

      if has('gui_running')
            setlocal columns=85
        endif

    A quick demonstration
    out

  25. eirnym commented on Aug 13, 2018

    @eirnym
    Contributor

    @ychin Is my way to reproduce is good enough?

  26. ychin commented on Aug 14, 2018

    @ychin
    Member

    @eirnym I couldn't reproduce the issue on my laptop. Did you only reproduce this using your method on an external monitor? If so I just need to hunt down an external monitor to connect to so I can debug it.

  27. eirnym commented on Aug 14, 2018

    @eirnym
    Contributor

    @ychin I have no external monitor

    my minimal vimrc with I able to reproduce it (build 150)

    fun! PythonSetup()
        setlocal ts=4 sts=4 sw=4 nu
        setlocal colorcolumn=79
        if has('gui_running')
            setlocal columns=85
        endif
    endfun
    
    autocmd FileType python call PythonSetup()
  28. eirnym commented on Aug 15, 2018

    @eirnym
    Contributor

    @ychin The problem with my issue is somewhere else, it's reproducable in build 122 (earlier builds don't want to be opened on my setup ;) )

    I'll open a separate issue

  29. ychin commented on Aug 16, 2018

    @ychin
    Member

    @eirnym Oh good to know. But also sad that that means I will have to hunt down an external monitor to test still.

    Also check out #557 which I suspect could be related. You can try the suggestions from this comment (#557 (comment)) to see if it helps by setting MMUseCGLayerAlways to true. It causes other issues such as scrolling performance but it's nice to know if it's related at least.

  30. eirnym commented on Aug 16, 2018

    @eirnym
    Contributor

    @ychin please, look into #732, it could be the source of many resizing issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions