This thread can only be closed by Nate Graham or people who have been tagged as Dolphin developers. This message is written for them. Not for obscure people with "stack overflow" editing syndrome. The reason for such a harsh statement: 1. Dolphin hasn't developed for ten years. The cosmetic effects that make this file manager look pretty don't count. 2. Dolphin cannot search for files. Built-in file search is not trustworthy, since it does not even have primitive settings (date, hidden, size, depth). Baloo is unable to search files adequately. Just try to find the file "baloofilerc" using the built-in search or baloo. Good luck! The problem is already 10 years old. 3. Dolphin is not able to work correctly with network folders. When I work, I feel almost real pain. Probably https://feverfew.home.blog/ will be implemented in Dolphin only after a millennium =) 4. Dolphin is not able to remember general parameters for all folders, as well as reset them (for old folders that already have ".directory") when this parameter is changed. 5. Dolphin is so strongly connected to KDE that it is impossible to painlessly replace it with another file manager. Without losing functionality. And here the user has a choice, either by losing the functionality and using another normal file manager, or the surrogate file manager Dolphin = ( 6. The only advantage of Dolphin over Nautilus is the functionality of "bookmarks", "entry points", "separate network folder", "restore tabs after restarting". In all other parameters, Dolphin is seriously inferior to Nautilus. 7. Restoration of previously opened tabs. This was the topic on the forum 8 years ago. And just recently this feature has become available. It was lightning fast. 8. If the folder is being read, no operations can be performed. This is very pronounced when working with network folders or connected devices. 9. The file manager is the backbone of the operating system. The user will work with this program most of the time. But KDE does not pay enough attention to this most important program (for the GUi). SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: KDE neon 5.20 (available in About System) KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2
If you have any specific bugs you want to report instead of unproductive rant, feel free to create separate actionable bug reports. I'm closing this again just similar to other bug report. If you continue reporting bugs like this it will result in ban.
(In reply to Bhushan Shah from comment #1) > If you have any specific bugs you want to report instead of unproductive > rant, feel free to create separate actionable bug reports. I'm closing this > again just similar to other bug report. If you continue reporting bugs like > this it will result in ban. I didn't see you being tagged as the author of Dolphin. Another one with stackoverflow syndrome. You don't do anything, but you still feel important.
This is not acceptable behavior. Cease it immediately. If you want to file real bug reports for the issues you face, please feel free to, with a separate bug report for each issue. Please stop filing bug reports in the form of hostile, abusive rants.
(In reply to Nate Graham from comment #3) > This is not acceptable behavior. Cease it immediately. > > If you want to file real bug reports for the issues you face, please feel > free to, with a separate bug report for each issue. Please stop filing bug > reports in the form of hostile, abusive rants. Don't make me angry. Why do weird people just close my report? This url https://bugs.kde.org/ I see as the only means of communication with those who can really solve problems in KDE and packages. Communicating with authors, not unknown people who have been endowed with moderator options.
Don't make *me* angry. You can communicate like a normal human being, or you can get banned. Your choice.
> 1. Dolphin hasn't developed for ten years. The cosmetic effects that make this file manager look pretty don't count. $ git shortlog -sn --all --since 2010 That shows more than 4.000 commits. hardly cosmetic as dolphin is mostly the same visuals since ever. > 2. Dolphin cannot search for files. Use KFind, or, Please provide patches. Opensource is a compromise that developers and users should work together and when one demands we need to remind him that software is build via community contributions, noone is getting paid to work on dolphin. > 3. Dolphin is not able to work correctly with network folders. Please provide patches. Dolphin received lots of patches for samba shares and other network formats. But demanding is not how things are done, you can either: Develop patches and send upstream, Pay a developer to provide patches upstream, or use another file manager. > 4. Dolphin is not able to remember general parameters for all folders Please provide patches. Every software has bugs and we need more people developing any software.If dolphin don't suit your needs, you also have krusader, konqueror, or the ones from other DE's like thunar and files. > 5. Dolphin is so strongly connected to KDE that it is impossible to painlessly replace it with another file manager. It's not. I use thunar and Files on my day to day usage. You can also use midnight commander, konqueror, krusader. 6. The only advantage of Dolphin over Nautilus is the... Good, if nautilus serves you better, you are of course welcome to use nautilus, there's no harm there. We KDE developers like and enjoy working with Gnome developers. > 7 Restoration of previously opened tabs. Good that someone took the time to do the patch, question, was it you? > 8 If the folder is being read, no operations can be performed. Please provide patches. > 9. The file manager is the backbone of the operating system. The user will work with this program most of the time. But KDE does not pay enough attention to this most important program (for the GUi). KDE doesn't pay, at all. All work is voluntary. Can you send patches?
(In reply to tcanabrava from comment #6) > > 7 Restoration of previously opened tabs. > > Good that someone took the time to do the patch, question, was it you? In fact, it was me. :)