retitle 351695 nvi: display of certain 8bit-char/locale combinations ambiguous
thankyou
Hi,
(from iso8859-1, -2, -7, -9, -15, -16)
Oct Dec Hex Char Description
240 160 A0 NO-BREAK SPACE
> Bug#351695: Simple Bash command gives unexpected error message.
> Bug reassigned from package `bash' to `nvi'.
Umm, the difference shows up just fine in nvi:
$ perl -e 'print "xxx", chr(160), "xxx\n";' > rrr
$ nvi rrr
[displays]
the first
thing about such things, though.
> > Date: Wed, 8 Feb 2006 14:41:13 -0500
> > To: Jim Hertzler <[EMAIL PROTECTED]>
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: Re: Bug#351695: Simple Bash command gives unexpected error
> > message.
> > From:
< Cc: [EMAIL PROTECTED]
< Subject: Re: Bug#351695: Simple Bash command gives unexpected error message.
< From: Justin Pryzby <[EMAIL PROTECTED]>
<
< On Wed, Feb 08, 2006 at 02:39:21PM -0500, Jim Hertzler wrote:
< > Justin,
< >
< > It would be nice if it were eas
On Wed, Feb 08, 2006 at 03:39:24PM -0500, Jim Hertzler wrote:
> Justin,
>
> dselect:Update:Select:Install:
> vim - Vi IMproved - enhanced vi editor
> vim-common - Vi IMproved - Common files
> exuberent-ct - build tag file indexes of source code definitions
> vim-
On Wed, Feb 08, 2006 at 02:39:21PM -0500, Jim Hertzler wrote:
> Justin,
>
> It would be nice if it were easier to detect the difference between
> character 32 and character 160.
>
> I suspected my bad command was tained with a special character.
> I expected that bash would hide the differe
On Wed, Feb 08, 2006 at 10:29:21AM -0500, Jim Hertzler wrote:
> (I am sending this again because you may not have gotten it the first time.)
> Justin,
>
> The ninth character of good and bad lines differs.
> The ninth character of the good line is char#32=space.
> The ninth character of the bad li
(I am sending this again because you may not have gotten it the first time.)
Justin,
The ninth character of good and bad lines differs.
The ninth character of the good line is char#32=space.
The ninth character of the bad lines is char#160=32+128.
My sloppy keyboarding must have produced the speci
Justin,
The ninth character of good and bad lines differs.
The ninth character of the good line is char#32=space.
The ninth character of the bad lines is char#160=32+128.
My sloppy keyboarding must have produced the special character.
Too bad "vi" does not reveal the difference.
Here is the "c" p
Start:What I just Did. (In responce to your email.)
Debian:XShells:XTerm
cd Mail
sh do.sh
End:What I just Did.
..
On Mon, Feb 06, 2006 at 02:46:07PM -0500, Jim Hertzler wrote:
> Package: bash
> Version: 2.05b.0(1)-release
>
> Output of "sh --version">/tmp/tmp:
> GNU bash, version 2.05b.0(1)-release (i386-pc-linux-gnu)
> Copyright (C) 2002 Free Software Foundation, Inc.
>
> Output of "cp -bvpi tmp jay_060202m
Package: bash
Version: 2.05b.0(1)-release
Output of "sh --version">/tmp/tmp:
GNU bash, version 2.05b.0(1)-release (i386-pc-linux-gnu)
Copyright (C) 2002 Free Software Foundation, Inc.
Output of "cp -bvpi tmp jay_060202m.to 2>/tmp/tmp":
cp: invalid option --
Try `cp --help' for more information.
12 matches
Mail list logo
