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
Currently, programs.kitty.shellIntegration.enable*Integration seemed to require respective shells to be enabled. With its default calculated by !(elem "disabled" (splitString " " config.programs.kitty.shellIntegration.mode)), which seemed to be true for all shells by default if integration mode is set to something enabling. Hence, to reduce confusion of not getting the integration after enabling, it may worth adding a note that these options depends on programs.<shell>.enable=true to work, in the descriptions of these options.
The text was updated successfully, but these errors were encountered:
I think the conditionals should be somewhat flipped for those options. Maybe set their default value to programs.<shell>.enable and just make it a noop if shell integration is disabled.
Description
Currently,
programs.kitty.shellIntegration.enable*Integration
seemed to require respective shells to be enabled. With its default calculated by!(elem "disabled" (splitString " " config.programs.kitty.shellIntegration.mode))
, which seemed to be true for all shells by default if integration mode is set to something enabling. Hence, to reduce confusion of not getting the integration after enabling, it may worth adding a note that these options depends onprograms.<shell>.enable=true
to work, in the descriptions of these options.The text was updated successfully, but these errors were encountered: