Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sorting of panels after Ctrl+u is broken after 4.8.27 #4432

Closed
mc-butler opened this issue Jan 16, 2023 · 7 comments
Closed

Sorting of panels after Ctrl+u is broken after 4.8.27 #4432

mc-butler opened this issue Jan 16, 2023 · 7 comments
Assignees
@aborodin
Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress ver: 4.8.28 Reproducible in version 4.8.28
Milestone
4.8.30

Comments

@mc-butler
Copy link

Important

This issue was migrated from Trac:

Origin https://midnight-commander.org/ticket/4432
Reporter a.panov (panov@….iacp.dvo.ru)

In version 4.8.27 and earlier, if the panels are sorted in a certain way (for example, left by name, and right by change date in reverse order), then after Ctrl+u the contents of the panels change, and the sorting remains the same. In versions 4.8.28, 4.8.29, the sorting reverts.
For example, it becomes in the left panel by the change date in direct order, and in the right panel by the name in the opposite.
Please return the behavior of version 4.8.27.
@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jan 16, 2023 at 10:24 UTC (comment 1)

Options -> Panel options... -> Simple swap

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Jan 29, 2023 at 8:46 UTC (comment 2)

  • Milestone Future Releases deleted
  • Status changed from new to closed
  • Resolution set to worksforme

@mc-butler
Copy link
Author

Changed by a.panov (panov@….iacp.dvo.ru) on Feb 1, 2023 at 8:38 UTC (comment 3)

It was introduced by commit [d07abec] on Mar 13, 2022. Do you have any reason to revert ordering on each panel swapping?

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 1, 2023 at 12:20 UTC (comment 4)

  • Status changed from closed to reopened
  • Version changed from master to 4.8.29
  • Resolution worksforme deleted
  • Milestone set to 4.8.30

You're right, that is my mistake.

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 1, 2023 at 12:21 UTC (comment 5)

  • Owner set to andrew_b
  • Status changed from reopened to accepted

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 1, 2023 at 17:57 UTC (comment 6)

  • Resolution set to fixed
  • Status changed from accepted to testing
  • Version changed from 4.8.29 to 4.8.28
  • Votes set to committed-master

[cce50e5]

@mc-butler
Copy link
Author

Changed by andrew_b (@aborodin) on Feb 1, 2023 at 17:58 UTC (comment 7)

  • Status changed from testing to closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@aborodin aborodin

Labels
area: core Issues not related to a specific subsystem prio: medium Has the potential to affect progress ver: 4.8.28 Reproducible in version 4.8.28
Milestone
4.8.30
Development

No branches or pull requests
2 participants
@aborodin @mc-butler