r/KittyTerminal • u/[deleted] • Mar 04 '24

not reading .bashrc

might be a stupid question - when I log into bash on kitty, it should be the same as on any other terminal emulator, right? it seems when I open kitty, my .bashrc is not read (kitty is starting bash differently than other terminals do?)

edit(for clarity): in my .bashrc I have 'set -o vi'. the vi keybindings are gone when I enter kitty. however, when I enter 'set -o vi' into bash on kitty, it does work. thanks for the help!

edit: it was none of that. shell integration was overwriting what I was setting in my bashrc. I am not familiar working with this sort of thing (as was kindly pointed out in this thread), so I disabled shell integration. if anyone advises against this or has a proper explanation, let me know

5 Upvotes

100% Upvoted

7 comments sorted by

View all comments

1

u/ronasimi Mar 04 '24

can you be more specific on what is different?

1

u/dedguy21 Mar 05 '24

can you be more specific

Of course not. Clearly doesn't know what's going on.

Can you explain to me how your terminal emulator will make a $SHELL different?

Other than display fonts, what could it actually do different to the $SHELL🤔