Date: Mon, 12 Oct 1998 14:59:11 +0100 From: Brian Somers <brian@Awfulhak.org> To: Jim Martin <jjmartin@eos.ncsu.edu> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: simple unix question ? Message-ID: <199810121359.OAA11051@woof.lan.awfulhak.org> In-Reply-To: Your message of "Sat, 10 Oct 1998 22:58:49 EDT." <36201EE9.621F@eos.ncsu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
> Hi, if I'm telnet'ing into a server and if I issue the command
> echo '12\t34' I will see '12\t34' on some (freebsd) machines and
> '12 34' on others machines (AIX). And on other machines
> we see the \t come back as the ascii tab (0x09). I need to learn how to
> control configure the telnet session to be able to translate
> the tab (the \t) or to not translate.
>
> The stty -oxtab I thought was to allow tabs to go untranslated.
> If I issue 'stty oxtab' to enable translation of tabs, I don't see
> freebsd substitute spaces for the tab. Likewise I can't change
> AIX's behavior with the stty command.
>
> what else is involved with being able to turn on and off the
> tab translation over a telnet session?
Using printf(1) will give more consistent results than echo; echo's
different on SYSV. BSDs echo will ``echo'' what you type, so \t == \t.
oxtabs will translate your tab character to the necessary number of
spaces at the tty driver level so that the target terminal device has
no control over tab stop widths - it only ever gets to see a series
of spaces instead. I believe -tabs gives the same effect in SYSV.
> thanks,
> jim
--
Brian <brian@Awfulhak.org>, <brian@FreeBSD.org>, <brian@OpenBSD.org>
<http://www.Awfulhak.org>;
Don't _EVER_ lose your sense of humour....
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199810121359.OAA11051>