FWIW, I'm all for this change! I constantly get bitten by not being
able to use the upper case prefixes I'm used to using almost everywhere.
Also, since the prefixes originally stem from the SI standard units,
where for example a lower case 'm' means 'milli' while an upper case 'M'
is used for
Simple patch to allow uppercase size modifiers (K, M, and G).
I know this is not the most important thing in the world, but this
annoys me so I'm going to give it one last shot:
can somebody please give me one reason why this should not go in?
Look, when you ask various tools to display
Well, it's not POSIX, but from what I can see nor are 'm' or 'w'.
I think if we do this we should do it consistently, so accept 'B' and
'W' and 'X' as well.
Otherwise I can't see this doing any harm. Anyone else?
On Sat, Oct 08, 2011 at 03:13:14PM +0200, Thomas Pfaff wrote:
Simple patch to
Simple patch to allow uppercase size modifiers (K, M, and G). Is there
a reason why not to? Plus, as a bonus you're less likely to mess up if
you've been naughty and used dd on Linux.
Index: args.c
===
RCS file:
On 10/02/11 14:25, Thomas Pfaff wrote:
Simple patch to allow uppercase size modifiers (K, M, and G). Is there
a reason why not to? Plus, as a bonus you're less likely to mess up if
you've been naughty and used dd on Linux.
Index: args.c
On Sun, 02 Oct 2011 14:38:42-0400
STeve Andre' and...@msu.edu wrote:
On 10/02/11 14:25, Thomas Pfaff wrote:
Simple patch to allow uppercase size modifiers (K, M, and G). Is there
a reason why not to? Plus, as a bonus you're less likely to mess up if
you've been naughty and used dd on
