zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: "off by one fix in multiple prompts" breaks multiline prompt
Date: Tue, 14 Aug 2018 09:30:15 +0100	[thread overview]
Message-ID: <20180814083016eucas1p2d426f9513c46e155c16bc33b3b443582~KsvuGgKmW2478124781eucas1p2Q@eucas1p2.samsung.com> (raw)
In-Reply-To: <8201EC10-DCE3-4E29-8B9A-C047E843153A@dana.is>

On Mon, 13 Aug 2018 17:44:32 -0500
dana <dana@dana.is> wrote:
> The change from >= to > seems bogus to me now — it only works by
> accident in that one case. As far as the new-line check, i'm not sure
> how to determine if that's a good direction, besides just trying it
> in different terminals. I can do that later if it's not completely
> disproven already.

Thanks very much --- this certainly sounds like a step in the right
direction, so I've committed it and we'll see if anyone turns up any
further problems we can actually deal with.

pws



  reply	other threads:[~2018-08-14  8:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20180810072702epcas5p4ecaa5cffa5dc7668e2b2aa3a30824f36@epcas5p4.samsung.com>
2018-08-10  7:26 ` Guillaume Chazarain
2018-08-13  8:42   ` Peter Stephenson
2018-08-13 11:22     ` Guillaume Chazarain
2018-08-13 11:36       ` Peter Stephenson
2018-08-13 11:42         ` Guillaume Chazarain
2018-08-13 12:58           ` Peter Stephenson
2018-08-13 14:19             ` dana
2018-08-13 18:34               ` Guillaume Chazarain
2018-08-13 21:29               ` dana
2018-08-13 21:45                 ` Bart Schaefer
2018-08-13 22:44                   ` dana
2018-08-14  8:30                     ` Peter Stephenson [this message]
2018-08-14  6:41                 ` Guillaume Chazarain
     [not found]       ` <20180813123639.5899f64e@camnpupstephen.cam.scsc.local>
2018-08-13 11:40         ` Peter Stephenson

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='20180814083016eucas1p2d426f9513c46e155c16bc33b3b443582~KsvuGgKmW2478124781eucas1p2Q@eucas1p2.samsung.com' \
    --to=p.stephenson@samsung.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).