zsh-workers
 help / color / mirror / code / Atom feed
From: Mikael Magnusson <mikachu@gmail.com>
To: zsh workers <zsh-workers@zsh.org>
Subject: Re: Strange initial escape string
Date: Sat, 15 Jun 2013 14:22:36 +0200	[thread overview]
Message-ID: <CAHYJk3TDMbdHHRyTy92Gcnds=DH1mjM2zkgPj_xa-7CsbhmByA@mail.gmail.com> (raw)
In-Reply-To: <CAM8HBcXCQ_OgEMoq_5fUDPv5NqoX-87uz8cYCUSeGnMCQFi4dw@mail.gmail.com>

On 15 June 2013 13:31, Mario Signorino <mario.signorino@gnufish.net> wrote:
> On Fri, May 31, 2013 at 7:10 AM, Bart Schaefer <schaefer@brasslantern.com>
> wrote:

> Now some question:
> I've used some custom escape codes ( \033| ) to surround the important
> info. Now I can trap these strings and easily work on them. This is
> working. The problem is in the prompt. My PS1 is something like that:
>
> export XPIPETERMINATOR=$'\033|.'
> PS1="${XPIPETERMINATOR}mario@squit $ "
>
> that "terminator" tells to my terminal that the previous command has just
> finished. I use it to close any pending operation (show icons... git fancy
> output): if I receive that, it means *for sure* that I am again on the
> standard prompt.
> The problem is that zsh does not know anything about that escape codes and
> it thinks to have written more chars than it actually has: and it sends the
> carriage return too early (when I reach the end of the line).
> So: how can I tell to zsh to forget those 2 or 3 special chars?

%{ %}

--
Mikael Magnusson


  reply	other threads:[~2013-06-15 12:22 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-30 21:28 Mario Signorino
2013-05-30 22:56 ` Mario Signorino
2013-05-31  5:10   ` Bart Schaefer
2013-06-15 11:31     ` Mario Signorino
2013-06-15 12:22       ` Mikael Magnusson [this message]
2013-06-15 18:44       ` Bart Schaefer
2013-06-15 19:14         ` Mario Signorino

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='CAHYJk3TDMbdHHRyTy92Gcnds=DH1mjM2zkgPj_xa-7CsbhmByA@mail.gmail.com' \
    --to=mikachu@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).