From 4847fb52cc54c5610f6ba0234fc784f45ef97f4a Mon Sep 17 00:00:00 2001 From: Kovid Goyal Date: Fri, 6 Apr 2018 08:16:14 +0530 Subject: [PATCH] Updates to README --- README.asciidoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/README.asciidoc b/README.asciidoc index 5e608db63..d3014bcc3 100644 --- a/README.asciidoc +++ b/README.asciidoc @@ -328,7 +328,8 @@ By default kitty looks for a config file in the OS config directories (usually `~/Library/Preferences/kitty/kitty.conf` on macOS) but you can pass a specific path via the `--config` option or use the `KITTY_CONFIG_DIRECTORY` environment variable. See the help for the `--config` option in `kitty --help` for full -details. +details. You can also dump the current configuration kitty is using using the +`--debug-config` option. == Startup Sessions @@ -534,7 +535,7 @@ for kitty and use `kitty @ set-colors --help`. Apple does not want you to use command line options with GUI applications. To workaround that limitation, kitty will read command line options from the file -`~/Library/Preferences/kitty/macos-launch-services-cmdline` when it is launched +`/macos-launch-services-cmdline` when it is launched from the GUI, i.e. by clicking the kitty application icon or using `open -a kitty`. Note that this file is *only read* when running via the GUI.