help / color / mirror / code / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: zsh-workers@zsh.org, Bart Schaefer <schaefer@brasslantern.com>,
	 Roman Perepelitsa <roman.perepelitsa@gmail.com>
Subject: Re: [PATCH v3 try2] prompt: support generic non-visible regions
Date: Wed, 1 Mar 2023 06:54:26 -0600	[thread overview]
Message-ID: <CAMP44s0s8SUtR3BpG4=esEzqU8XU1QDZFWgRz3+vidcahhTyMA@mail.gmail.com> (raw)
In-Reply-To: <74532-1677601785.546332@Gkr5.eJZU.TqFp>

On Tue, Feb 28, 2023 at 10:29 AM Oliver Kiddle <opk@zsh.org> wrote:
> Felipe Contreras wrote:
> > readline uses \001 (start of header) and \002 (start of text) as markers
> So the literal ASCII Ctrl-A and Ctrl-B characters and not the \001 etc
> strings, right?


> The main concern I have with this is whether there definitely is no use
> of those two characters anywhere by any terminal for some other purpose
> such that some user somewhere has them already in their prompt?

If that was an issue, wouldn't bash users have already experienced it
in the years this code has been active? (or possibly decades)

Moreover, can we agree that it's at least extremely unlikely for this
to be an actual issue?

> And do we know they won't form part of some other future terminal
> sequence?

Once again, can we agree that's unlikely? (especially since bash
already uses these)

> We can find a special way to generate the literal characters but that
> only helps with future uses, not backward compatibility.

Like what? A setopt flag?

> I can understand the motivation to be able to support the lack of
> prompt_percent and perhaps both bash and zsh in some plugin or other.

I personally don't care about the prompt_percent stuff, somebody else
mentioned it. The usefulness of sharing prompts between bash and zsh
is what I'm interested in.

> > +     } else if(*bv->fm == 0x01) { // start non-visible characters
> For now, we've not, to my knowledge, bumped our requirements to cover
> C99, C17 etc so stick with old-style C comments in the code.*

OK. Will fix in the next version.

Felipe Contreras

  reply	other threads:[~2023-03-01 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 15:55 Felipe Contreras
2023-02-28 16:29 ` Oliver Kiddle
2023-03-01 12:54   ` Felipe Contreras [this message]
2023-02-28 19:36 ` Bart Schaefer
2023-03-08  4:04 ` [PATCH v4] " 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMP44s0s8SUtR3BpG4=esEzqU8XU1QDZFWgRz3+vidcahhTyMA@mail.gmail.com' \
    --to=felipe.contreras@gmail.com \
    --cc=opk@zsh.org \
    --cc=roman.perepelitsa@gmail.com \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \


* 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


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).