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. On Sep 26, 4:54 am, björn <[email protected]> wrote: > On 25 September 2010 22:16, Thomas <[email protected]> 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 -- 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
