zsh-users
 help / color / mirror / code / Atom feed
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: Wed, 13 May 2020 20:54:04 -0700	[thread overview]
Message-ID: <CAH+w=7ZPvTP_1x-kJFCBsLaN=hXwS6hZdVjMSi-_K=zSnAr=0Q@mail.gmail.com> (raw)
In-Reply-To: <E2F20022-1E29-4571-8E6D-50CFC5A8870C@covisp.net>

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

On Wed, May 13, 2020 at 2:26 PM Lewis Butler <lbutler@covisp.net> wrote:

>
> Found what I had done, which still had occasional issues with eating the
> space (or less often, adding characters to the start of the line)
>
> function toon {
>   echo -n “%(👹%2G%}”
> }
>
> It’s not all the time and it is an annoyance rather than a showstopper.
>

Firstly, if that's a literal copy-and-paste, you've written percent
open-paren rather than percent open-brace.

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.

There's also the possibility of interference by something you haven't
mentioned, such as an RPROMPT setting.  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.

In any case I can't reproduce a problem with only the PROMPT from your
first message.

  reply	other threads:[~2020-05-14  3:55 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 [this message]
2020-05-14  9:50         ` Lewis Butler
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='CAH+w=7ZPvTP_1x-kJFCBsLaN=hXwS6hZdVjMSi-_K=zSnAr=0Q@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).