https://bugs.kde.org/show_bug.cgi?id=507106
--- Comment #15 from Sanmay <[email protected]> --- A few points that in my opinion may be relevant here: 1. I think I may have kind of understood the reason behind differences in KWrite's users' opinion and the dev team's opinion on this matter (correct me if I'm wrong though). For the dev team, whether or not to implement a feature also involves a decision with regards to 'code complexity' (which seems substantial in this case). Whereas from user standpoint, its usually a matter of 'usage complexity'. As an example, for users, asking for support of a programming language, or multiple cursor support, would amount to complexity. 2. AFAIK, the extent to which 'code complexity' is taken into consideration when deciding upon whether to implement a feature (or in this case, to fix a bug) that balances 'usage complexity' is a matter of organization's internal policies. So yeah, I guess its up to the KDE Org policies and the devs to deliberate and decide. 3. One of the main reasons that users come here asking for help, and reporting bugs is likely because KWrite is distributed in reputed distributions like Fedora. If this is in fact an unmaintained application, I think such distribution's communities should be made aware of this fact in good faith (or public database be updated as may be the case as per KDE policies). This will allow them to move on to other applications for basic text editing that support basic features (like the feature/bugfix being discusses here). FeatherPad comes to mind as an alternative to KWrite. -- You are receiving this mail because: You are watching all bug changes.
