Opened 13 years ago
Closed 13 years ago
#3338 closed Bug (invalid)
transmission-remote --uplimit only accepts integers
Reported by: | Darwin | Owned by: | |
---|---|---|---|
Priority: | Normal | Milestone: | None Set |
Component: | Daemon | Version: | 2.00 |
Severity: | Normal | Keywords: | |
Cc: |
Description
transmission-remote -t 1 --uplimit 2.00 Not a number: "2.00"
This should accept floats.
Running svn r10820
Change History (5)
comment:1 Changed 13 years ago by livings124
comment:2 Changed 13 years ago by charles
- Component changed from CLI to Daemon
- Resolution set to invalid
- Status changed from new to closed
I agree with livings. transmission-remote could be coded to accept floats here, but I don't see any practical use case for it.
comment:3 Changed 13 years ago by Darwin
- Resolution invalid deleted
- Status changed from closed to reopened
I suggest the info option in transmission-remote match that then. The 'Upload Limit' field is displayed with floats. Example:
> transmission-remote -t all -i | grep -i 'upload limit' Upload Limit: 20.00 KiB/s
comment:4 Changed 13 years ago by charles
How is that a use case?
comment:5 Changed 13 years ago by charles
- Resolution set to invalid
- Status changed from reopened to closed
Note: See
TracTickets for help on using
tickets.
The bandwidth limits intentionally only accept integers, as any more precision would be beyond the scope of what anyone could need.