Cleanup the previous PR
This commit is contained in:
parent
c3807e175d
commit
a1fc383e6f
@ -53,6 +53,17 @@ Variables that influence kitty behavior
|
||||
directory lookup mechanism see, :option:`kitty --config`.
|
||||
|
||||
|
||||
.. envvar:: VISUAL
|
||||
|
||||
Controls what program kitty uses as an editor, when, for instance, opening
|
||||
kitty.conf in response to :sc:`edit_config_file`
|
||||
|
||||
|
||||
.. envvar:: EDITOR
|
||||
|
||||
Same as :envvar:`VISUAL`. Used if :envvar:`VISUAL` is not set.
|
||||
|
||||
|
||||
Variables that kitty sets when running child programs
|
||||
|
||||
.. envvar:: KITTY_WINDOW_ID
|
||||
|
||||
@ -2418,11 +2418,13 @@ starts in interactive mode and reads its startup rc files.
|
||||
opt('editor', '.',
|
||||
long_text='''
|
||||
The console editor to use when editing the kitty config file or similar tasks.
|
||||
The default value of . means to use the environment variables :envvar:`VISUAL`
|
||||
The default value of ``.`` means to use the environment variables :envvar:`VISUAL`
|
||||
and :envvar:`EDITOR` in that order. Note that these environment variables have
|
||||
to be set when kitty starts, so if they're set in shell startup scripts but
|
||||
kitty is launched directly from your desktop, kitty will not see them. In
|
||||
that case you're better off naming your favorite editor here.
|
||||
to be set when kitty starts, so if they're only set in shell startup scripts, but
|
||||
kitty is launched directly from your desktop, kitty will not see them. kitty does try
|
||||
to read the values from the shell as well, but this process is not entirely robust since
|
||||
there are a myriad different shells out there. In that case you're better off naming
|
||||
your favorite editor here.
|
||||
'''
|
||||
)
|
||||
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user