kitty: add shellIntegration

[Scrumplex]

Description

Kitty provides integrations for bash, fish and zsh. The new programs.kitty.shellIntegration options allow the configuration of these integrations.

See https://sw.kovidgoyal.net/kitty/shell-integration for more details

Checklist

• Change is backwards compatible.

• Code formatted with ./format.

• Code tested through nix-shell --pure tests -A run.all.

• Test cases updated/added. See example.

• Commit messages are formatted like

  {component}: {description}
  
  {long description}
  

  See CONTRIBUTING for more information and recent commit messages for examples.

• If this PR adds a new module

  • Added myself as module maintainer. See example.

  • Added myself and the module files to .github/CODEOWNERS.

[ncfavier]

It's a bit confusing to have enable = true, enable*Integration = true and mode = "enabled". Can we simplify this?

[Scrumplex]

Hmm. What if we get rid of enable and only check if one of the enable*Integration options is true?

[Scrumplex]

Or alternatively, check if mode != "disabled"

[ncfavier]

At startup, kitty detects if the shell you have configured (either system wide or the shell option in kitty.conf) is a supported shell. If so, kitty injects some shell specific code into the shell, to enable shell integration.

If kitty does this automatically, why do we have to do it ourselves?

[Scrumplex]

It is just more robust, especially for more complex workflows:

The automatic shell integration is designed to be minimally intrusive, as such it wont work for sub-shells, terminal multiplexers, containers, etc. For such systems, you should setup manual shell integration by adding some code to your shells startup files to load the shell integration script.

[erooke]

It is just more robust, especially for more complex workflows:

The automatic shell integration is designed to be minimally intrusive, as such it wont work for sub-shells, terminal multiplexers, containers, etc. For such systems, you should setup manual shell integration by adding some code to your shells startup files to load the shell integration script.

Also, the way kitty does this is by modifying the bashrc at runtime which it can't do if the bashrc is managed by home manager.