From: Bart Schaefer <schaefer@brasslantern.com>
To: Lewis Butler <lbutler@covisp.net>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Prompts with emoji issues
Date: Thu, 14 May 2020 10:55:12 -0700 [thread overview]
Message-ID: <CAH+w=7bcTxHGvgznD21squGi4U5wut_NwtaG5MTT2w93Y3dXww@mail.gmail.com> (raw)
In-Reply-To: <2475C365-C62B-48DE-AC8A-3866E2DAEEEC@covisp.net>
[-- Attachment #1: Type: text/plain, Size: 1681 bytes --]
On Thu, May 14, 2020 at 2:52 AM Lewis Butler <lbutler@covisp.net> wrote:
>
> > Firstly, if that's a literal copy-and-paste, you've written percent
> open-paren rather than percent open-brace.
>
> Typo.
>
Please copy-paste rather than type things in. Aside from that obvious
typo, your double-quotes are coming through as unicode curly-quotes, and
sometimes your single-quotes are unicode apostrophes. This makes it
painful to use your examples as test cases.
> 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.
>
Yes, but that's obviously not the ONLY file, since you are loading OMZ, and
goodness only knows what is coming in from there.
> 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.
This is not the list on which to be debugging OMZ problems. If you can't
reproduce the issue when using ...
zsh -f
% autoload colors
% colors
% setopt promptsubst
% function toon {
> echo -n "%{👹%2G%}"
> }
% PROMPT=$'$(toon) %{$fg_bold[red]%}%n@%m %{$fg_bold[green]%}# '
... then you should pursue this elsewhere, as an OMZ problem.
> 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.
>
Those are at least recent enough that it should be OK.
> I’ll try playing around with a new user account on the off chance there is
> some odd setting in my Terminal.app preferences.
>
A good next step in any case.
next prev parent reply other threads:[~2020-05-14 17:56 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
2020-05-14 12:13 ` Lewis Butler
2020-05-14 17:55 ` Bart Schaefer [this message]
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='CAH+w=7bcTxHGvgznD21squGi4U5wut_NwtaG5MTT2w93Y3dXww@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=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).