> +file_in_path +find_in_path +float +folding -footer +fork() +fullscreen > +digraphs +dnd -ebcdic +emacs_tags +eval +ex_extra +extra_search +farsi > +conceal +cryptv +cscope +cursorbind +cursorshape +dialog_con_gui +diff > +clientserver +clipboard +cmdline_compl +cmdline_hist +cmdline_info +comments ![]() > +arabic +autocmd +balloon_eval +browse ++builtin_terms +byte_offset +cindent > Compiled by Huge version with MacVim GUI. > sudo port install MacVim +huge +python32 +cscope > that backtrace is reproducible when binding to MacVim with gdb everytime it is hanging. ![]() > #3 0x00007fff84cefef0 in ActionDataToServer () > #2 0x00007fff84cf04e9 in SSClient_AudioServicesSetActionDataMessageAsync () > Here is how I realized it was supposed to be playing a sound: > - Using a guest account on my mac which has the default vim/MacVim configuration > - Renaming ~/.vimrc, ~/.gvimrc, and ~/.vim > - Navigating to the top or bottom of a file and attempting to navigate past the beginning or end of it. > - Pressing the escape key when in normal mode > Every time an OS X "beep" warning sound should be played, my MacVim buffer hangs for a few seconds before becoming responsive again, and no sound is played. ![]() On Saturday, J10:28:22 PM UTC-7, Colin Sullivan wrote: #3 0x00007fff84cefef0 in ActionDataToServer () #2 0x00007fff84cf04e9 in SSClient_AudioServicesSetActionDataMessageAsync () This one has a slightly different backtrace: I also can reproduce this with filesystem autocomplete in command mode, i.e.Įxhibits the same halting behavior.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |