Version: unspecified OS: Linux firstly not sure where this problem goes and who has to fix it I am using SUSE 11.3 and Dolphin. lets say you are opening fstab~ (the backup file created by kwrite) using dolphin. but because the thing (not sure what) dont recognise the file you are clicking on (if you clicked on fstab it would open with kwrite, however this is different) it says there is no application installed that can open the files of type "backup file" (do you want to install one). you choose "no" (hmm might report this as a bug to suse). and dolphin asks you what program to open it with. you want to choose Kwrite as that was what created it. you know it is under "utilities" which is the second last one. so you click on the [+] sign beside the word "utilities" and it opens it. however, what i expect it to do now is scroll down so that "utilities" is now at the top so i can see all the items under "utilities". but instead i have to do it. call me lazy but these little things speed up productivity - especailly when time is your most precious asset! Charlie. Reproducible: Always
click the Maximize Button with the Middle button (System Settings > Window Properties -> Titlebar Actions) or type kwrite or type e (for editor) after linking /usr/bin/kwrite -> ./bin/e
i am suggesting some extra "artificial intelligence" so i can work faster. for me its faster to move the mouse to the object then to take my hand off the mouse and type kwrite, i am suggesting that i have one less object to click when choosing items in lists, by having it autoscroll. as for e, the error i get in the scenario i posted above is "e not found please type a valid program name"
type in Konsole: ln -s /usr/bin/kwrite ./bin/e which e /home/charlie/bin/e dir ./bin/e lrwxrwxrwx 1 charlie users 15 22. Sep 15:41 ./bin/e -> /usr/bin/kwrite
Hi, kdelibs (version 4 and earlier) is no longer maintained since a few years. KDE Frameworks 5 or 6 might already have implemented this wish. If not, please re-open against the matching framework if feasible or against the application that shows the issue. We then can still dispatch it to the right Bugzilla product or component. Greetings Christoph Cullmann