From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 22884 invoked by alias); 18 Dec 2014 18:24:31 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 19567 Received: (qmail 16900 invoked from network); 18 Dec 2014 18:24:30 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE, T_FSL_HELO_BARE_IP_2 autolearn=ham version=3.3.2 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1418926956; bh=Ho4NBznoWBdF5R3PXwPDITwxNIYeMH0YuM4JfPmuyVU=; h=From:To:In-Reply-To:References:Subject:Date; b=eqahXcvnzX6XOh4UHHEq7g2aN4qMoY3AD99JM8UNl/DQFffVa6SkFSFr6oqGHP7Xa Rn0/c+t/A9VS7BEJEPjNIlMt4j6NpoMZI6Fh+QquN0mjCGBvebQR/LsliGDPi0LQMI KsG/HMAgEwIWmi097e2E1jjGXXdBzREbd3+D+2hY= From: ZyX To: Ray Andrews , "zsh-users@zsh.org" In-Reply-To: <54931986.6050507@eastlink.ca> References: <5491C5E7.1070207@eastlink.ca> <20141218092544.01495a40@pwslap01u.europe.root.pri> <549310A1.4080602@eastlink.ca> <20141218174855.3aaa00dd@pwslap01u.europe.root.pri> <54931986.6050507@eastlink.ca> Subject: Re: utf-8 MIME-Version: 1.0 Message-Id: <1060081418926955@web2o.yandex.ru> X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 18 Dec 2014 21:22:35 +0300 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=utf-8 18.12.2014, 21:16, "Ray Andrews" : > 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 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.