Re: How is 8-bit character support enabled for the TTY driver
Marcin Dalecki (dalecki@dacotec.net)
Wed, 08 Dec 1999 14:13:11 +0100
Khimenko Victor wrote:
>
> On Wed, 8 Dec 1999, Martin Dalecki wrote:
>
> > "Jeff V. Merkey" wrote:
> > >
> > > "Richard B. Johnson" wrote:
> > > >
> > > > On Wed, 8 Dec 1999, Khimenko Victor wrote:
> > > >
> > > > > Whomever owns the TTY drivers, how do you turn the damn thing on to
> > > > > allow you to display characters above 127?
> > > > [SNIPPED]
> > > >
> > > > #include <termios.h>
> > > > #include <ioctls.h>
> > > >
> > > > struct termios term;
> > > > ioctl(1, TCGETS, &term);
> > > > term.c_cflag |= CS8;
> > > > ioctl(1, TCSETS, &term);
> > > >
> > > > The terminal is now 8-bit clean.
> > > >
> > > > Cheers,
> > > > Dick Johnson
> > >
> > > Sorry Dick, but this doesn't work with bash. It still outputs
> > > characters below 127. I tried thi already.
> >
> > Bash is broken with respect to this. You could however use as
> > well pdksh-5.2.14 instead, where I have fixed those issues.
> > However you should prefferable get the one distributed under the
> > guaidiance of the www.pld.opg.pl project, since there is a minor
> > memmory allocation issue (which will never hurt you in interactive mode)
> > in it...
> >
> If bash is broken why I can not see it ? I'm using bash 2.03 and all
> russian filenames and such works just fine ...
Uh.. oh... I did only look at bash-1.14.
> P.S. Of course I said (via .inputrc) that I need support for 8bit characters
> for both input and output (it's in bash's info under "Command Line Editing",
> "Readline Init File", "Readline Init File Syntax": input-meta,
> convert-meta, output-meta, etc).
Yeah GNU hell of configuration...
--Marcin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/