Re: ... --limit-rate nn%

--limit-rate nn%. Any reason not to do so? The current parser, and in particular, the actual code that handles, K, M, etc, is used by other options, for which percentages are not appropriate. Plus, whereas those options have been taking doubles, you'll now need some sort of struct to hold

Re: ... --limit-rate nn%

- that would reduce the amount of code necessary to implement --limit-rate nn%. Any reason not to do so? The current parser, and in particular, the actual code that handles, K, M, etc, is used by other options, for which percentages are not appropriate. Plus, whereas those options have been taking

Re: ... --limit-rate nn%

thinking I can hack the parser that now handles the K, M, etc. suffixes so it works as it did before but also sees a '%' suffix as valid- that would reduce the amount of code necessary to implement --limit-rate nn%. Any reason not to do so? -- Best Regards. Please keep in touch.