Version: (using KDE KDE 3.5.5) Installed from: Gentoo Packages OS: Linux When dragging and dropping a folder from konqueror onto kate file list sidebar, the folder is opened as a file (that is obviously empty). It should not be opened but cause the file list to chdir to that folder.
Can reproduce in KDE 3.5.8 and KDE 4. Actually, I think there are several issues about this at once (if you can't deal with them in one go, tell me to split them into separate reports). 1) Bad error message: Kate should indicate that the URL can't be opened because it's a folder, not due to missing permissions. It's smart enough to do that from the commandline. 2) Kate needs to be smarter about where and how to drops. Right now, it seems to attempt to open a file, whereever the url is dropped. However, a) This does not make sense at all in most tool views. b) The behavior in the filesystem browser should probably be different (original report). c) In the text area, the filename should be inserted (note how it even shows a drop marker, which seems to indicate that the dragged object will be inserted *inside* the current document). d) When dealing with this, note the related wishes bug #148389 and bug #148390 .
I can confirm this still, and I think kate should either open all the files inside the folder or just display the file open dialog browsing the dropped folder. I don't agree with c) on comment #1: I drag files inside kate all the time, I would hate it if instead of opening them, kate started just writing their urls.
The drop event is received by the editor component, which can not open all the files on its own. But it could sure open a file dialog. To be able to let the user open more files, the host application would need a signal, and that would require an interface in KTextEditor to provide taht I believe.
*** Bug 169159 has been marked as a duplicate of this bug. ***
I've committed a somewhat dumb implementation. You'll need to be careful what folders you drop on kate. It'll happily open up / and all files below it. If there are any huge problems with the current behavior, please open up a new bug :)
*** Bug 323924 has been marked as a duplicate of this bug. ***