https://bugs.kde.org/show_bug.cgi?id=507106
--- Comment #19 from Christoph Cullmann <[email protected]> --- (In reply to Nate Graham from comment #18) > I don't have a comment on the implementation, but to me, in terms of UX, > being tab-based means externally-opened documents should be opened in new > tabs. > > If this is technically problematic, it may make sense to change the > implementation to share more code between KWrite and Kate, or remove the > feature from KWrite and let Kate be the tab-based app. Sorry, but that makes no sense for me, we had exactly the other request in the past to have there tabs, just like they are now. That we don't share instances doesn't break the tab feature. And if one really wants all that, one can use Kate. Sharing instances will make all other use of KWrite harder, like for using it as git commit editor. Shall it block? Shall it not? We have all that in Kate and I don't see we need that there. -- You are receiving this mail because: You are watching all bug changes.
