From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: color codes to eval
Date: Wed, 10 Apr 2024 12:17:19 -0700 [thread overview]
Message-ID: <f6f27937-cd16-4da0-bfe3-fbbaa627bdbd@eastlink.ca> (raw)
In-Reply-To: <ZhbjF4CfK2PcPROp@eeyore.local>
[-- Attachment #1: Type: text/plain, Size: 341 bytes --]
On 2024-04-10 12:05, Andreas Kähäri wrote:
> They could also use print with -P and start using the prompt escape
> %F{red}, but that's bypassing the issue rather than handling the
> original string.
Yeah, the eval is buried under three nested levels of called functions,
if it was directly on the command line there'd be no problem.
[-- Attachment #2: Type: text/html, Size: 778 bytes --]
next prev parent reply other threads:[~2024-04-10 19:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 16:46 Ray Andrews
2024-04-10 18:39 ` Lawrence Velázquez
2024-04-10 19:05 ` Andreas Kähäri
2024-04-10 19:17 ` Ray Andrews [this message]
2024-04-10 19:12 ` Ray Andrews
2024-04-11 0:01 ` Lawrence Velázquez
2024-04-11 0:15 ` Ray Andrews
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=f6f27937-cd16-4da0-bfe3-fbbaa627bdbd@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).