From: ZyX <kp-pav@yandex.ru>
To: Ray Andrews <rayandrews@eastlink.ca>,
"zsh-users@zsh.org" <zsh-users@zsh.org>
Subject: Re: utf-8
Date: Thu, 18 Dec 2014 21:22:35 +0300 [thread overview]
Message-ID: <1060081418926955@web2o.yandex.ru> (raw)
In-Reply-To: <54931986.6050507@eastlink.ca>
18.12.2014, 21:16, "Ray Andrews" <rayandrews@eastlink.ca>:
> On 12/18/2014 09:48 AM, Peter Stephenson wrote:
>> Yes, correct. Most syntax is pinned down --- either something is a
>> keyword or something like a decimal number from a fixed set, or it's
>> any old string. Identifiers are an exception. There's an option for
>> this. POSIX_IDENTIFIERS <K> <S> When this option is set, only the
>> ASCII characters a to z, A to Z, 0 to 9 and _ may be used in
>> identifiers (names of shell parameters and modules). When the option
>> is unset and multibyte character support is enabled (i.e. it is
>> compiled in and the option MULTIBYTE is set), then additionally any
>> alphanumeric characters in the local character set may be used in
>> identifiers. Note that scripts and functions written with this feature
>> are not portable, and also that both options must be set before the
>> script or function is parsed; setting them during execution is not
>> sufficient as the syntax variable=value has already been parsed as a
>> command rather than an assignment. If multibyte character support is
>> not compiled into the shell this option is ignored; all octets with
>> the top bit set may be used in identifiers. This is non-standard but
>> is the tradi‐ tional zsh behaviour. pws
>
> Ok thanks. Now if I can just figger out how to enter one of these
> unicodes in xfce terminal. You'd think their doc might say something
> about it.
Zsh has `insert-unicode-char` if you know the codepoint and `insert-composed-char` for a more human-friendly input of a limited set of characters.
next prev parent reply other threads:[~2014-12-18 18:24 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 18:05 utf-8 Ray Andrews
2014-12-17 20:31 ` utf-8 ZyX
2014-12-18 0:39 ` utf-8 Ray Andrews
2014-12-18 6:48 ` utf-8 Павлов Николай Александрович
2014-12-18 9:25 ` utf-8 Mikael Magnusson
2014-12-18 9:25 ` utf-8 Peter Stephenson
2014-12-18 17:36 ` utf-8 Ray Andrews
2014-12-18 17:48 ` utf-8 Peter Stephenson
2014-12-18 18:14 ` utf-8 Ray Andrews
2014-12-18 18:22 ` ZyX [this message]
2014-12-18 18:05 ` utf-8 ZyX
2014-12-18 18:41 ` utf-8 Ray Andrews
2014-12-18 18:52 ` utf-8 ZyX
2014-12-18 20:04 ` utf-8 Ray Andrews
2014-12-18 20:12 ` utf-8 Peter Stephenson
2014-12-18 20:52 ` utf-8 ZyX
2014-12-18 21:15 ` utf-8 Ray Andrews
2014-12-18 21:38 ` utf-8 ZyX
2014-12-18 23:55 ` utf-8 Ray Andrews
2014-12-19 2:04 ` utf-8 Bart Schaefer
2014-12-19 2:27 ` utf-8 Ray Andrews
2014-12-19 2:32 ` utf-8 Mikael Magnusson
2014-12-19 2:45 ` utf-8 Bart Schaefer
2014-12-19 6:34 ` utf-8 Ray Andrews
2014-12-19 7:02 ` utf-8 Bart Schaefer
2014-12-19 17:04 ` utf-8 Ray Andrews
2014-12-19 22:06 ` utf-8 ZyX
2014-12-19 7:29 ` utf-8 Павлов Николай Александрович
2014-12-19 3:50 ` utf-8 Lawrence Velázquez
2014-12-19 5:24 ` utf-8 Павлов Николай Александрович
2014-12-19 5:18 ` utf-8 Павлов Николай Александрович
[not found] <BC9BC140-F1A5-11D5-BA73-000393164560@mas.ecp.fr>
2001-12-18 16:51 ` UTF-8 Oliver Kiddle
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=1060081418926955@web2o.yandex.ru \
--to=kp-pav@yandex.ru \
--cc=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).