From: Matthew Burgess <matthew@linuxfromscratch.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: dash@vger.kernel.org
Subject: Re: Allow dash to build with i18n version of Coreutils
Date: Tue, 1 Sep 2009 14:27:04 -0600 [thread overview]
Message-ID: <c0670a2697cad20e7e616e7dba2ed2a0@quantum.linuxfromscratch.org> (raw)
In-Reply-To: <20090901031557.GA17361@gondor.apana.org.au>
On Tue, 1 Sep 2009 13:15:57 +1000, Herbert Xu <herbert@gondor.apana.org.au> wrote:
> On Mon, Aug 31, 2009 at 08:19:24AM -0600, Matthew Burgess wrote:
>
> Oh I see what's going on. In fact it's sed that's not working for
> you, not sort. Let me find a way around that.
Ah, well spotted. The following is enough to get the correct output from sed(1):
sed 's/\t-[a-z]*//' $temp2
This is with sed-4.2.1 compiled against Glibc-2.10.1.
Running through 'nl -v 0', I end up with:
0 . dotcmd
1 : truecmd
2 [ testcmd
3 alias aliascmd
4 bg bgcmd
5 break breakcmd
6 cd cdcmd
7 chdir cdcmd
8 command commandcmd
9 continue breakcmd
10 echo echocmd
11 eval evalcmd
12 exec execcmd
13 exit exitcmd
14 export exportcmd
15 false falsecmd
16 fg fgcmd
17 getopts getoptscmd
18 hash hashcmd
19 jobs jobscmd
20 kill killcmd
21 local localcmd
22 printf printfcmd
23 pwd pwdcmd
24 read readcmd
25 readonly exportcmd
26 return returncmd
27 set setcmd
28 shift shiftcmd
29 test testcmd
30 times timescmd
31 trap trapcmd
32 true truecmd
33 type typecmd
34 ulimit ulimitcmd
35 umask umaskcmd
36 unalias unaliascmd
37 unset unsetcmd
38 wait waitcmd
That still doesn't help with the sort(1) output though (from coreutils-7.5), which
still doesn't appear to be honouring LC_COLLATE! I suspect a bug in our i18n patch
for Coreutils, which I'll try to take a look at over the next few days.
Thanks,
Matt.
prev parent reply other threads:[~2009-09-01 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-15 18:07 Allow dash to build with i18n version of Coreutils Matthew Burgess
2009-08-31 10:27 ` Herbert Xu
2009-08-31 14:19 ` Matthew Burgess
2009-09-01 3:15 ` Herbert Xu
2009-09-01 20:27 ` Matthew Burgess [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c0670a2697cad20e7e616e7dba2ed2a0@quantum.linuxfromscratch.org \
--to=matthew@linuxfromscratch.org \
--cc=dash@vger.kernel.org \
--cc=herbert@gondor.apana.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox