expr say "non integer argument"

2010-02-18 Thread jidanni
$ expr 3.1 + 3 expr: non-numeric argument <---say "non integer argument" $ expr 3.1 + 3b expr: non-numeric argument

Re: expr say "non integer argument"

2010-02-18 Thread Chris F.A. Johnson
On Thu, 18 Feb 2010, jida...@jidanni.org wrote: > $ expr 3.1 + 3 > expr: non-numeric argument <---say "non integer argument" > $ expr 3.1 + 3b > expr: non-numeric argument The expr command's arithmetic only works with integers. 3.1 is not an integer, nor is 3b. To do calculations with

Re: expr say "non integer argument"

2010-02-18 Thread jidanni
> "CFAJ" == Chris F A Johnson writes: CFAJ> On Thu, 18 Feb 2010, jida...@jidanni.org wrote: >> $ expr 3.1 + 3 >> expr: non-numeric argument <---say "non integer argument" >> $ expr 3.1 + 3b >> expr: non-numeric argument CFAJ>The expr command's arithmetic only works with integers. Yes CFA

Re: expr say "non integer argument"

2010-02-18 Thread Chris F.A. Johnson
On Thu, 18 Feb 2010, jida...@jidanni.org wrote: > > "CFAJ" == Chris F A Johnson writes: > CFAJ> On Thu, 18 Feb 2010, jida...@jidanni.org wrote: > > >> $ expr 3.1 + 3 > >> expr: non-numeric argument <---say "non integer argument" > >> $ expr 3.1 + 3b > >> expr: non-numeric argument > > CFAJ>

Re: expr say "non integer argument"

2010-02-18 Thread Eric Blake
According to Chris F.A. Johnson on 2/18/2010 6:20 AM: > On Thu, 18 Feb 2010, jida...@jidanni.org wrote: > >> $ expr 3.1 + 3 >> expr: non-numeric argument <---say "non integer argument" >> $ expr 3.1 + 3b >> expr: non-numeric argument > >The expr command's arithmetic only works with integers.

Re: expr say "non integer argument"

2010-02-18 Thread jidanni
EB> jidanni, it would be a two-line patch to expr.c. Would you care to write EB> such a patch, rather than just complaining? It would be much more efficient for me to just play the role of the bug reporter here trust me. Thanks.

Re: expr say "non integer argument"

2010-02-18 Thread Chris F.A. Johnson
On Thu, 18 Feb 2010, Eric Blake wrote: > According to Chris F.A. Johnson on 2/18/2010 6:20 AM: > > On Thu, 18 Feb 2010, jida...@jidanni.org wrote: > > > >> $ expr 3.1 + 3 > >> expr: non-numeric argument <---say "non integer argument" > >> $ expr 3.1 + 3b > >> expr: non-numeric argument > > > >

Re: expr say "non integer argument"

2010-02-18 Thread jidanni
CFAJ> That'll teach me to post early in the morning! The problem is that you live in the incorrect timezone :-|

Re: expr say "non integer argument"

2010-02-18 Thread Eric Blake
According to jida...@jidanni.org on 2/18/2010 6:54 AM: > EB> jidanni, it would be a two-line patch to expr.c. Would you care to write > EB> such a patch, rather than just complaining? > > It would be much more efficient for me to just play the role of the bug > reporter here trust me. Thanks.

Re: expr say "non integer argument"

2010-02-18 Thread jidanni
$ diff --git diff: unrecognized option '--git'<--see my next email coming soon. $ dlocate src/expr.c|wc 0 0 0 Actually at one point I was much more involved. http://article.gmane.org/gmane.comp.version-control.git/103400 However today its bash: git: command not found for me, as

diff "--git"

2010-02-18 Thread jidanni
$ diff --git diff: unrecognized option '--git' I think diff should say at this point "real diff, at least up to year 2010, does not have a --git option, you are probably getting that idea from git output" or something. Or ask those git pros for a patch to give diff a --git option, or tell them th

Re: diff "--git"

2010-02-18 Thread Alfred M. Szmidt
$ diff --git diff: unrecognized option '--git' I think diff should say at this point "real diff, at least up to year 2010, does not have a --git option, you are probably getting that idea from git output" or something. That is what it says, though not in so many words. Having an o

Re: diff "--git"

2010-02-18 Thread jidanni
AMS> That is what it says, though not in so many words. Having an option AMS> for each VS would really be a headache (SCCS, RCS, CVS, hg, darcs, AMS> bzr, tla, git, ...). Well all I know is we then harangue the system administrator for not installing the latest diff that the other guys are alread

RE: expr say "non integer argument"

2010-02-18 Thread Voelker, Bernhard
Eric Blake wrote: > -error (EXPR_INVALID, 0, _("non-numeric argument")); > +error (EXPR_INVALID, 0, _("non-integer argument")); ... > -error (EXPR_INVALID, 0, _("non-numeric argument")); > +error (EXPR_INVALID, 0, _("non-integer argument")); Maybe a

Re: Final point in new option of join

2010-02-18 Thread Pádraig Brady
On 16/02/10 00:09, Pádraig Brady wrote: +sc_option_desc_uppercase: + @$(MAKE) -C src $@ + @$(MAKE) -C man $@ I've pushed with the above changed to: @$(MAKE) -s -C src all_programs @$(MAKE) -s -C man $@ The -s is defined by POSIX and is available on linux/BSD/solaris at least, and makes the

[bug #26512] ls: it's no longer possible to change the default (NORMAL) text color

2010-02-18 Thread Pádraig Brady
Update of bug #26512 (project coreutils): Status:None => Fixed Assigned to:None => pixelbeat ___ Follow-up Comment #1: Fixed with commi

Re: expr say "non integer argument"

2010-02-18 Thread Eric Blake
According to Voelker, Bernhard on 2/18/2010 8:31 AM: >> -error (EXPR_INVALID, 0, _("non-numeric argument")); >> +error (EXPR_INVALID, 0, _("non-integer argument")); > > Maybe a dumb question: > Why's the error message hardcoded? It isn't. > Isn't there localization for th