Re: [PATCH] Re: date timezone question

2004-05-10 Thread P
Paul Eggert wrote: [EMAIL PROTECTED] writes: OK I've attached a patch that addresses question 1 above. Note this is not for merging, just for disussion really. The user-interface change sounds good cool, that's all I wanted to determine with the patch. but the implementation isn't quite right. I

Re: Test failure tests/date/date-tests with current CVS

2004-05-10 Thread Thomas Schwinge
On Sun, May 09, 2004 at 08:44:36PM +0100, Ed Avis wrote: > I configured and built the current CVS HEAD of coreutils, but 'make > check' fails with > > make check-TESTS > make[3]: Entering directory > `/home/ed/cvs_working/coreutils/tests/date' > ./date-tests: line 777: ./utc-1.I: No such file or

Re: 'expr' and weird character classes

2004-05-10 Thread DervishD
Hi Andreas :) * Andreas Schwab <[EMAIL PROTECTED]> dixit: > > returns 1, correctly. That is, 'expr' understands character > > classes but it needs that double bracket :( > The syntax of a character class is [:CLASS:], _including_ the brackets. > Thus to build a regular expression that mat

Re: cp by blocks, with errors

2004-05-10 Thread Jim Meyering
[EMAIL PROTECTED] (Bryan Henderson) wrote: > I have two (related) enhancements to cp to propose. Code is attached. > Enhancement 1: reading by blocks > Enhancement 2: handling of unreadable portions of source file ... > I can do some of this with dd if I'm desperate, but dd is technically > for a

Re: Test failure tests/date/date-tests with current CVS

2004-05-10 Thread Paul Eggert
Jim Meyering <[EMAIL PROTECTED]> writes: > You can work around the problem by removing all of the > *-tests files from your checked-out directory: > > rm `find tests -name '*-tests'` > > I've removed those (generated) files from CVS, > so they shouldn't cause any more trouble. I was about to re

Re: Unable to build current CVS: coreutils.pot not built

2004-05-10 Thread Paul Eggert
Ed Avis <[EMAIL PROTECTED]> writes: > shouldn't the configure script have a 'checking for gettext' stage? When you check source out directly from CVS, you're assumed to be an expert, and to have the correct build tools even if they're not on the standard list of tools all users are assumed to hav

Re: Test failure tests/date/date-tests with current CVS

2004-05-10 Thread Jim Meyering
Paul Eggert <[EMAIL PROTECTED]> wrote: > Jim Meyering <[EMAIL PROTECTED]> writes: > >> You can work around the problem by removing all of the >> *-tests files from your checked-out directory: >> >> rm `find tests -name '*-tests'` >> >> I've removed those (generated) files from CVS, >> so they sho

Re: Unable to build current CVS: coreutils.pot not built

2004-05-10 Thread Paul Eggert
Ed Avis <[EMAIL PROTECTED]> writes: > when I check out of CVS, am I getting a > slightly different code base from what goes into the tarballs? Yes, you're getting a subset of the tarballs. ___ Bug-coreutils mailing list [EMAIL PROTECTED] http://mail.g

Re: Unable to build current CVS: coreutils.pot not built

2004-05-10 Thread Ed Avis
On Sun, 9 May 2004, Andreas Schwab wrote: I got a clean checkout, configured with './configure' and tried to build with 'make'. The build fails with make coreutils.pot-update >>>You need to install gettext. >>But shouldn't the configure script have a 'checking for gettext' >>st

Test failure tests/date/date-tests with current CVS

2004-05-10 Thread Ed Avis
I configured and built the current CVS HEAD of coreutils, but 'make check' fails with make check-TESTS make[3]: Entering directory `/home/ed/cvs_working/coreutils/tests/date' ./date-tests: line 777: ./utc-1.I: No such file or directory ./date-tests: line 795: ./utc-1a.I: No such file or directory

Re: Unable to build current CVS: coreutils.pot not built

2004-05-10 Thread Ed Avis
On Sun, 9 May 2004, Andreas Schwab wrote: >>I got a clean checkout, configured with './configure' and tried to >>build with 'make'. The build fails with >> >>make coreutils.pot-update >>make[4]: Entering directory `/home/ed/cvs_working/coreutils/po' >>: --default-domain=coreutils --directory=.. \

'expr' and weird character classes

2004-05-10 Thread DervishD
Hello all :) I'm using coreutils 5.2.1 and I've noticed a weird behaviour of 'expr'. I don't know if it's my fault, but a command like: $ expr "x" : "[:alpha:]" returns 0 instead of 1, but a command like: $ expr "x" : "[[:alpha:]]" returns 1, correctly. That is, 'expr'

cp by blocks, with errors

2004-05-10 Thread Bryan Henderson
I have two (related) enhancements to cp to propose. Code is attached. Enhancement 1: reading by blocks Reading and writing of files is typically fastest and most efficient when you read or write blocks of a certain size. cp seems to understand this in that it us

uniq -c chokes on international characters

2004-05-10 Thread blue0ne
To whom it may concern, After executing a uniq on a list of names, some of which contain accent characters, I noticed that the lines with acccent characters were not being consolidated into a non-repeating pattern. For instance, the following is sampling of the output of a command line which c

Re: Test failure tests/date/date-tests with current CVS

2004-05-10 Thread Jim Meyering
Ed Avis <[EMAIL PROTECTED]> wrote: > I configured and built the current CVS HEAD of coreutils, but 'make > check' fails with > > make check-TESTS > make[3]: Entering directory > `/home/ed/cvs_working/coreutils/tests/date' > ./date-tests: line 777: ./utc-1.I: No such file or directory > ./date-test

Re: uniq -c chokes on international characters

2004-05-10 Thread Jim Meyering
[EMAIL PROTECTED] wrote: > To whom it may concern, > After executing a uniq on a list of names, some of which contain > accent characters, I noticed that the lines with acccent characters were > not being consolidated into a non-repeating pattern. For instance, the > following is sampling of t

Re: 'expr' and weird character classes

2004-05-10 Thread Andreas Schwab
DervishD <[EMAIL PROTECTED]> writes: > Hello all :) > > I'm using coreutils 5.2.1 and I've noticed a weird behaviour of > 'expr'. I don't know if it's my fault, but a command like: > > $ expr "x" : "[:alpha:]" This matches "x" against the set of characters ":ahlp". > returns 0 in