zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Felipe Contreras <felipe.contreras@gmail.com>
Cc: zsh-workers@zsh.org
Subject: Re: [PATCH v2] prompt: support generic non-visible regions
Date: Wed, 17 Aug 2022 15:48:02 -0700	[thread overview]
Message-ID: <CAH+w=7ZrxuWET6NGkVLBdCt+oT2esou7y1BJ6JKzRTG6zGfgYw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7ZrUfQV6QRcfjCzJkdYM8bTgZkR3p0W4cWxJZEUOSS8CQ@mail.gmail.com>

On Wed, Aug 17, 2022 at 3:31 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Mon, Aug 15, 2022 at 2:37 PM Felipe Contreras
> <felipe.contreras@gmail.com> wrote:
> >
> > Do we want something like "\001foo\002%\001bar%\002"?
>
> More on this below.

Oops, forgot to come back to that.

If nesting isn't a concern, then %{\001%} would do it, just change the
tests in the patch to be
(bv->dontcount == 0 && *bv->fm == 0x01)
I don't think there's any reason to treat control characters as non-zero-width?

(Note I'm hoping for input from others than Filipe and I on whether
nesting is important.)

If nesting is a problem, then I suppose yes, we need %\001 like we
have %% and %).  Other suggestions welcome.


  reply	other threads:[~2022-08-17 22:48 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 23:09 Felipe Contreras
2022-08-14 19:57 ` Bart Schaefer
2022-08-14 22:46   ` Felipe Contreras
2022-08-15  1:00     ` Bart Schaefer
2022-08-15 21:37       ` Felipe Contreras
2022-08-17 22:31         ` Bart Schaefer
2022-08-17 22:48           ` Bart Schaefer [this message]
2022-08-22  0:17             ` Felipe Contreras
2022-08-22  0:15           ` Felipe Contreras
2022-08-22  0:11 ` [PATCH v3] " Felipe Contreras

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=7ZrxuWET6NGkVLBdCt+oT2esou7y1BJ6JKzRTG6zGfgYw@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=felipe.contreras@gmail.com \
    --cc=zsh-workers@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).