no windows on MacVim 7.3 (53) OSX 10.6.4

193 views
Skip to first unread message

Thomas

unread,
Sep 24, 2010, 2:51:36 PM9/24/10
to vim_mac
Opening MacVim either from the dock, the applications folder or
terminal ('open -a MacVim'), displays no window. Neither does Cmd-N
(New Window). However launching MacVim through it's binary ('mvim')
works just fine, although Cmd-N does not work.

I've read trough the ReportingBugs and none of those steps fixed the
problem. I've also searched the group and found two similar issues,
neither of which applies to me:

"No Window at all in Mac OS 10.5.2" (Posted 9/13/10)
- Logitech Control Center problem (I don't use LCC)

"No windows macvim 7.3 (and previous versions)" (Posted 3/15/08)
- mislocated Ruby library (Library is in correct location)

Please let me know if I can provide any more details or if you have
any suggestions for troubleshooting.

Thanks.

T

björn

unread,
Sep 25, 2010, 6:30:22 AM9/25/10
to vim...@googlegroups.com

I've not seen anything like this before. I'd be interested to know
what the debug logs say but in order to see them you need to enable
them first. To do so, open up Terminal.app and type

$ defaults write org.vim.MacVim MMLogLevel 7
$ sudo syslog -c syslogd -d

Now, quit MacVim, open Console.app and start MacVim again. Copy&paste
the output in Console.app. After you've done this, try starting
MacVim using the mvim script and copy&paste from Console.app again.

When done, you can reset the debug settings to normal as follows:

$ sudo syslog -c syslogd off
$ defaults delete org.vim.MacVim MMLogLevel


Björn

Thomas

unread,
Sep 25, 2010, 11:16:44 AM9/25/10
to vim_mac
Do you know which log I should be looking in?

I see the syslog commands showing up under Database Searches -> All
Commands, but starting MacVim or mvim generates nothing. Unless I'm
looking in the wrong place.

T

björn

unread,
Sep 25, 2010, 11:26:02 AM9/25/10
to vim...@googlegroups.com
On 25 September 2010 17:16, Thomas <tjl...@gmail.com> wrote:
> Do you know which log I should be looking in?
>
> I see the syslog commands showing up under Database Searches -> All
> Commands, but starting MacVim or mvim generates nothing. Unless I'm
> looking in the wrong place.

Hmmm...it should pop up under "All messages". Maybe it is easier if
you send the logs to stderr instead. Open Terminal.app and in
addition to the two commands I mentioned previously also type

$ defaults write org.vim.MacVim MMLogToStdErr 1

Then open MacVim via "open -a MacVim" and "mvim". The debug logs
should pop up in Terminal.app.

When done, in addition to the two steps in my previous post, also type

$ defaults delete org.vim.MacVim MMLogToStdErr


Björn

Thomas

unread,
Sep 25, 2010, 12:21:46 PM9/25/10
to vim_mac
here you go....

as you can see, opening the MacVim app doesn't write anything (but
does start application with no window), but mvim does.

Thanks.

T


