Zsh Mailing List Archive
Messages sorted by: Reverse Date, Date, Thread, Author

Re: utf-8

18.12.2014, 21:16, "Ray Andrews" <rayandrews@xxxxxxxxxxx>:
> 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.

Messages sorted by: Reverse Date, Date, Thread, Author