Cursor style for bash vi mode not what I expect

[DylanGriffith]

I would like ghostty to switch between bar and block cursor in vi mode in bash. But I'm only seeing a bar cursor for some reason.

I have a minimal setup with:

# ~/.bashrc

set -o vi

if [ -n "${GHOSTTY_RESOURCES_DIR}" ]; then
    builtin source "${GHOSTTY_RESOURCES_DIR}/shell-integration/bash/ghostty.bash"
fi

# ~/.bash_profile

set -o vi

When I start up ghostty I have a bar cursor. When I type some text and hit "escape" I still have a bar cusor. I would expect a block cursor when in "normal mode" for VI.

Am I missing something?

I did find the following similar-ish issues, but none of them seem to match what I'm seeing:

1. Cursor style over SSH in vi mode #3797
2. Trying to understand cursor style #3836

[rhodes-b]

https://ghostty.org/docs/config/reference#cursor-style
read the note here

[DylanGriffith]

Thanks for the link. I'm not able to get the suggestions in there to work with iTerm or Ghostty but in any case I think this highlights that it's not really a Ghostty issue.

Still, if anyone happens to figure out the right way to configure this in Ghostty I'd love to hear it.

[rhodes-b]

https://docs.warp.dev/features/editor/vim
it looks like warp has a bunch of extra functionality for vi mode, which means I dont think it will work in ghostty

with shell integration off I was able to get underline cursor with echo -e "\e[4 q in ghostty im not sure how you hook that up to bash though. Ghostty doesnt have any explicit special vi mode

[00-kat]

with shell integration off

I had noticed this in the past too. I have a solution basically identical to the StackOverflow link above in my inputrc, and noticed that sourcing the Bash shell integration breaks it.

[DylanGriffith]

Thanks @00-kat that seems to work for me too.

sourcing the Bash shell integration breaks it

I'm kinda confused now because basically I find that Bash shell integration makes everything worse. When I enable it I also find that it fails to correctly detect which program is running. It always just shows a Ghost icon in the title bar and always prompts me for confirmation when closing a window.

But without bash integration it works as expected and also I can get my cursor to work the way I want.

I'm now curious about what I'm missing by not using bash integration.

[00-kat]

I'm kinda confused now because basically I find that Bash shell integration makes everything worse. When I enable it I also find that it fails to correctly detect which program is running. It always just shows a Ghost icon in the title bar and always prompts me for confirmation when closing a window.

Interesting, that's the exact opposite experience I have. If I have shell integration disabled, it always prompts me and it doesn't ever update the title based on the current working directory. And if I enable it, things work fine.

But without bash integration it works as expected and also I can get my cursor to work the way I want.

You could use shell-integration-features = no-cursor even if shell integration is enabled.

I'm now curious about what I'm missing by not using bash integration.

Obligatory documentation link: https://ghostty.org/docs/features/shell-integration#features. Half of those seem to be the opposite for you when it is enabled though, although I can't discern any reason for that.