zsh-workers
 help / color / mirror / code / Atom feed
From: "Franco Gastón Pellegrini" <francogpellegrini@gmail.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: bug report: key up or down for history scroll inserts and 'e' in some cases
Date: Wed, 17 Jun 2020 06:03:10 -0300	[thread overview]
Message-ID: <CAK+O6wssOuwt-15G0uTFC+eGbM3-4z19oQg47uGyusP4S0B7HA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMqD3uVbw=_=tTxD00DNZF3HJvc8W0wYrGuiJjbvbD_Z0g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

I forgot to mention that bash does not reproduce the problem. Only ZSH.

El mié., 17 de junio de 2020 04:25, Roman Perepelitsa <
roman.perepelitsa@gmail.com> escribió:

> On Wed, Jun 17, 2020 at 1:22 AM Franco Gastón Pellegrini
> <francogpellegrini@gmail.com> wrote:
> > *In the gif I'm using powerlevel10k and lots of scripts, BUT the problem
> > can be reproduced perfectly with a fresh vanilla installation of zsh*
> > It seems that I can reproduce it ONLY on windows v2004, WSL 2, and
> windows
> > terminal
>
> I suggest reporting it to Microsoft Terminal. Make sure that your
> report contains complete instructions to reproduce the problem and
> that they are short. It might look like this:
>
> <report>
>
> To reproduce:
>
> 1. Install Microsoft Terminal from Windows Store. Keep the default
> settings.
> 2. Enable WSL and install Ubuntu 20.04 from Windows Store.
> 3. Start Ubuntu 20.04 via WSL2.
> 4. When bash prompt appears, run:
>     sudo apt-get install -y zsh && zsh -f
> 5. When zsh prompt appears, run:
>     for i in {1..20}; do for x in {a..e}; do print -s $x$i; done; done
> 6. Press and hold the UP key until nothing stops changing on the screen.
>
> - Actual: screenshot.
> - Expected: either a screenshot or textual description.
>
> System information:
>
> - Windows version: xxx.
> - Microsoft Terminal version: xxx.
>
> </report>
>
> Needless to say, verify that *you* can reproduce the issue by
> following these instructions. If you cannot, figure out what needs to
> be added or changed so that the problem reproduces.
>
> Roman.
>

  reply	other threads:[~2020-06-17  9:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-16 23:22 Franco Gastón Pellegrini
2020-06-17  7:25 ` Roman Perepelitsa
2020-06-17  9:03   ` Franco Gastón Pellegrini [this message]
2020-06-17  9:06     ` Roman Perepelitsa

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=CAK+O6wssOuwt-15G0uTFC+eGbM3-4z19oQg47uGyusP4S0B7HA@mail.gmail.com \
    --to=francogpellegrini@gmail.com \
    --cc=roman.perepelitsa@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).