More sophisticated PATH resolution for the launch command

This commit is contained in:
Kovid Goyal
2020-12-29 11:51:17 +05:30
parent c1b7023e3a
commit 2a026de526
3 changed files with 24 additions and 2 deletions

View File

@@ -13,6 +13,10 @@ To update |kitty|, :doc:`follow the instructions <binary>`.
- Add entries to the terminfo file for some user capabilities that are shared
with XTerm (:pull:`3193`)
- The launch command now does more sophisticated resolving of executables to
run. The system-wide PATH is used first, then system specific default paths,
and finally the PATH inside the shell.
0.19.3 [2020-12-19]
-------------------

View File

@@ -93,6 +93,16 @@ in the window and ``window.id`` is the internal kitty ``id`` of the
window.
Finding executables
-----------------------
When you specify a command to run as just a name rather than an absolute path,
it is searched for in the system-wide ``PATH`` environment variable. Note that
this **may not** be the value of ``PATH`` inside a shell, as shell startup scripts
often change the value of this variable. If it is not found there, then a
system specific list of default paths is searched. If it is still not found,
then your shell is run and the value of ``PATH`` inside the shell is used.
Syntax reference
------------------