Agreed. when developing, I jump around the source tree in my terminal and spawn gvims to load files.. often a few at a time. the auto-backgrounding feature of GVim is rather essential to this mode of operation, which I suspect is one of the main use cases of GVim. If dbusmenu can't handle programs which are backgrounded, that's a very serious design flaw in dbusmenu, and is most certainly a bug. I hit this every day at work and at home.
At the very least, is there some way to disable dbusmenu for GVim? a blacklist somewhere, perhaps?
Agreed. when developing, I jump around the source tree in my terminal and spawn gvims to load files.. often a few at a time. the auto-backgrounding feature of GVim is rather essential to this mode of operation, which I suspect is one of the main use cases of GVim. If dbusmenu can't handle programs which are backgrounded, that's a very serious design flaw in dbusmenu, and is most certainly a bug. I hit this every day at work and at home.
At the very least, is there some way to disable dbusmenu for GVim? a blacklist somewhere, perhaps?