Version: (using KDE KDE 3.4.0) Installed from: Compiled From Sources Compiler: gcc-3.4.3 OS: Linux Dragging files and selected text from Konqueror or the Desktop into an open gvim window does not work. Cursor stays as the circle/slash icon and nothing happens on mouse button release. Drop+Drag between gvim and Konsole, gvim and Mozilla works as expected.
Dragging files works fine from Nautilus as well - just not from Konqueror. It's terribly irritating. (I'm running Mandrake 2006 = KDE 3.4.2).
confirmed for 3.5.4
I can confirm that dragging files from Konqueror (and also Dolphin) to gvim does not work with 3.5.9 (Kubuntu 8.04) and SVN trunk rev. 808111 (dragging a file to a KWrite window opens the file in KWrite). Dragging selected text from Konqueror doesn't work at all for me: If I click on a selected text area, it is unselected, so I can't drag it. Dragging text from Firefox to gvim works fine. Note that Konqueror isn't the only KDE app that shows this behaviour: Dragging selected text from one KWrite window to another one copies the text as expected, dragging text from KWrite to gvim does not work.
This Konqueror/GVim (maybe even KDE/GTK) behavior is still very annoying especially for opening files (here with KDE 3.5.9). I also made several tests in order to fix or at least get a possible workaround for this bug, but I seems that I need to know more about KDE internals in order to get any further results. As noted before, dragging any file from Konqueror/Desktop to an open GVim window does not work as expected, i.e. to open the file in the current Tab/Split, but if I press CTRL during dropping, it still seems to work as stated at the VIM documentation, it opens the file in a new split. So why does it not work for simple dropping (without any key)? I played a little bit with Klipper, but I found no real solution/workaround to this behavior. Could someone at least give me some details about this CTRL and no-CTRL behavior in KDE and if/how Klipper can intersect any standard drag-and-drop behavior in KDE?
KDE 3 is no longer maintained. If this issue is still present in KDE 4, feel free to reopen this ticket.