|
1 | | -*gui.txt* For Vim version 9.1. Last change: 2025 Aug 10 |
| 1 | +*gui.txt* For Vim version 9.1. Last change: 2025 Oct 12 |
2 | 2 |
|
3 | 3 |
|
4 | 4 | VIM REFERENCE MANUAL by Bram Moolenaar |
@@ -164,7 +164,7 @@ window Vim is running in with these commands: > |
164 | 164 | *gui-IME* *iBus* |
165 | 165 | Input methods for international characters in X that rely on the XIM |
166 | 166 | framework, most notably iBus, have been known to produce undesirable results |
167 | | -in gvim. These may include an inability to enter spaces, or long delays |
| 167 | +in gvim. These may include an inability to enter spaces, or long delays |
168 | 168 | between typing a character and it being recognized by the application. |
169 | 169 |
|
170 | 170 | One workaround that has been successful, for unknown reasons, is to prevent |
@@ -574,8 +574,8 @@ the mouse button down on this will pop up a menu containing the item |
574 | 574 | which when selected, performs the operation. |
575 | 575 |
|
576 | 576 | To create a menu for terminal mode, use |:tlmenu| instead of |:tmenu| unlike |
577 | | -key mapping (|:tmap|). This is because |:tmenu| is already used for defining |
578 | | -tooltips for menus. See |terminal-typing|. |
| 577 | +key mapping (|:tmap|). This is because |:tmenu| is already used for defining |
| 578 | +tooltips for menus. See |terminal-typing|. |
579 | 579 |
|
580 | 580 | Special characters in a menu name: |
581 | 581 |
|
@@ -851,7 +851,7 @@ not wrap. |
851 | 851 |
|
852 | 852 | Note that Vim may be in any mode when executing these commands. The menu |
853 | 853 | should be defined for Normal mode and will be executed without changing the |
854 | | -current mode. Thus if the current window is in Visual mode and the menu |
| 854 | +current mode. Thus if the current window is in Visual mode and the menu |
855 | 855 | command does not intentionally change the mode, Vim will remain in Visual |
856 | 856 | mode. Best is to use `:nnoremenu` to avoid side effects. |
857 | 857 |
|
@@ -1019,8 +1019,8 @@ The tip is defined like this: > |
1019 | 1019 | And delete it with: > |
1020 | 1020 | :tunmenu MyMenu.Hello |
1021 | 1021 |
|
1022 | | -Tooltips are currently only supported for the X11 and Win32 GUI. However, they |
1023 | | -should appear for the other gui platforms in the not too distant future. |
| 1022 | +Tooltips are currently only supported for the X11 and Win32 GUI. However, |
| 1023 | +they should appear for the other gui platforms in the not too distant future. |
1024 | 1024 |
|
1025 | 1025 | The ":tmenu" command works just like other menu commands, it uses the same |
1026 | 1026 | arguments. ":tunmenu" deletes an existing menu tip, in the same way as the |
@@ -1158,12 +1158,12 @@ Examples: > |
1158 | 1158 |
|
1159 | 1159 | See also |font-sizes|. |
1160 | 1160 |
|
1161 | | -Note on Weights: Fonts often come with a variety of weights. "Normal" weights |
| 1161 | +Note on Weights: Fonts often come with a variety of weights. "Normal" weights |
1162 | 1162 | in Windows have a value of 400 and, left unspecified, this is the value that |
1163 | | -will be used when attempting to find fonts. Windows will often match fonts |
| 1163 | +will be used when attempting to find fonts. Windows will often match fonts |
1164 | 1164 | based on their weight with higher priority than the font name which means a |
1165 | 1165 | Book or Medium variant of a font might be used despite specifying a Light or |
1166 | | -ExtraLight variant. If you are experiencing heavier weight substitution, then |
| 1166 | +ExtraLight variant. If you are experiencing heavier weight substitution, then |
1167 | 1167 | explicitly setting a lower weight value may mitigate against this unwanted |
1168 | 1168 | substitution. |
1169 | 1169 |
|
|
0 commit comments