Jeroen Budts <[email protected]> wrote: > Hi All, > > (First off, I hope this is the correct mailinglist to report this. I first > tried > vim_use but didn't get any response, sorry if I'm wrong here.) > > A few days ago I started using AwesomeWM (running as the WM inside > XFCE) and started seeing Gvim crashes (SEGV & ABRT) when I resize > the Gvim window (by changing the size of the master pane in the > tile-layout and by switching layouts). From what I understand these > indicate bugs? > I have been using Gvim for a few years now without much problems > under XFCE + XFWM (default Xubuntu). I also used Xmonad for one > week without problems.
Hi Jeron I tried to reproduce the crash but I could not. My setup is a bit different since I used xubuntu-15.10 and my own build of vim-7.4.1817. I cloned your https://github.com/teranex/dotvim repo + added pathogen. I got errors when starting vim with your .vimrc so it seems that your git repo is missing a plugin: Error detected while processing /home/pel/.vimrc: line 280: E117: Unknown function: Pl#Theme#InsertSegment line 281: E117: Unknown function: Pl#Theme#RemoveSegment line 282: E117: Unknown function: Pl#Theme#RemoveSegment line 284: E117: Unknown function: Pl#Theme#RemoveSegment line 285: E117: Unknown function: Pl#Theme#RemoveSegment line 286: E117: Unknown function: Pl#Theme#RemoveSegment line 287: E117: Unknown function: Pl#Theme#ReplaceSegment line 288: E117: Unknown function: Pl#Theme#ReplaceSegment line 289: E117: Unknown function: Pl#Theme#InsertSegment When doing :e .vimrc I also get errors: Error detected while processing BufRead Auto commands for "*": E492: Not an editor command: Rooter E492: Not an editor command: :DetectIndent I installed awesome but I did not see any crash in vim. I resized Vim, also pressed Window+Space to change the layout in awesome and did not see crash. But you might be doing something else that cause the crash. I'm not familiar with the awesome window manager so I only tried basic things. Please try to build the latest vim with debug symbols so we have good stack traces, and try with valgrind as suggested earlier email. Regards Dominique -- -- You received this message from the "vim_dev" 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
