[Tcsh] "Readable" Unicode in setenv

Michal Szymanski msz at astrouw.edu.pl
Thu Dec 9 12:02:34 UTC 2021


Actually, both the mentioned FreeBSD sh(1) man page and Linux (Ubuntu
20.04) bash(1) man page mention \U (uppercase U) for the longer (one
to eight hex digits) unicode character coding. Indeed, under bash,

$ echo $'\u1234FE'   outputs ሴFE  (only four digits interpreted as Unicode)
while
$ echo $'\U1234FE'   outputs garbage ???? (char not supported in my terminal
                     font) 

regards,
Michal

On Thu, Dec 09, 2021 at 01:47:52PM +0200, Kimmo Suominen wrote:
> Hi all,
> 
> I've committed code that implements the dollar-single-quote feature.
> https://github.com/tcsh-org/tcsh/commit/bda86ab754b56d5a8983b554cb1dfffad2f3b43d
> 
> What should we do about these differences:
> 
> We do:
> - \uNNNNNN for unicode code points (six hex digits)
> - \xNN and \x{NNNN} for "ASCII" char in hex (how is NNNN ASCII?)
> 
> FreeBSD sh(1) documents these:
> - \uNNNN and \uNNNNNNNN for unicode code points (four and eight hex digits)
> - \xNN for a byte in hex, where NN can be 1 or more hex digits and
> only last two are used
> 
> We are also missing \cC for a control character. I would have added
> this but ran out of steam for now.
> 
> Cheers,
> + Kimmo
> -- 
> Tcsh mailing list
> Tcsh at astron.com
> https://mailman.astron.com/mailman/listinfo/tcsh

-- 
  Michal Szymanski (msz at astrouw dot edu dot pl)
  Warsaw University Observatory, Warszawa, POLAND


More information about the Tcsh mailing list