Thanks for any help.
/ivo welch i...@next.agsm.ucla.edu
/ivo welch i...@next.agsm.ucla.edu
So get a real shell:
$ echo ' ' | od -c
0000000 \t \n
0000002
$
On a NeXT improved csh (and presumably on some other shells), the following
works:
sort -t\^V^I
that is, the tab must be quoted twice: once with the backslash, and then with
the ^V (control-V) to not substitute spaces.
Once you know this, it is no big deal, of course.
/ivo welch i...@next.agsm.ucla.edu
...
>that is, the tab must be quoted twice: once with the backslash, and then with
>the ^V (control-V) to not substitute spaces.
"improved"? Thanks, NeXT; thanks a lot. The vanilla C shell doesn't
have this particular stupidity. Is this a "tcsh"ism? If so, whoever
maintains "tcsh" should seriously think about getting rid of it, 'cause
it's a crock. "csh" is broken enough already without breaking it
further....
Improved: it is command-line and history editing via Emacs commands that
probably screws up some of this. I am VERY GLAD that the NeXT csh has this
feature. It makes life much more pleasant. In fact, I wouldn't even consider a
shell without this feature.
/ivo welch i...@next.agsm.ucla.edu
There is absolutely no reason why the fact that a shell has editing
facilities should cause it to substitute spaces for tabs. If the NeXT
csh does this then it's just plain wrong.
-- Richard
--
Richard Tobin, JANET: R.T...@uk.ac.ed
AI Applications Institute, ARPA: R.Tobin%uk.a...@nsfnet-relay.ac.uk
Edinburgh University. UUCP: ...!ukc!ed.ac.uk!R.Tobin
And *I* wouldn't consider a shell that turned tabs into spaces, even
though I like that kind of command-line and history editing. "ksh" has
command-line and history editing via EMACS commands, and as I remember
it didn't have any such problems; the Bourne-again shell version here
also has command-line and history editing via EMACS commands, and *it*
doesn't have that problem.
--
"Down in the dumps? I TOLD you you'd | Chris Robertson
need two sets..." | ch...@mcc.oz
Some "improvement" that would be, changing an 8 to a 9.
You bet it will! The vanilla S5 Bourne shell doesn't interpret escape
sequences such as that except in the "echo" command (and I don't think
it even interprets one such as yours; try '\011' instead, 8 not being a
valid octal digit), nor does any other Bourne shell version with which
I'm familiar. The C shells with which I'm familiar don't do so, either.
What sort of shell are you using? Did Pyramid "improve" the shell by
-t' '
^^^^^^ literal tab here entered with the TAB key
Bob McGowan (standard disclaimer, these are my own ...)
Product Support, Wyse Technology, San Jose, CA
..!uunet!wyse!bob
b...@wyse.com
Okay, csh is seriously f*cked. However:
csh% echo ' ' | od -c
0000000 \t \n
0000002
tcsh% echo '^ ' | od -c (NB: ^V needed before TAB as TAB has special
meaning in tcsh)
0000000 \t \n
0000002
So *csh may not be a 'real shell' but this I'm afraid it does do (Sun-4,
SunOs 4.0.3).
---------------------------------------------------------------------------
Sean Legassick, cu...@uk.ac.warwick.cu "Improbability factor of one
Computing Services as...@uk.ac.warwick.cu to one. We have normality.
University of Warwick Anything you still can't
(the walking C obfuscator!) handle is your own problem."
Sorry, brain out to lunch when I wrote this. Not only did I type 8 instead
of 11, but I just checked my test file and it has a typo in it. This
definitely doesn't work. I must admit, I *was* a bit surprised when it
seemed to. So just ignore me while I crawl back into that handy hole in
the wall... :-(