Philip, that PS is kind of pointless.
You can safely assume that people who do experience the bug do want to run gvim not vim, or they wouldn't care about this bug. Last but not least, even if you're running gvim from the K menu or any other setup that doesn't display stderr, output from stderr ends up in ~/.xsession-errors. That file just keeps growing and growing, and because it's a . file, you tend to forget about it when trying to figure out where all your disk space on /home went.
Launchpad lacks a setting that will tell people that this bug will be fixed for 10.04 but not for 9.10, so the folks using 9.10 will stop posting "affects me too" reports. ( By the way, should the "this bug affects me too" link on the top of the page be made more obvious? )
Philip, that PS is kind of pointless.
You can safely assume that people who do experience the bug do want to run gvim not vim, or they wouldn't care about this bug. Last but not least, even if you're running gvim from the K menu or any other setup that doesn't display stderr, output from stderr ends up in ~/.xsession-errors. That file just keeps growing and growing, and because it's a . file, you tend to forget about it when trying to figure out where all your disk space on /home went.
Launchpad lacks a setting that will tell people that this bug will be fixed for 10.04 but not for 9.10, so the folks using 9.10 will stop posting "affects me too" reports. ( By the way, should the "this bug affects me too" link on the top of the page be made more obvious? )