zsh-workers
 help / color / mirror / code / Atom feed
From: Максим <herobrine135111@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: Bug when $USERNAME is cyryllic
Date: Sun, 1 Oct 2023 21:54:46 +0300	[thread overview]
Message-ID: <CAHJ=x4ajbNr2ufWi3BX-kHfA1pijEJ=L0ZVbQznHMk8xNE==Lg@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZQc41R2QiNDKiT4gf-WFqOgVEMU8Z3uMx=vrpBt9f0uA@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]

Tested both patches:

    env -i LANG=C =zsh-5.9.0.1-dev -fc 'cd; echo "$USERNAME | ${(%):-%n} |
$LOGNAME"'

Now results in:

    Студент | Студент | Ѓ�ту�дент

*USERNAME* and *%n* works, but *LOGNAME* is broken now (both in C and
C.UTF-8 locales)


Btw, *zcompile* now works just fine

вс, 1 окт. 2023 г., 21:05 Bart Schaefer <schaefer@brasslantern.com>:

> On Sat, Sep 30, 2023 at 10:05 PM Максим Щербаков
> <herobrine135111@gmail.com> wrote:
> >
> > As we can see, $LOGNAME is fine, but $USERNAME and %n are bad.
>
> Patch appended.
>
> As mentioned in another thread, this presumes that it's harmless to
> metafy something that's already metafied.  If that's not true then the
> patch will fix USERNAME but break LOGNAME.
>
> Aside:  If USE_GETPWUID is not defined and DISABLE_DYNAMIC_NSS is also
> defined, then both USERNAME and LOGNAME will be empty.
>
> > zcompile: can't write zwc file: /home/Студент/.zc/.zcompdump-5.9.zwc
>
> The opposite problem.
>
>

[-- Attachment #2: Type: text/html, Size: 1789 bytes --]

  reply	other threads:[~2023-10-01 18:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-01  5:04 Максим Щербаков
2023-10-01  7:04 ` Ellenor Bjornsdottir
2023-10-01  7:17   ` Максим Щербаков
2023-10-01 18:05 ` Bart Schaefer
2023-10-01 18:54   ` Максим [this message]
2023-10-01 20:35     ` Bart Schaefer
2023-10-02  4:50       ` Максим
2023-10-02 10:28       ` Peter Stephenson

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='CAHJ=x4ajbNr2ufWi3BX-kHfA1pijEJ=L0ZVbQznHMk8xNE==Lg@mail.gmail.com' \
    --to=herobrine135111@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@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).