$: defaults write org.vim.MacVim MMLogLevel 7
$: sudo syslog -c syslogd -d
Set ASL Data Store syslog filter mask: Emergency - Debug
$: defaults write org.vim.MacVim MMLogToStdErr 1
$: open -a MacVim
$: mvim
$: Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290]
<Debug>: gui_macvim_after_fork_init@120:
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
gui_mch_init@177:
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Info>: -[MMAppController applicationDidFinishLaunching:]@377: MacVim
finished launching
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController connectBackend:pid:]@1187: pid=49290
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Info>: -[MMVimView initWithFrame:vimController:]@98: Use renderer=0
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
gui_mch_new_colors@537: back=1f1f1f norm=dcdccc
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController(Private) addVimController:]@2208: Add Vim
controller pid=49290 id=1
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController(Private) activateWhenNextWindowOpens]@1960:
Activate MacVim when next window opens
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
gui_mch_init_font@913: font_name='(null)' fontset=0
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
gui_mch_get_screen_dimensions@1504: Columns=191 Rows=58
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
gui_mch_set_shellsize@1554: width=191 height=58 min_width=12
min_height=2 base_width=0 base_height=0 direction=15
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
SetDefaultColorsMsgID SetDefaultColorsMsgID AdjustLinespaceMsgID
SetFontMsgID SetWideFontMsgID ShowToolbarMsgID SetTextDimensionsMsgID
OpenWindowMsgID SetTooltipMsgID BatchDrawMsgID AddMenuItemMsgID(394)
AddMenuMsgID(32) EnableMenuItemMsgID(56) SetScrollbarPositionMsgID(1)
SetScrollbarThumbMsgID(1) ShowScrollbarMsgID(4)
CreateScrollbarMsgID(3)
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID SetDefaultColorsMsgID
SetDefaultColorsMsgID AdjustLinespaceMsgID SetFontMsgID
SetWideFontMsgID ShowToolbarMsgID SetTextDimensionsMsgID
OpenWindowMsgID SetTooltipMsgID BatchDrawMsgID AddMenuItemMsgID(394)
AddMenuMsgID(32) EnableMenuItemMsgID(56) SetScrollbarPositionMsgID(1)
SetScrollbarThumbMsgID(1) ShowScrollbarMsgID(4)
CreateScrollbarMsgID(3) >>>
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMVimController sendMessage:data:]@326:
msg=SetWindowPositionMsgID (isInitialized=1)
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Info>: -
[MMBackend registerServerWithName:]@1411: Registered server with name:
VIM
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
gui_mch_settitle@1595: title='[No Name] - VIM' icon='[No Name]'
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
SetServerNameMsgID SetPreEditPositionMsgID BuffersNotModifiedMsgID
SetWindowTitleMsgID SetDocumentFilenameMsgID SetPreEditPositionMsgID
BatchDrawMsgID SetScrollbarPositionMsgID(1) SetScrollbarThumbMsgID(1)
ShowScrollbarMsgID(1)
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend(Private) processInputQueue]@1822: (1)
SetWindowPositionMsgID
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend(Private) handleInputEvent:data:]@2069:
SetWindowPositionMsgID: x=84 y=878
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
BatchDrawMsgID
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMVimController sendMessage:data:]@326:
msg=SetWindowPositionMsgID (isInitialized=1)
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend(Private) processInputQueue]@1822: (1)
SetWindowPositionMsgID
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend(Private) handleInputEvent:data:]@2069:
SetWindowPositionMsgID: x=29 y=873
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
BatchDrawMsgID
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID SetServerNameMsgID
SetPreEditPositionMsgID BuffersNotModifiedMsgID SetWindowTitleMsgID
SetDocumentFilenameMsgID SetPreEditPositionMsgID BatchDrawMsgID
SetScrollbarPositionMsgID(1) SetScrollbarThumbMsgID(1)
ShowScrollbarMsgID(1) >>>
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMVimController sendMessage:data:]@326: msg=GotFocusMsgID
(isInitialized=1)
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend(Private) processInputQueue]@1822: (1) GotFocusMsgID
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
BatchDrawMsgID
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID BatchDrawMsgID >>>
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID BatchDrawMsgID >>>
Sat Sep 25 12:17:01 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID BatchDrawMsgID >>>
Sat Sep 25 12:17:02 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
BatchDrawMsgID
Sat Sep 25 12:17:02 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID BatchDrawMsgID >>>
Sat Sep 25 12:17:02 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMVimController sendMessage:data:]@326: msg=LostFocusMsgID
(isInitialized=1)
Sat Sep 25 12:17:02 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend(Private) processInputQueue]@1822: (1) LostFocusMsgID
Sat Sep 25 12:17:02 thomas-lahrs-macbook-pro.local Vim[49290] <Debug>:
-[MMBackend flushQueue:]@661: Flushing queue: SetVimStateMsgID
BatchDrawMsgID
Sat Sep 25 12:17:02 thomas-lahrs-macbook-pro.local MacVim[49291]
<Debug>: -[MMAppController processInput:forIdentifier:]@1227: QUEUE
for identifier=1: <<< SetVimStateMsgID BatchDrawMsgID >>>

björn

unread,
Sep 25, 2010, 12:31:12 PM9/25/10
to vim...@googlegroups.com
On 25 September 2010 18:21, Thomas <tjl...@gmail.com> wrote:
> here you go....
>
> as you can see, opening the MacVim app doesn't write anything (but
> does start application with no window), but mvim does.

You are right "open -a MacVim" does nothing...you'll have to use

$ /Applications/MacVim.app/Contents/MacOS/MacVim

instead (note "MacVim" at the end, not "Vim"). This is the log I'm
most interested in.

Björn

Thomas

