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
$ ble summaryGNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu) [Artix Linux]ble.sh, version 0.4.0-devel4+17646524 (noarch) [git 2.47.1, GNU Make 4.4.1, GNU Awk 5.3.1, API 4.0, PMA Avon 8-g1, (GNU MPFR 4.2.1, GNU MP 6.3.0)]bash-completion, version 2.15.0 (hash:480ffcc6a751e55621ec526eb5dea7a0d86d9e72, 17877 bytes) (noarch)fzf key-bindings, (hash:2da32cbab672fc962b4c56c6a052a6bf47ef2c12, 5618 bytes) (noarch) �[1m(integration: on)fzf completion, (hash:afdb947635ba13e3f5a5f6d147f943e43f7dbbf3, 17559 bytes) (noarch) �[1m(integration: on)bash-preexec, (hash:14a677888d35643b5ade7558b75ecc25746ac05b, 14704 bytes) (noarch)locale: LANG=it_IT.utf8terminal: TERM=xterm-ghostty wcwidth=15.0-west/16.0-2+ri, xterm:10 (1;10;0)options: -emacs +vi +extglob +histappend -hostcomplete +inherit_errexit
While using Ghostty with shell integration enabled, after I run the first command, the left prompt becomes [ble: press RET to continue]. Right prompt and status bar are fine.
I actually have no idea if this issue is from Ghostty or from Blesh, but you gotta start from somewhere.
The text was updated successfully, but these errors were encountered:
How do you load ble.sh in your ~/.bashrc? Do you have --attach=none and ble-attach? Or do you simply source ble.sh without ble-attach? If you use the former setup with ble-attach, it wouldn't work because ble-attach needs to be performed at the end of the shell startup file, while the Ghostty shell integration tries to execute something non-trivial after sourcing ~/.bashrc. Could you try simply sourcing ble.sh without using ble-attach and see if the behavior changes?
While using Ghostty with shell integration enabled, after I run the first command, the left prompt becomes
[ble: press RET to continue]
. Right prompt and status bar are fine.I actually have no idea if this issue is from Ghostty or from Blesh, but you gotta start from somewhere.
The text was updated successfully, but these errors were encountered: