mirrors/kitty
1
0
Fork 0
mirror of https://github.com/kovidgoyal/kitty synced 2026-07-06 16:05:05 +02:00
Code Issues Packages Projects Releases Wiki Activity

A new command to show the env vars of the kitty process

Browse Source
This commit is contained in:
Kovid Goyal
2021-03-03 16:04:08 +05:30
parent 90c6c2a366
commit 1ded78a98c
2 changed files with 18 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/faq.rst
View File

@@ -270,10 +270,17 @@ and the shell's rc files will have setup a whole different set of environment
variables which kitty will now inherit.
You need to make sure that the environment variables you define in your shell's
rc files are either also defined system wide or via the ``env`` directive in
kitty.conf. Common environment variables that cause issues are those related to
localization, such as ``LANG, LC_*`` and loading of configuration files such as
``XDG_*, KITTY_CONFIG_DIRECTORY``.
rc files are either also defined system wide or via the :opt:`env` directive in
:file:`kitty.conf`. Common environment variables that cause issues are those
related to localization, such as ``LANG, LC_*`` and loading of configuration
files such as ``XDG_*, KITTY_CONFIG_DIRECTORY``.
To see the environment variables that kitty sees, you can add the following
mapping to :file:`kitty.conf`::
map f1 show_kitty_env_vars
then pressing :kbd:`F1` will show you the environment variables kitty sees.
This problem is most common on macOS, as Apple makes it exceedingly difficult to
setup environment variables system-wide, so people end up putting them in all