[-- Attachment #1: Type: text/plain, Size: 670 bytes --] https://recordit.co/xndxC0sLyw This gif reproduce the problem. *I'm only pressing up and down keys.* At the beginning you can see whats inside the history file, on the top. It seems that the char 'e' is causing problems for some reason. *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 (using an ubuntu 20.04 distro), but if remote access to my Native Ubuntu server using the same window terminal and configs, it work just fine, as intended. -- Franco Gastón Pellegrini
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.
[-- 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. >
On Wed, Jun 17, 2020 at 11:03 AM Franco Gastón Pellegrini <francogpellegrini@gmail.com> wrote: > > I forgot to mention that bash does not reproduce the problem. Only ZSH. You've mentioned it on https://github.com/romkatv/powerlevel10k/issues/824#issuecomment-645051032. My advice to report this to Microsoft Terminal with good reproduction instructions still stands. Roman.