zsh-users
 help / color / mirror / code / Atom feed
From: Lewis Butler <lbutler@covisp.net>
To: zsh-users@zsh.org
Subject: Re: Prompts with emoji issues
Date: Sun, 17 May 2020 13:50:26 -0600	[thread overview]
Message-ID: <062FFA20-B1CE-40DC-9B9A-F57315542A1F@covisp.net> (raw)
In-Reply-To: <2066CB5D-FC4B-49CE-893A-A430D933C425@covisp.net>

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

On 14 May 2020, at 12:18, Lewis Butler <lbutler@covisp.net> wrote:
>  That works as expected, so the problem is a plugin or OMZ

Spoke to soon, while the prompt is working ok on my Mac, it is not working on the FreeBSD machine. I stripped out all the zsh and plugins from my .zshrc and have this:

# cat ~/.zshrc
export PATH=/usr/local/bin:$PATH
HYPHEN_INSENSITIVE="true"
ENABLE_CORRECTION="true"
COMPLETION_WAITING_DOTS="true"

# PROMPT

# Have tried %3G and %4G
function toon { echo -n "%{👹%2G%}" }

setopt PROMPT_SUBST
PROMPT='$(toon)%F{blue]%}%n@%m%f %F{green}%}#%f '
RPROMPT='%F{green}%}[%T] %f[%~] '

source ~/.zshaliases
source ~/.zshfunctions
source /usr/local/share/zsh-autosuggestions/zsh-autosuggestions.zsh
fpath=(/usr/local/share/zsh-completions $fpath)
source /usr/local/share/zsh-syntax-highlighting/zsh-syntax-highlighting.zsh

Which results in a prompt:

👹lbutlr@mail #_		[13:37] [~] 

Where _ is the cursor position.

So, once again the space after the # is being eaten.

If I remove the $(toon) from PROMPT, it works as expected.

I did find a very old note (Jan 2014) about a similar issue when using tmux (which I use) but the note said that calling tmux -u (which I do) avoids this issue.

<https://askubuntu.com/questions/410048/utf-8-character-not-showing-properly-in-tmux <https://askubuntu.com/questions/410048/utf-8-character-not-showing-properly-in-tmux>>

# grep sshf .zshaliases:
alias sshf='ssh <my server> -t tmux -u new-session -A -s mail'

-- 
ɹןʇnqן
<mailto:lbutler@covisp.net>
tel:+1.303.219.0564




  reply	other threads:[~2020-05-17 19: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
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 [this message]
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=062FFA20-B1CE-40DC-9B9A-F57315542A1F@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).