From: Wolfgang Hukriede <whukriede@googlemail.com>
To: zsh-workers@sunsite.dk
Subject: Re: Echoing of 8-bit-characters broken after 4.3.2?
Date: Sat, 28 Feb 2009 23:00:44 +0100 [thread overview]
Message-ID: <2493fbfb0902281400r5d56ef91r74d55433eddf51be@mail.gmail.com> (raw)
Andrey wrote:
> Because this is established standard to define your character set
> properties. Without it applications should assume C (or POSIX) locale
> that basically corresponds to standard ASCII.
Should the character set properties not be set by LC_CTYPE? As far as
I can tell LANG sets more than that? Do I understand correctly that
LANG is zsh-specific? (On my box, man 3 setlocale does not have it.)
> So I would be surprised if
> zsh were the only program that had issues with non-ASCII characters.
At least emacs passes them through without ado. There's only one other
program that I had problems with in that respect. (That's unicode
only.) Looks like more will come...
> FreeBSD could provide some other means to define local though.
Not that I know of.
> Because blindly emitting arbitrary character sequence to terminal may
> have completely undefined effects and screw up display to the point that
> you need hard reset (town legend also is that you can cause you terminal
> to echo back any sequence like "rm -rf" as input back to shell ...)
Urban legends aside, this may be. Otoh... I've been using zsh since at
least 10 years almost exclusively and quite intensely and have used
8-bit-characters all the time (all on xterms), but any display
distortion never happened to me. This is probably due to the fact that
filenames are mostly under ones own control. I suffered display
distortion from reading emails though, but the shell could not have
done anything about that. Correctness of vt100-control-sequences
cannot be monitored either.
Therefore I think passing-through of eight bit characters should be
configurable. But I still do not understand how am I supposed to do
that (without triggering side effects). Why is PRINT_EIGHT_BIT
constricted to affect tab-completion only?
next reply other threads:[~2009-02-28 22:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 22:00 Wolfgang Hukriede [this message]
2009-03-01 0:12 ` Phil Pennock
-- strict thread matches above, loose matches on Subject: below --
2009-02-28 20:31 Wolfgang Hukriede
2009-02-28 20:49 ` Andrey Borzenkov
2009-02-28 23:01 ` Bart Schaefer
2009-02-28 19:52 Wolfgang Hukriede
2009-02-28 20:40 ` Andrey Borzenkov
2009-02-28 8:35 Wolfgang Hukriede
2009-02-28 17:53 ` Bart Schaefer
2009-02-28 19:07 ` Andrey Borzenkov
2009-02-28 19:19 ` Bart Schaefer
2009-02-28 19:29 ` Andrey Borzenkov
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=2493fbfb0902281400r5d56ef91r74d55433eddf51be@mail.gmail.com \
--to=whukriede@googlemail.com \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).