zsh-workers
 help / color / mirror / code / Atom feed
From: "Nikolay Aleksandrovich Pavlov (ZyX)" <kp-pav@yandex.ru>
To: Bart Schaefer <schaefer@brasslantern.com>,
	Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Weird behaviour of a multiline prompt
Date: Sun, 30 Oct 2016 00:44:04 +0300	[thread overview]
Message-ID: <1269451477777444@web17m.yandex.ru> (raw)
In-Reply-To: <161029114131.ZM17050@torch.brasslantern.com>



29.10.2016, 21:49, "Bart Schaefer" <schaefer@brasslantern.com>:
> On Oct 29, 9:13pm, Nikolay Aleksandrovich Pavlov (ZyX) wrote:
> }
> } PS1=$'abc\n'
> }
> } (i.e. non-empty line above an empty prompt) then it shows up as
> } expected when I replace my prompt with this. But when I try using
> } exactly the same prompt in `pexpect` zsh no longer shows any prompt at
> } all: neither `abc`, nor RPS1.
>
> Check to see if the SINGLE_LINE_ZLE option has become set when inside
> pexpect? RPS1 is not printed in single-line mode, and only the last
> line of PS1.

My test suite is testing multiline prompts which also have PS1 and this works, up until I do not try to use prompt with empty last line. A check shows that `$options[singlelinezle]` evaluates to `off` while this problem is in effect.

>
> Fix would be to force the environment value of LINES to be something
> greater than 1 for pexpect.

Though making $LINES actually be 3 (in pexpect I used 1x300 screen, 2x300 neither did work well) fixes this bug and previously ignored bug with RPS1 not showing up was also fixed, thanks.


      reply	other threads:[~2016-10-29 21:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-29 18:13 Nikolay Aleksandrovich Pavlov (ZyX)
2016-10-29 18:41 ` Bart Schaefer
2016-10-29 21:44   ` Nikolay Aleksandrovich Pavlov (ZyX) [this message]

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=1269451477777444@web17m.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=schaefer@brasslantern.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).