Bug 271941

Summary:	[PATCH] Remember the moved tab positions in Tabify plugin
Product:	[Applications] kate	Reporter:	Tao Bao <rehash_fd>
Component:	general	Assignee:	KWrite Developers <kwrite-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	christoph
Priority:	NOR	Keywords:	triaged
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	make tabs movable and remember the moved positions on re-opening

Description Tao Bao 2011-04-28 22:40:04 UTC

Created attachment 59403 [details]
make tabs movable and remember the moved positions on re-opening

Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

This is a follow-up patch for bug #266530.

With the patch of #266530, the tabs in Tabify plugin become movable. However, their positions are not kept after closing the session. Because the moved positions are kept locally in m_docList, which will be lost after exiting. With
this updated patch, it changes the order of document list maintained by
Kate's document manager. So that documents (and tabs) will be listed according
to their latest positions on re-opening.

Reproducible: Always

Steps to Reproduce:
With the patched version of tabify (from bug #266530):

1. Move the tab position;
2. Close kate;
3. Restart kate.

Actual Results:  
Tab positions are restored to the order before the moves in step 1.

Expected Results:  
Tab positions should be of the same order as last exiting.

Comment 1 Christoph Cullmann 2012-11-01 16:31:45 UTC

Sorry, but the document list can not be resorted this way, that will break havok in all other parts of Kate App. If you want to have this, please implement this in the tabify plugin alone and provide a new patch. Sorry for the inconvenience, but the document list order really should have no semantics.

Comment 2 Andrew Crouthamel 2018-09-23 02:40:17 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!

Comment 3 Andrew Crouthamel 2018-10-27 03:49:22 UTC

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!