acomagu / fish-async-prompt

Make your prompt asynchronous to improve the reactivity.
MIT License
389 stars 22 forks source link

Clean install on Ubuntu results in multiple "disown: There are no suitable jobs" after every command #67

Open Kintar opened 1 year ago

Kintar commented 1 year ago

Reproduction steps:

Install Ubuntu Install Fish Install fisher Install fish-async-prompt

Result:

$ fisher install acomagu/fish-async-prompt                                       
fisher install version 4.4.3
Fetching https://api.github.com/repos/acomagu/fish-async-prompt/tarball/HEAD
Installing acomagu/fish-async-prompt
           /home/alanter/.config/fish/conf.d/__async_prompt.fish
Installed 1 plugin/s
disown: There are no suitable jobs
disown: There are no suitable jobs
 ~

This has happened to me on two clean installs now. One of them started working after a wipe and reinstall of Fish. The other did not.

acomagu commented 1 year ago

Thank you for reporting.

Could you tell me what version of Fish are you using?

Kintar commented 1 year ago

Yes, sorry! Fish 3.6.0 on one machine, and 3.6.1 on another.

acomagu commented 12 months ago

I tried to reproduce with the following steps, but could not reproduce...

Install Ubuntu 22.04.2
sudo apt-add-repository ppa:fish-shell/release-3
sudo apt update
sudo apt install fish  # 3.6.1
curl -sL https://raw.githubusercontent.com/jorgebucaran/fisher/main/functions/fisher.fish | source && fisher install jorgebucaran/fisher
fisher install acomagu/fish-async-prompt

Seems working correctly.

bdmorin commented 11 months ago

Fresh install today, having same issue.

fish --version                                                                                                     Wed Aug  2 11:45:56 2023
fish, version 3.6.1
disown: There are no suitable jobs
disown: There are no suitable jobs

uname -a                                                                                                               Wed Aug  2 11:46:08 2023
Darwin n0x.local 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000 arm64
disown: There are no suitable jobs
disown: There are no suitable jobs

happy to provide more info, just let me know what.

wiillou commented 10 months ago

Im having this issue too on nixos unstable using the pure prompt

ar065 commented 9 months ago

Having this issue on Debian GNU/Linux 12 (bookworm) on Windows 10 x86_64 (Its Windows 11 WSL, I have no idea why it still says windows 10)

kimusan commented 9 months ago

Just want to chime in that I see it in Ubuntu in WSL2 (win10)

acomagu commented 4 months ago

@wiillou I couldn't also reproduce on Nix unstable. Could you provide a reproducible Nix file?

acomagu commented 4 months ago

@Kintar @bdmorin @wiillou @ar065 @kimusan Sorry for the inconvenience. Still I have not figured out the cause of this problem so I need to investigate more, but anyway, I added a flag to disable the disown for now. set -g async_prompt_disown 1 may improve the situation. Please refer README.

acomagu commented 4 months ago

I haven't been able to reproduce the issue in my environment yet, so it would be greatly appreciated if someone could provide a Dockerfile or similar.

wiillou commented 4 months ago

hello, i have tried to reproduce it on a nixos-shell, but for some reason i still cannot, it only happens on my full build of my system

petertriho commented 1 week ago

Also on nixos (wsl)

Disabling disown removes the disown: There are no suitable jobs error messages but makes the commandline slow. Seems like there's a command that is timing out.

EDIT: Found the issue for me, it was this plugin https://github.com/oh-my-fish/plugin-grc