From: Lewis Butler <lbutler@covisp.net>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Prompts with emoji issues
Date: Thu, 14 May 2020 03:50:52 -0600 [thread overview]
Message-ID: <2475C365-C62B-48DE-AC8A-3866E2DAEEEC@covisp.net> (raw)
In-Reply-To: <CAH+w=7ZPvTP_1x-kJFCBsLaN=hXwS6hZdVjMSi-_K=zSnAr=0Q@mail.gmail.com>
On 13 May 2020, at 21:54, Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Wed, May 13, 2020 at 2:26 PM Lewis Butler <lbutler@covisp.net> wrote:
> echo -n “%(👹%2G%}”
> Firstly, if that's a literal copy-and-paste, you've written percent open-paren rather than percent open-brace.
Typo.
> Assuming that's not the problem ... You mentioned having a similar occurrence but with a different emoji on your Mac. Different emoji characters might need different numbers of "glitch", e.g., on the Mac the emoji might occupy only one position, so you need only %1G (or just %G). Also on different terminals the same emoji might occupy different numbers of positions, though that's less likely.
Same terminal emulator, same behavior, different emojis. I have setups for 👹, , and 🥧 (though I use the pi so rarely I am not sure it has the same problem. Currently, I always lose the space after the #
Whit this
#v+
function toon {
echo -n “%(👹%2G%}”
}
PROMPT=$'$(toon) %{$fg_bold[red]%}%n@%m %{$fg_bold[green]%}# '
👹 root@mail #cd /var/log
👹 root@mail #pwd
/var/log
#v-
If I remove the space after the $(toon) in PROMPT I get
👹root@mail #pwd
Still no final space.
> There's also the possibility of interference by something you haven't mentioned, such as an RPROMPT setting.
That is the entirety of the file, barring comments.
> You haven't told us the version(s) of zsh under which you encountered this -- it's possible there was something related that has since been fixed.
oh-my-Zsh updates frequently so if I do not currently have the latest version I am no more than a day or two out of date. Zsh versions are "5.7.1 (x86_64-apple-darwin19.0)" and "zsh 5.8 (i386-portbld-freebsd12.1)", but this problem has been consistently inconsistent since last fall.
> In any case I can't reproduce a problem with only the PROMPT from your first message.
That’s what I was afraid of. I’ll try playing around with a new user account on the off chance there is some odd setting in my Terminal.app preferences.
--
ɹןʇnqן
<mailto:lbutler@covisp.net>
tel:+1.303.219.0564
next prev parent reply other threads:[~2020-05-14 9:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 5:08 Lewis Butler
2020-05-13 6:52 ` Bart Schaefer
2020-05-13 16:47 ` Roman Perepelitsa
2020-05-13 21:14 ` Lewis Butler
2020-05-13 21:26 ` Lewis Butler
2020-05-14 3:54 ` Bart Schaefer
2020-05-14 9:50 ` Lewis Butler [this message]
2020-05-14 12:13 ` Lewis Butler
2020-05-14 17:55 ` Bart Schaefer
2020-05-14 18:18 ` Lewis Butler
2020-05-17 19:50 ` Lewis Butler
2020-05-17 20:39 ` Bart Schaefer
2020-05-18 3:41 ` Bart Schaefer
2020-05-18 12:23 ` Lewis Butler
2020-05-19 0:26 ` Bart Schaefer
2020-05-19 13:21 ` Lewis Butler
2020-05-19 13:54 ` Roman Perepelitsa
2020-05-19 22:05 ` Lewis Butler
2020-05-19 23:20 ` Daniel Shahaf
2020-05-20 5:16 ` Roman Perepelitsa
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=2475C365-C62B-48DE-AC8A-3866E2DAEEEC@covisp.net \
--to=lbutler@covisp.net \
--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).