Bug 398525

Summary: kate: Add option to change default position/order for new document: LAST | FIRST
Product: [Applications] kate Reporter: LiuYan <moontide>
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED DUPLICATE    
Severity: wishlist    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
See Also: https://bugs.kde.org/show_bug.cgi?id=397913
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description LiuYan 2018-09-12 03:23:10 UTC
Currently, if I opened a new document, kate will put the document at the first position of document tabs.

I'd like to put it at the last position -- append to the document tabs, like many other text editors does.

It would be nice if I can change the position for new document.
Comment 1 Christoph Feck 2018-10-04 20:40:52 UTC
I don't think there should be an option. It's either A or B, and it doesn't make a difference, once you get used to it.
Comment 2 LiuYan 2018-10-09 09:58:44 UTC
(In reply to Christoph Feck from comment #1)
> I don't think there should be an option. It's either A or B, and it doesn't
> make a difference, once you get used to it.

I actually doesn't get used to it, like a right headed person doesn't get used to be left handed, or vice verse. 

That's actually one of several reasons that I didn't make kate as my default editor.

If there's such option, that would be great. If there're more order by options, that would be a significant improvement:
* add option to sort document view by open time, ascending or descending
* add option to sort document view by file name, ascending or descending
* add option to sort document view by file size, ascending or descending
* add option to sort document view by file modification time, ascending or descending
* add function to allow make a combination of above options, like 'ORDER BY colume1 ASC|DESC[, columnN ASC|DESC]...' clause in SQL script. (wait, too much? i know...)
Comment 3 Christoph Feck 2018-12-20 03:04:36 UTC

*** This bug has been marked as a duplicate of bug 390043 ***