Removing ble.sh from .bashrc prepends an @ to PS1

[Strykar]

If I comment out ble.sh from my .bashrc, my PS1 looks like @[strykar@i-5 ~]$ instead of [strykar@i-5 ~]$ since my .bashrc has PS1='[\u@\h \W]\$ '.

@[strykar@i-5 ~]$ echo $PS1
\[\e]133;k;start_kitty\a\]\[\e]133;A\a\]\[\e]133;k;end_kitty\a\][\u@\h \W]\$ \[\e]133;k;start_suffix_kitty\a\]\[\e[5 q\]\[\e]2;\w\a\]\[\e]133;k;end_suffix_kitty\a\]
@[strykar@i-5 ~]$ 

PS1 is fine after re-enabling ble.sh.
How do I troubleshoot this?

[akinomyoga]

From #257

[strykar@i-5 ~]$ @echo $PS1
[\u@\h \W]\$

[strykar@i-5 ~]$ @

If PS1=[\u@\h \W]\$ the terminal should look like [strykar@i-5 ~]$ instead of [strykar@i-5 ~]$ @.
If I disable ble.sh, the prompt is prepended with the @ like @ [strykar@i-5 ~]$.

I am a bit confused. If it is the problem when you do not have ble.sh, how do you think it is related to ble.sh? Or, did you actually intend to write "If I enable ble.sh"? Hmm, or do you mean that an unexpected @ is prepended without ble.sh and appended with ble.sh?

[Strykar]

The last, it is prepended without ble.sh and appended when ble.sh is sourced.

[Strykar]

Only the first option appears to remedy the situation:

[strykar@i-5 ~]$ @env -i INPUTRC=/dev/null HOME=$HOME USER=$USER TERM=$TERM HISTFILE=~/a.tmp PS1='\w\$ ' bash --norc                                                                                                                                                                       ~
~$ exit            # Notice the missing '@' here
exit
[strykar@i-5 ~]$ @env -i HOME=$HOME USER=$USER TERM=$TERM HISTFILE=~/a.tmp PS1='\w\$ ' bash --norc                                                                                                                                                                                         ~
@~$ exit
exit
[strykar@i-5 ~]$ @env -i HOME=$HOME USER=$USER TERM=$TERM HISTFILE=~/a.tmp PS1='[\u@\h \W]\$ ' bash --norc                                                                                                                                                                                 ~
@[strykar@i-5 ~]$

[akinomyoga]

(Please forget about this comment. I think this is irrelevant now.)

OK! If so, I guess the problem does not appear with the session started as the following. Is it correct?

$ bash --noprofile
$      # <-- check the behavior
$ exit # <-- close the session

[akinomyoga]

This means that your ~/.inputrc is related to the behavior.

Ah, OK. I think now I understand what is happening. Don't you have the following line in your ~/.inputrc?

set show-mode-in-prompt on

[Strykar]

Fixed!! Thank you so much!
I had added that years ago and forgotten about it:

#set editing-mode vi
set show-mode-in-prompt on

[akinomyoga]

Great. Let me summarize the solution in another reply.

[akinomyoga]

Here's the summary. This turned out to be caused by the readline setting set show-mode-in-prompt on. This is a feature of GNU Readline, and the character @ is used to represent that we are currently in Emacs editing mode. You can remove or comment out the corresponding line in your ~/.inputrc, ~/.bashrc, etc.

When ~/.inputrc contains the setting:

# inputrc

# If you have the following line, you can comment it out or remove it
set show-mode-in-prompt on

When ~/.bashrc or other files sourced from ~/.bashrc contains the setting:

# bashrc

# If you have the following line in bashrc, you can comment it out or remove it
bind 'set show-mode-in-prompt on'

[Strykar]

Thank you for taking the time to help me troubleshoot this, and for your amazing software ble.sh, whose surface and power, I have barely scratched! 🙏