unread,
Sep 25, 2010, 1:47:47 PM9/25/10
to vim_mac
$: /Applications/MacVim.app/Contents/MacOS/MacVim
Sat Sep 25 13:47:11 thomas-lahrs-macbook-pro.local MacVim[49828]
<Info>: -[MMAppController(Private) loadDefaultFont]@2118: Loading the
default font...
Sat Sep 25 13:47:12 thomas-lahrs-macbook-pro.local MacVim[49828]
<Debug>: -[MMAppController applicationOpenUntitledFile:]@456: Opening
untitled window...
Sat Sep 25 13:47:12 thomas-lahrs-macbook-pro.local MacVim[49828]
<Debug>: -[MMAppController newWindow:]@1075: Open new window
Sat Sep 25 13:47:12 thomas-lahrs-macbook-pro.local MacVim[49828]
<Debug>: -[MMAppController(Private)
executeInLoginShell:arguments:]@2252: new process pid=49831 (count=1)
Sat Sep 25 13:47:12 thomas-lahrs-macbook-pro.local MacVim[49828]
<Info>: -[MMAppController applicationDidFinishLaunching:]@411: MacVim
finished launching

Thomas

unread,
Sep 25, 2010, 1:50:49 PM9/25/10
to vim_mac
fwiw, Cmd-N (New Window) generates

Sat Sep 25 13:49:52 thomas-lahrs-macbook-pro.local MacVim[49875]
<Debug>: -[MMAppController(Private)
executeInLoginShell:arguments:]@2252: new process pid=49886 (count=2)

björn

unread,
Sep 25, 2010, 2:49:33 PM9/25/10
to vim...@googlegroups.com
On 25 September 2010 19:47, Thomas <tjl...@gmail.com> wrote:
> $: /Applications/MacVim.app/Contents/MacOS/MacVim
> Sat Sep 25 13:47:11 thomas-lahrs-macbook-pro.local MacVim[49828]
> <Info>: -[MMAppController(Private) loadDefaultFont]@2118: Loading the
> default font...

OK, this right here is very suspect...the code that loads the default
font was removed before the release of MacVim 7.3. Do you by any
chance have multiple versions of MacVim.app on your harddrive?

I suggest you delete all MacVim.app (search with Spotlight to find
them) from your hard drive, then re-download the latest version from:

http://github.com/b4winckler/macvim/downloads

and copy that to /Applications.

Let me know how it goes.

Björn

Thomas

unread,
Sep 25, 2010, 3:28:52 PM9/25/10
to vim_mac
I did find a couple of versions of MacVim on my harddrive, which I
wiped out. Still no windows however...

$: /Applications/MacVim.app/Contents/MacOS/MacVim
Sat Sep 25 15:26:23 thomas-lahrs-macbook-pro.local MacVim[66626]
<Debug>: -[MMAppController applicationOpenUntitledFile:]@422: Opening
untitled window...
Sat Sep 25 15:26:23 thomas-lahrs-macbook-pro.local MacVim[66626]
<Debug>: -[MMAppController newWindow:]@1005: Open new window
Sat Sep 25 15:26:23 thomas-lahrs-macbook-pro.local MacVim[66626]
<Debug>: -[MMAppController(Private)
executeInLoginShell:arguments:]@2108: new process pid=66628 (count=1)
Sat Sep 25 15:26:23 thomas-lahrs-macbook-pro.local MacVim[66626]
<Info>: -[MMAppController applicationDidFinishLaunching:]@377: MacVim
finished launching

T

björn

unread,
Sep 25, 2010, 3:42:49 PM9/25/10
to vim...@googlegroups.com
On 25 September 2010 21:28, Thomas <tjl...@gmail.com> wrote:
> I did find a couple of versions of MacVim on my harddrive, which I
> wiped out. Still no windows however...

This may be silly, but did you empty your Trash after deleting all the
old versions?

The debug logs tell me more or less nothing...I'll try to see if I can
think up what the problem may be.

In the meantime could you please try some older snapshots of
MacVim.app and see if they work -- if they do then I'd be interested
to know which version introduced this problem. You can find old
snapshots here:

http://code.google.com/p/macvim/downloads/list?can=1&q=&colspec=Filename+Summary+Uploaded+Size+DownloadCount

(Start with snap 52 and work your way towards older snaps.)

Thanks,
Björn

Thomas

unread,
Sep 25, 2010, 4:16:03 PM9/25/10
to vim_mac
Not silly at all! I totally forgot to empty the trash. However doing
so and going through the process again didn't change anything.

When I get some time, I'll start running through the various snapshots
and let you know what I find out.

T

On Sep 25, 3:42 pm, björn <bjorn.winck...@gmail.com> wrote:
> On 25 September 2010 21:28, Thomas <tjl...@gmail.com> wrote:
>
> > I did find a couple of versions of MacVim on my harddrive, which I
> > wiped out. Still no windows however...
>
> This may be silly, but did you empty your Trash after deleting all the
> old versions?
>
> The debug logs tell me more or less nothing...I'll try to see if I can
> think up what the problem may be.
>
> In the meantime could you please try some older snapshots of
> MacVim.app and see if they work -- if they do then I'd be interested
> to know which version introduced this problem.  You can find old
> snapshots here:
>
> http://code.google.com/p/macvim/downloads/list?can=1&q=&colspec=Filen...

björn

unread,
Sep 26, 2010, 4:54:05 AM9/26/10
to vim...@googlegroups.com
On 25 September 2010 22:16, Thomas <tjl...@gmail.com> wrote:
> Not silly at all! I totally forgot to empty the trash. However doing
> so and going through the process again didn't change anything.
>
> When I get some time, I'll start running through the various snapshots
> and let you know what I find out.

Ok, before doing so I'd like to know if there are any crash logs (they
should be in ~/Library/Logs/CrashReporter if I remember correctly)?
Specifically are there any reports of the Vim process crashing?

Can you also open Activity Monitor and see if any processes called Vim
are created when you press Cmd+N. From your logs it looks like they
are started ok but they never log anything so I'm not sure if they
exit immediately or just never start.

Finally, another thing to try is to create a new temporary user in
System Preferences (make it an Administrator to be on the safe side)
and switch over to that to see if a "clean" user has the same problems
(you can completely delete all traces of the temporary user when you
are done).

Hmmm...some more thoughts: do you use a non-standard file system (case
sensitive etc.)? Have you installed some "haxies" or apps that mess
around with the OS or Finder in some way?

Björn

Thomas

unread,
Sep 27, 2010, 1:11:57 AM9/27/10
to vim_mac
Solved!

Turns out I had a circular logic in my .bashrc that was causing it to
hang whenever I ran bash. Following your advice, I watched what was
happening in the system monitor and noticed that each Cmd-N was
creating a new bash process which would spike my cpu usage. Each new
window command created a new bash process would run and then crash
after a while. (Btw, there were no Vim crash reports in ~/Library/Logs/
CrashReporter, but there were a TON of bash crash reports.)

So I renamed my bash dot files and MacVim opened just fine, including
new windows. Great. I then went through the dot files and found the
offending code and changed it.

I should have caught this myself following the ReportingBugs wiki
page, but I when I read "temporarily rename your rc-files and .vim
directory", I only thought of the .vimrc file and ignored bash. Maybe
emphasizing 'all' rc-files might filter out more reports like these?

Anyway, thanks for your time and help. I hope this thread comes in
handy for somebody going through a similar issue.

T




I had recently been noticing it at the beginning of my terminal
sessions but just halted execution and told myself I'd get to it
later.

björn

unread,
Sep 27, 2010, 3:39:45 PM9/27/10
to vim...@googlegroups.com
On 27 September 2010 07:11, Thomas <tjl...@gmail.com> wrote:
> Solved!
>
> Turns out I had a circular logic in my .bashrc that was causing it to
> hang whenever I ran bash. Following your advice, I watched what was
> happening in the system monitor and noticed that each Cmd-N was
> creating a new bash process which would spike my cpu usage. Each new
> window command created a new bash process would run and then crash
> after a while. (Btw, there were no Vim crash reports in ~/Library/Logs/
> CrashReporter, but there were a TON of bash crash reports.)
>
> So I renamed my bash dot files and MacVim opened just fine, including
> new windows. Great. I then went through the dot files and found the
> offending code and changed it.
>
> I should have caught this myself following the ReportingBugs wiki
> page, but I when I read "temporarily rename your rc-files and .vim
> directory", I only thought of the .vimrc file and ignored bash. Maybe
> emphasizing 'all' rc-files might filter out more reports like these?
>
> Anyway, thanks for your time and help. I hope this thread comes in
> handy for somebody going through a similar issue.

Great that you figured it out. I'll update the ReportingBugs wiki to
include a step where all rc-files are renamed. Thanks for the
suggestion.

Björn

Reply all
Reply to author
Forward
0 new messages