prezto: async_job:zpty:12 no such pty command: prompt_pure

I’m not sure what triggers it, but occasionally a session will show the output:

~/.config
❯ rm -rf something
async_job:zpty:12: no such pty command: prompt_pure

and then, every enter press at that prompt will show the same output:

~/.config
❯ 
async_job:zpty:12: no such pty command: prompt_pure

Prezto commit: 8914274
ZSH version: 5.7.1
OS information: Arch 5.2.11

About this issue

Original URL
State: closed
Created 5 years ago
Reactions: 32
Comments: 31 (6 by maintainers)

Most upvoted comments

I’m getting this too, but on prompt_sorin.

async_job:zpty:12: no such pty command: prompt_sorin

+12

ackerleytng on Sep 24, 2019

I was getting the same issue using pure, it seems to be fixed by changing the symlink in /modules/prompt/functions/async to point to the async.zsh in the /modules/prompt/external/pure rather than /modules/prompt/external/async. I am not sure if I am losing any functionality but this might help to narrow down the issue!

JustinKnueppel on Nov 19, 2019

async_job:zpty:12: no such pty command: prompt_sorin

Here too, fresh install

rgessner on Nov 6, 2019

For reference, this is the straightforward fix:

cd ~/.zprezto/modules/prompt/external/async
git checkout tags/v1.1.0

logout and reopen your shell

avivace on Feb 23, 2020

I was receiving this on prompt_pure.

I upgraded the pure submodule to 1.11 tag and the issue disappeared.

synasius on Feb 6, 2020

I’ve had this issue for some time, on all machines I use (Ubuntu 19.04 and 19.10). The workaround suggested by @JustinKnueppel works for me. I’ve also recently noticed that stderr has been set to null (ls /proc/self/fd shows 2 as symbolic link to /dev/null). I’ve not been able to discern a patter to when this occurs. This also seems to have gone away after applying the workaround.

magne on Nov 21, 2019

Spamming ctrl + c in the command line reproduced it very reliably for me before.

Mentioum on Oct 29, 2019