You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently I've decided to try something new for my zsh and I decided to go with spaceship. Yet after installing it mc subshell stopped working. Basically when I press ctrl+o in mc a black screen appears but I cannot type anything as it brings back mc. After commenting out spaceship from my .zshrc mc subshell starts working again.
Relevant Zsh configuration
# Set up the prompt
autoload -Uz promptinit
promptinit
prompt adam1
setopt histexpiredupsfirst histignorealldups histignoredups histignorespace histverify incappendhistory sharehistory
# Use emacs keybindings even if our EDITOR is set to vi
bindkey -e
# Enable zinitdeclare -A ZINIT
ZINIT[PLUGINS_DIR]="/tmp/zinit_plugs"source"/usr/local/share/zinit/zinit.zsh"# Enable spaceship prompt
zinit snippet OMZP::sudo
zinit light spaceship-prompt/spaceship-prompt
What is version of Spaceship are you using?
v4.10.1
What is version of Zsh are you using?
5.9
What operation system are you running?
Linux (debian unstalbe)
Do you use any Zsh framework or plugin manager?
zinit
Which terminal emulator do you use?
putty
Additional information
No response
The text was updated successfully, but these errors were encountered:
The problem
Recently I've decided to try something new for my zsh and I decided to go with spaceship. Yet after installing it mc subshell stopped working. Basically when I press ctrl+o in mc a black screen appears but I cannot type anything as it brings back mc. After commenting out spaceship from my .zshrc mc subshell starts working again.
Relevant Zsh configuration
What is version of Spaceship are you using?
v4.10.1
What is version of Zsh are you using?
5.9
What operation system are you running?
Linux (debian unstalbe)
Do you use any Zsh framework or plugin manager?
zinit
Which terminal emulator do you use?
putty
Additional information
No response
The text was updated successfully, but these errors were encountered: