Opened 10 years ago

Closed 10 years ago

#4237 closed Bug (fixed)

transmission-remote -l shows torrent list in reverse order

Reported by: KyleK Owned by: jordan
Priority: Normal Milestone:
Component: Daemon Version: 2.22+
Severity: Normal Keywords:
Cc:

Description

transmission-remote by default displays the torrent list ordered by the torrent ID. I believe changeset r12424 causes the list to be in reverse order (newest torrent on top of the list, oldest at the bottom).

Change History (7)

comment:1 Changed 10 years ago by gunzip

i'm seeing the same reversing with r12426

comment:2 Changed 10 years ago by jordan

I agree with the analysis and have seen the same thing, but how is this a bug? The numbering is arbitrary, so what difference does it make?

comment:3 Changed 10 years ago by jordan

kylek, gunzip: ping

comment:4 Changed 10 years ago by KyleK

Well, it actually confuses me a lot. I usually have a few torrents seeding over a longer period of time, and then a couple of others that get removed fairly early after finishing. When the daemon is running over a longer period (a couple of days),this pushes the seeding torrents to the top of the list while new torrents get added to the bottom.

The new display completely reverses this and makes it harder for me to determine which IDs I have to delete/stop/change other values.

Could maybe transmission-remote do some magic to re-reverse the list, so we don't lose the CPU gains by r12424?

comment:5 Changed 10 years ago by livings124

Having it in torrent-id order makes a lot more sense to me than reverse-torrent-id order, even with some tiny speed gains.

Last edited 10 years ago by livings124 (previous) (diff)

comment:6 Changed 10 years ago by jordan

  • Milestone None Set deleted
  • Owner set to jordan
  • Status changed from new to assigned

ok

comment:7 Changed 10 years ago by jordan

  • Resolution set to fixed
  • Status changed from assigned to closed

r12434: revert r12424

Note: See TracTickets for help on using tickets.