https://bugs.kde.org/show_bug.cgi?id=438298
--- Comment #4 from Waqar Ahmed <waqar....@gmail.com> --- About point 3.. So, we can't ever get a one size fits all solution in any case, there can always be some path that is very long but anyways, this is besides the point. If you notice, Kate grays out the path a little bit while the filename stays "white" or whatever your primary foreground color is. The reason we do that is because we want filename to be the thing that you should be looking for without worrying about path. However, in some cases when you have multiple files with same name, for example CMakeLists.txt, you can do two things: - Type Cmklst, and navigate to the one you want by looking at the path - Filter by path directly, '/pth/toCmkl" The idea is to get you there quickly without you needing to read full paths. You read the path partially and you know that is what you want to open and hit enter just. The screenshot you posted has tons of redundant text, same path being repeated over and over again with some differences. This would make it harder to navigate and the longer it gets the harder it becomes to concentrate, imo. We try to minimize this as much as we can. Of course, we assume that the user has some knowledge of the folder he is in, so that they can navigate quickly. Lastly, I must mention that if you want to utilize quick-open in a more effective way, it is much better if you are working with a project, i.e., project opened inside kate. If you are unsure how to do that, just do "kate /path/to/folder". I hope my reasoning makes sense and is understandable. -- You are receiving this mail because: You are watching all bug changes.
