Commit: runtime(doc): update for new keyprotocol option value (after v9.1.0969)
5 views
Skip to first unread message
Christian Brabandt
Dec 28, 2024, 11:30:11 AM12/28/24
to vim...@googlegroups.com
runtime(doc): update for new keyprotocol option value (after v9.1.0969)
Commit: https://github.com/vim/vim/commit/f6ba8defc62e18363752c6c78c76865dd53acd57
Author: Christian Brabandt <c...@256bit.org>
Date: Sat Dec 28 17:15:05 2024 +0100
runtime(doc): update for new keyprotocol option value (after v9.1.0969)
Signed-off-by: Christian Brabandt <c...@256bit.org>
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 7c32384e1..489415c78 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 9.1. Last change: 2024 Dec 14
+*options.txt* For Vim version 9.1. Last change: 2024 Dec 28
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -5072,11 +5072,12 @@ A jump table for the options with a short description can be found at |Q_op|.
a pattern that is matched against the 'term' option, a colon and the
protocol name to be used. To illustrate this, the default value would
be set with: >
- set keyprotocol=kitty:kitty,foot:kitty,wezterm:kitty,xterm:mok2
+ set keyprotocol=kitty:kitty,foot:kitty,ghostty:kitty,wezterm:kitty
+ set keyprotocol+=xterm:mok2
-< This means that when 'term' contains "kitty, "foot" or "wezterm"
- somewhere then the "kitty" protocol is used. When 'term' contains
- "xterm" somewhere, then the "mok2" protocol is used.
+< This means that when 'term' contains "kitty, "foot", "ghostty" or
+ "wezterm" somewhere, then the "kitty" protocol is used. When 'term'
+ contains "xterm" somewhere, then the "mok2" protocol is used.
The first match is used, thus if you want to have "kitty" use the
kitty protocol, but "badkitty" not, then you should match "badkitty"
diff --git a/runtime/doc/version9.txt b/runtime/doc/version9.txt
index 34ccf88bf..35921032e 100644
--- a/runtime/doc/version9.txt
+++ b/runtime/doc/version9.txt
@@ -41619,6 +41619,8 @@ Changed~
increased to 12pt to accomodate modern high-dpi monitors
- filetype detection now detects bash scripts as a separate "bash filetype
instead of the "sh" filetype
+- the default value of the 'keyprotocol' option has been updated by support
+ for the ghostty terminal emulator (using kitty protocol)
*added-9.2*
Added ~
Commit: https://github.com/vim/vim/commit/f6ba8defc62e18363752c6c78c76865dd53acd57
Author: Christian Brabandt <c...@256bit.org>
Date: Sat Dec 28 17:15:05 2024 +0100
runtime(doc): update for new keyprotocol option value (after v9.1.0969)
Signed-off-by: Christian Brabandt <c...@256bit.org>
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 7c32384e1..489415c78 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -1,4 +1,4 @@
-*options.txt* For Vim version 9.1. Last change: 2024 Dec 14
+*options.txt* For Vim version 9.1. Last change: 2024 Dec 28
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -5072,11 +5072,12 @@ A jump table for the options with a short description can be found at |Q_op|.
a pattern that is matched against the 'term' option, a colon and the
protocol name to be used. To illustrate this, the default value would
be set with: >
- set keyprotocol=kitty:kitty,foot:kitty,wezterm:kitty,xterm:mok2
+ set keyprotocol=kitty:kitty,foot:kitty,ghostty:kitty,wezterm:kitty
+ set keyprotocol+=xterm:mok2
-< This means that when 'term' contains "kitty, "foot" or "wezterm"
- somewhere then the "kitty" protocol is used. When 'term' contains
- "xterm" somewhere, then the "mok2" protocol is used.
+< This means that when 'term' contains "kitty, "foot", "ghostty" or
+ "wezterm" somewhere, then the "kitty" protocol is used. When 'term'
+ contains "xterm" somewhere, then the "mok2" protocol is used.
The first match is used, thus if you want to have "kitty" use the
kitty protocol, but "badkitty" not, then you should match "badkitty"
diff --git a/runtime/doc/version9.txt b/runtime/doc/version9.txt
index 34ccf88bf..35921032e 100644
--- a/runtime/doc/version9.txt
+++ b/runtime/doc/version9.txt
@@ -41619,6 +41619,8 @@ Changed~
increased to 12pt to accomodate modern high-dpi monitors
- filetype detection now detects bash scripts as a separate "bash filetype
instead of the "sh" filetype
+- the default value of the 'keyprotocol' option has been updated by support
+ for the ghostty terminal emulator (using kitty protocol)
*added-9.2*
Added ~
Reply all
Reply to author
Forward
0 new messages