term.txt ForVim version 9.1. Last change: 2024 Dec 31VIM REFERENCE MANUAL by Bram MoolenaarTerminal informationterminal-infoVim uses information about theterminal you are using to fill the screen andrecognize what keys you hit. If this informationis not correct, the screenmay be messed up or keys may not be recognized. The actions which have to beperformed on the screen are accomplished by outputtingastring ofcharacters.Special keys produceastring of characters. These strings arestored in theterminal options, seeterminal-options.NOTE: Most of thisis not used when running theGUI.1. Startupstartup-terminal2. Terminaloptionsterminal-options3. Window sizewindow-size4. Slow and fast terminalsslow-fast-terminal5. Using the mousemouse-using==============================================================================1. Startupstartup-terminalWhen Vimis starteda defaultterminal typeis assumed. For theAmiga thisisa standard CLI window, forMS-Windows the pc terminal, forUnix an ansiterminal.A few otherterminal types are always available, see belowbuiltin-terms.You can give theterminal name with the '-T' Vim argument. Ifitis not givenVim will try to get the name from theTERM environment variable.termcapterminfoE557E558E559OnUnix theterminfo database ortermcap fileis used. Thisis referred toas"termcap" in all the documentation. At compile time, when running configure,the choice whether to useterminfo ortermcapis done automatically. Whenrunning Vim the output of ":version" will show+terminfo ifterminfoisused. Also seexterm-screens.On non-Unix systemsatermcapis only available if Vim was compiled withTERMCAP defined.builtin-termsbuiltin_termsA number of builtin terminals are available. Since patch 9.0.0280 thereis nodifference between Vim versions. You can seealist of available builtinterminals in the error message you get for `:set term=xxx` (when not runningthe GUI). Also see++builtin_terms.If thetermcap codeis included Vim will try to get the strings for theterminal you are using from thetermcap file and the builtin termcaps. Bothare always used, if an entry for theterminal you are usingis present. Whichoneis used first depends on the'ttybuiltin' option:'ttybuiltin' on1: builtintermcap2: externaltermcap'ttybuiltin' off1: externaltermcap2: builtintermcapIf an optionis missing in one of them,it will be obtained from the otherone. If an optionis present in both, the one first encounteredis used.Which externaltermcap fileis used varies from system to system and maydepend on the environmentvariables "TERMCAP" and "TERMPATH". See "mantgetent".Settings depending onterminalterm-dependent-settingsIf you want to setoptions or mappings, depending on theterminal name, youcando this best in your .vimrc. Example: if &term == "xterm" ... xterm maps and settings ... elseif &term =~ "vt10." ... vt100, vt102 maps and settings ... endifraw-terminal-modeFor normal editing theterminal will beput into "raw" mode. The stringsdefined with't_ti','t_TI' and't_ks' will be sent to the terminal. Normallythis puts theterminal ina state where thetermcap codes are valid andactivates the cursor and function keys.When Vim exits theterminal will beput back into the modeit was before Vimstarted. The strings defined with't_te','t_TE' and't_ke' will be sent tothe terminal. On the Amiga, with commands that execute an external command(e.g., "!!"), theterminal will beput intoNormal mode fora moment. Thismeans that you can stop the output to the screen by hittingaprinting key.Output resumes when you hit<BS>.Note: When't_ti'is not empty, Vim assumes thatit causes switching to thealternate screen. This may slightly change what happens when executingashell command orexiting Vim. To avoid this use't_TI' and't_TE' (but makesure to add to them, not overwrite).Vim will try to detect what keyboard protocol theterminalis using with the't_RK'termcap entry. Thisis sent after't_TI', but only when thereis nowork todo (no typeahead and no pending commands). Thatis to avoid theresponse toend up ina shell command or arrive after Vim exits.xterm-bracketed-pasteWhen the't_BE' optionis set then't_BE' will be sent to theterminal when entering "raw" mode and't_BD' when leaving "raw" mode. Theterminalis then expected toput't_PS' before pasted text and't_PE' afterpasted text. This way Vim can separate text thatis pasted from charactersthat are typed. The pasted textis handled like when the middle mouse buttonis used,itis inserted literally and not interpretedas commands.Pleasenote: while bracketed pasteis trying to prevent nasty side-effectsfrom pasting (like theCTRL-C or<ESC> key), it's nota guaranteed securitymeasure because different terminals may implement this mode slightlydifferently. You should still be careful with what you paste into Vim.When the cursoris in the first column, the pasted text will be insertedbefore it. Otherwise the pasted textis appended after the cursor position.This means one cannot paste after the first column. Unfortunately Vim doesnot havea way to tell where the mouse pointer was.Note that in some situations Vim will not recognize the bracketed paste andyou will get the raw text. In other situations Vim will only get the firstpasted character and drop the rest, e.g. when using the "r" command. If youhavea problem with this, disable bracketed paste by putting this in your.vimrc:set t_BE=If thisis done while Vimis running the't_BD' will be sent to theterminalto disable bracketed paste.Ift_PS ort_PEis not set, thent_BE will not be used. Thisis to makesure that bracketed pasteis not enabled when theescape codes surroundingpasted text cannot be recognized.Note: bracketed paste mode will be disabled, when the'esckeys' optionis notset (also when the'compatible' optionis set).If yourterminal supports bracketed paste, but theoptions are not setautomatically, you can try using something like this:if &term =~ "screen" let &t_BE = "\e[?2004h" let &t_BD = "\e[?2004l" exec "set t_PS=\e[200~" exec "set t_PE=\e[201~"endifTheterminfo entries "BE", "BD", "PS" and "PE" were added in ncurses version6.4, early 2023, for some terminals. If you have this version then you maynot have to manually configure your terminal.tmux-integrationIf you experience issues when running Vim inside tmux, here area few hints.You can comment-out parts if something doesn't work (it may depend on theterminal thattmuxis running in): if !has('gui_running') && &term =~ '^\%(screen\|tmux\)' " Better mouse support, see :help 'ttymouse' set ttymouse=sgr " Enable true colors, see :help xterm-true-color let &termguicolors = v:true let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum" let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum" " Enable bracketed paste mode, see :help xterm-bracketed-paste let &t_BE = "\<Esc>[?2004h" let &t_BD = "\<Esc>[?2004l" let &t_PS = "\<Esc>[200~" let &t_PE = "\<Esc>[201~" " Enable focus event tracking, see :help xterm-focus-event let &t_fe = "\<Esc>[?1004h" let &t_fd = "\<Esc>[?1004l"execute "set <FocusGained>=\<Esc>[I" execute "set <FocusLost>=\<Esc>[O" " Enable modified arrow keys, see :help arrow_modifiers execute "silent! set <xUp>=\<Esc>[@;*A" execute "silent! set <xDown>=\<Esc>[@;*B" execute "silent! set <xRight>=\<Esc>[@;*C" execute "silent! set <xLeft>=\<Esc>[@;*D" endifcs7-problemNote: If theterminal settings are changed after running Vim, you might havean illegal combination of settings. This has been reported on Solaris 2.5with "stty cs8 parenb", whichis restoredas "stty cs7 parenb". Use"stty cs8 -parenb -istrip" instead, thisis restored correctly.Sometermcap entries are wrong in the sense that after sending't_ks' thecursor keys send codes different from the codes defined in the termcap. Toavoid this you can set't_ks' (and't_ke') to empty strings. Thismust bedone duringinitialization (seeinitialization), otherwise it's too late.Sometermcap entries assume that the highest bitis always reset. Forexample: Thecursor-up entry for theAmiga could be ":ku=\E[A:". But theAmiga really sends "\233A". This works fine if the highest bitis reset,e.g., when using anAmiga overa serial line. If the cursor keys don't work,try the entry ":ku=\233A:".Sometermcap entries have the entry ":ku=\E[A:". But theAmiga really sends"\233A". On output "\E[" and "\233" are often equivalent, on input theyaren't. You will have to change thetermcap entry, or change the key code withthe:set command to fix this.Many cursor key codes start with an<Esc>. Vimmust find out if thisisasingle hit of the<Esc> key or the start ofa cursor key sequence. It waitsfora next character to arrive. Ifit does not arrive within one secondasingle<Esc>is assumed. On very slow systems this may fail, causing cursorkeys not to work sometimes. If you discover this problem reset the'timeout'option. Vim will wait for the next character to arrive after an<Esc>. Ifyou want to entera single<Esc> youmust typeit twice. Resetting the'esckeys' option avoids this problem inInsert mode, but you lose thepossibility to use cursor and function keys inInsert mode.On theAmiga the recognition ofwindow resizingis activated only when theterminal nameis "amiga" or "builtin_amiga".Some terminals have confusing codes for the cursor keys. The televideo 925issucha terminal. It sendsaCTRL-H for cursor-left. This would makeitimpossible to distinguishabackspace and cursor-left. To avoid this problemCTRL-His never recognizedas cursor-left.vt100-cursor-keysxterm-cursor-keysOther terminals (e.g., vt100 and xterm) have cursor keys that send<Esc>OA,<Esc>OB, etc. Unfortunately these are valid commands ininsert mode: Stopinsert, Opena new line above the new one, startinserting 'A', 'B', etc.Instead of performing these commands Vim will erroneously recognize this typedkey sequenceasa cursor key movement. To avoid this and make Vimdo what youwant in eithercase you could use these settings::set notimeout" don't timeout on mappings:set ttimeout" do timeout on terminal key codes:set timeoutlen=100" timeout after 100 msecThis requires thekey-codes to be sent within 100 msec in order to recognizethemasa cursor key. When you type you normally are not that fast, so theyare recognizedas individual typed commands, even though Vim receives the samesequence of bytes.vt100-function-keysxterm-function-keysAn xterm can send function keys F1 to F4 in two modes: vt100 compatible ornot. Because Vim may not know what the xtermis sending, both types of keysare recognized. The same happens for the<Home> and<End> keys.normalvt100<F1>t_k1<Esc>[11~<xF1><Esc>OP<xF1>-xterm<F2>t_k2<Esc>[12~<xF2><Esc>OQ<xF2>-xterm<F3>t_k3<Esc>[13~<xF3><Esc>OR<xF3>-xterm<F4>t_k4<Esc>[14~<xF4><Esc>OS<xF4>-xterm<Home>t_kh<Esc>[7~<xHome><Esc>OH<xHome>-xterm<End>t_@7<Esc>[4~<xEnd><Esc>OF<xEnd>-xtermWhen Vim starts,<xF1>is mapped to<F1>,<xF2> to<F2> etc. This means thatby default both codesdo the same thing. If you makeamapping for<xF2>,because yourterminal does have two keys, the defaultmappingis overwritten,thus you can use the<F2> and<xF2> keys for something different.xterm-shifted-keysNewer versions of xterm support shifted function keys and special keys. Vimrecognizes most of them. Use ":settermcap" to check which are supported andwhat the codes are. Mostly these are not ina termcap, they are onlysupported by the builtin_xterm termcap.xterm-modifier-keysNewer versions of xterm support Alt and Ctrl for most function keys. To avoidhaving to add all combinations of Alt, Ctrl and Shift for every keya specialsequenceis recognizedat theend ofatermcap entry: ";*X". The "X" can beany character, often '~'is used. The ";*" stands for an optional modifierargument. ";2"is Shift, ";3"is Alt, ";5"is Ctrl and ";9"is Meta (whenit's different from Alt). They can be combined. Examples::set <F8>=^[[19;*~:set <Home>=^[[1;*HAnother speciality about these codesis that they are not overwritten byanother code. Thatis to avoid that the codes obtained from xterm directlyt_RV overwrite them.Another special valueisatermcap entry ending in "@;*X". Thisis for cursorkeys, which either use "CSIX" or "CSI 1; modifierX". Thus the "@"stands for either "1" ifa modifier follows, or nothing.arrow_modifiersSeveralterminal emulators (alacritty, gnome, konsole, etc.) send specialcodes for keys with modifiers, but thesedo not have an entry in thetermcap/terminfo database. You can make them work by addinga few lines inyour vimrc. For example, to make the Control modifier work with arrow keysfor the gnome terminal:if &term =~ 'gnome' execute "set <xUp>=\<Esc>[@;*A" execute "set <xDown>=\<Esc>[@;*B" execute "set <xRight>=\<Esc>[@;*C" execute "set <xLeft>=\<Esc>[@;*D"endifxterm-scroll-regionThe defaulttermcap entry for xterm on Sun and other platforms does notcontain the entry for scroll regions. Add ":cs=\E[%i%d;%dr:" to the xtermentry in /etc/termcap and everything should work.xterm-end-home-keysOn some systems (at least on FreeBSD with XFree86 3.1.2) the codes that the<End> and<Home> keys send containa<Nul> character. To make these keys sendthe proper key code, add these lines to your ~/.Xdefaults file:*VT100.Translations:#override \n\<Key>Home: string("0x1b") string("[7~") \n\<Key>End: string("0x1b") string("[8~")xterm-8bitxterm-8-bitXterm can be run ina mode whereit uses 8-bitescape sequences. The CSI codeis used instead of<Esc>[. The advantageis that an<Esc> can quickly berecognized inInsert mode, becauseit can't be confused with the start ofaspecial key.For the builtintermcap entries, Vim checks if the'term' option contains"8bit" anywhere. It then uses 8-bit characters for thetermcap entries, themouse anda few other things. You would normally set $TERM in your shell to"xterm-8bit" and Vim picks this up and adjusts to the 8-bit settingautomatically.When Vim receivesa response to thet_RV (request version) sequence anditstarts with CSI,it assumes that theterminalis in 8-bit mode and willconvert all key sequences to their 8-bit variants.xterm-terminfo-entriesFor some time theterminfo entries were insufficient to describe all thefeatures that Vim can use. The builtin xtermtermcap entries did have these,with the result that several terminals that were similar enough to xterm tookadvantage of these by prefixing "xterm-" to theterminal name in $TERM.This leads to problems, because quite often these terminals are not 100%compatible with xterm. At the start of 2023 several entries have been addedto theterminfo database to makeit possible to use these features withoutusing the "xterm" workaround. These are the relevant entries (so far):namexterm valuedescriptionRV"\033[>c"Request versiont_RVBE"\033[?2004h"enable bracketed paste modet_BEBD"\033[?2004l"disable bracketed paste modet_BDPS"\033[200~"pasted text startt_PSPE"\033[201~"pasted textendt_PEXM"\033[?1006;1004;1000%?%p1%{1}%=%th%el%;"mouse enable/ disablet_XMFE"\033[?1004h"enable focus event trackingt_feFD"\033[?1004l"disable focus event trackingt_fdThe "XM" entry includes "1006" to enable SGR style mouse reporting. Thissupports columns above 223. It also includes "1004" which enables focusreporting.Note: As of 2023, the "1004"is currently not used by Vim itself, insteaditis recommended to set focus reporting independently of mouse tracking bythet_fe andt_fd entries,as ncurses also starts to use with the latestversions (and will then alsoend up in terminfo/termcap).xterm-kittykitty-terminalThe Kittyterminalisa special case. Mainly becauseit works differentlyfrom most other terminals, but also because, instead of trying to fit in andmakeit behave like other terminals by default,it dictates how applicationsneed to work when using Kitty. This makesit very difficult for Vim to workina Kitty terminal. Some exceptions have been hard coded, butitis notatall nice to have to make exceptions for one specific terminal.One of the problemsis that the value for $TERMis set to "xterm-kitty". ForVim thisis an indication that theterminalis xterm-compatible and thebuiltin xtermtermcap entries should be used. Many other terminals depend onthis. However, Kittyis not fully xterm compatible. Theauthor suggested toignore the "xterm-" prefix and use theterminfo entry anyway, so thatis whathappens now, the builtin xtermtermcap entries are not used. However, thet_RVis set, otherwise other things would not work, suchas automaticallysetting'ttymouse' to "sgr" (at least untilt_XMis being used for this).Itis not clear why kitty sets $TERM to "xterm-kitty", theterminal isn'treally xterm compatible. "kitty" would be more appropriate, butaterminfoentry with that nameis not widespread.Note that using the kitty keyboard protocolisa separate feature, seekitty-keyboard-protocol.==============================================================================2. Terminaloptionsterminal-optionstermcap-optionsE436Theterminaloptions can be set just like normal options. But they are notshown with the ":set all" command. Instead use ":settermcap".Itis always possible to change individual strings by setting theappropriate option. For example::set t_ce=^V^[[K(CTRL-V, <Esc>, [, K)Theoptions are listed below. The associatedtermcap codeis always equal tothe last two characters of the option name. Only onetermcap codeisrequired: Cursor motion,'t_cm'.Theoptions't_da','t_db','t_ms','t_xs','t_xn','t_xo' represent flags inthe termcap. When thetermcap flagis present, the option will be set to "y".But any non-emptystring means that the flagis set. An emptystring meansthat the flagis not set.'t_CS' works like this too, butit isn'tatermcapflag.OUTPUT CODESterminal-output-codesoptionmeaningt_ABset background color (ANSI)t_AB't_AB't_AFset foreground color (ANSI)t_AF't_AF't_ALadd number of blank linest_AL't_AL't_aladd new blank linet_al't_al't_bcbackspace charactert_bc't_bc't_cdclear toend of screent_cd't_cd't_ceclear toend of linet_ce't_ce't_clclear screent_cl't_cl't_cmcursor motion (required!)E437t_cm't_cm't_Conumber of colorst_Co't_Co't_CSif non-empty, cursor relative to scroll regiont_CS't_CS't_csdefinescrolling regiont_cs't_cs't_CVdefine verticalscrolling regiont_CV't_CV't_daif non-empty, lines from above scroll downt_da't_da't_dbif non-empty, lines from below scroll upt_db't_db't_DLdelete number of linest_DL't_DL't_dldelete linet_dl't_dl't_fssetwindow titleend (from status line)t_fs't_fs't_keexit "keypad transmit" modet_ke't_ke't_ksstart "keypad transmit" modet_ks't_ks't_lemove cursor one char leftt_le't_le't_mbblinking modet_mb't_mb't_mdbold modet_md't_md't_meNormal mode (undoes t_mr, t_mb,t_md and color)t_me't_me't_mrreverse (invert) modet_mr't_mr't_ms't_ms't_msif non-empty, cursor can be moved in standout/inverse modet_ndnon destructivespace charactert_nd't_nd't_opreset to original color pairt_op't_op't_RIcursor number of chars rightt_RI't_RI't_Sbset background colort_Sb't_Sb't_Sfset foreground colort_Sf't_Sf't_sestandoutendt_se't_se't_sostandout modet_so't_so't_srscroll reverse (backward)t_sr't_sr't_teend of "termcap" modet_te't_te't_tiputterminal into "termcap" modet_ti't_ti't_tssetwindow title start (to status line)t_ts't_ts't_ueunderlineendt_ue't_ue't_usunderline modet_us't_us't_utclearing uses the current background colort_ut't_ut't_vbvisual bellt_vb't_vb't_vecursor visiblet_ve't_ve't_vicursor invisiblet_vi't_vi't_vscursor very visible (blink)t_vs't_vs't_xs't_xs't_xsif non-empty,standout not erased by overwriting (hpterm)t_xn't_xn't_xnif non-empty,writinga characterat the last screen celldoes not causescrollingt_xo't_xo't_xoif non-empty,terminal uses xon/xoff handshaking,mappingCTRL-S will not be possible then, sinceitis used for flowcontrol (used by vt420 terminal). Setting this flag has onlyan effect whenstarting Vim.t_ZHitalics modet_ZH't_ZH't_ZRitalicsendt_ZR't_ZR'Added by Vim (there are no standard codes for these):t_AUsetunderline color (ANSI)t_AU't_AU't_Ceundercurl andunderlineendt_Ce't_Ce't_Csundercurl (curly underline) modet_Cs't_Cs't_CFset alternate font (usingindex0- 10)t_CF't_CF't_Usdoubleunderline modet_Us't_Us't_dsdottedunderline modet_ds't_ds't_Dsdashedunderline modet_Ds't_Ds't_Testrikethroughendt_Te't_Te't_Tsstrikethrough modet_Ts't_Ts't_ISset icon text startt_IS't_IS't_IEset icon textendt_IE't_IE't_WPsetwindow position (Y, X) in pixelst_WP't_WP't_GPgetwindow position (Y, X) in pixelst_GP't_GP't_WSsetwindow size (height, width in cells)t_WS't_WS't_VScursor normally visible (no blink)t_VS't_VS't_SIstartinsert mode (bar cursor shape)t_SI't_SI't_SRstart replace mode (underline cursor shape)t_SR't_SR't_EIendinsert or replace mode (block cursor shape)t_EI't_EI'termcap-cursor-shapet_RVrequestterminal versionstring (works fort_RV't_RV'xterm and otherterminal emulators) Theresponseis stored inv:termresponsexterm-8bit'ttymouse'xterm-codest_XMenable/disable mouse reporting,t_XM't_XM'seemouse-reporting belowt_RKrequestterminal keyboard protocol state;t_RK't_RK'sent aftert_TIt_u7request cursor position (for xterm)t_u7't_u7'see'ambiwidth'The responseis stored inv:termu7respt_RFrequestterminal foreground colort_RF't_RF'The responseis stored inv:termrfgrespt_RBrequestterminal background colort_RB't_RB'The responseis stored inv:termrbgrespt_8fset foreground color (R, G, B)t_8f't_8f'xterm-true-colort_8bset background color (R, G, B)t_8b't_8b'xterm-true-colort_8usetunderline color (R, G, B)t_8u't_8u't_BEenable bracketed paste modet_BE't_BE'xterm-bracketed-pastet_BDdisable bracketed paste modet_BD't_BD'xterm-bracketed-pastet_SCset cursor color startt_SC't_SC't_ECset cursor colorendt_EC't_EC't_SHset cursor shapet_SH't_SH't_RCrequestterminal cursor blinkingt_RC't_RC'The responseis stored inv:termblinkrespt_RSrequestterminal cursor stylet_RS't_RS'The responseis stored inv:termstylerespt_STsavewindow title to stackt_ST't_ST't_RTrestorewindow title from stackt_RT't_RT't_Sisave icon text to stackt_Si't_Si't_Rirestore icon text from stackt_Ri't_Ri't_TEend of "raw" modet_TE't_TE't_TIputterminal into "raw" modet_TI't_TI't_feenable focus-event trackingt_fe't_fe'xterm-focus-eventt_fddisable focus-event trackingt_fd't_fd'xterm-focus-eventSome codes havea start, middle andend part. The start andend are definedby thetermcap option, the middle partis text.set title text:t_ts{title text}t_fsset icon text:t_IS{icon text}t_IEset cursor color:t_SC{color name}t_ECt_SHmust take one argument:0, 1 or noneblinking block cursor2block cursor3blinkingunderline cursor4underline cursor5blinking verticalbar cursor6verticalbar cursort_RSis sent only if the response tot_RV has been received. Itis not usedonMac OS when Terminal.app could be recognized from the termresponse.mouse-reportingMany terminals can report mouse clicks and some can report mousemovement anddragging. Vim needs to know what codes are being used for this.The "XM" terminfo/termcap entryis used for this. Vim also has the'ttymouse'option to specify the mouse protocol being used. See the option for thepossible values.If Vim can read the "XM" terminfo/termcap entry thenit will be used forenabling and disabling the mouse reporting. Ifitis missing, then the valuefrom'ttymouse'is used to decide how todo this.If the "XM" entry exists and the first numberis "1006" then'ttymouse' willbe set to "sgr", unlessit was already set earlier.KEY CODESterminal-key-codesNote: Use the<> form if possibleoptionnamemeaningt_ku<Up>arrow upt_ku't_ku't_kd<Down>arrow downt_kd't_kd't_kr<Right>arrow rightt_kr't_kr't_kl<Left>arrow leftt_kl't_kl'<xUp>alternate arrow up<xUp><xDown>alternate arrow down<xDown><xRight>alternate arrow right<xRight><xLeft>alternate arrow left<xLeft><S-Up>shift arrow up<S-Down>shift arrow downt_%i<S-Right>shift arrow rightt_%i't_%i't_#4<S-Left>shift arrow leftt_#4't_#4't_k1<F1>function key 1t_k1't_k1'<xF1>alternate F1<xF1>t_k2<F2>function key 2<F2>t_k2't_k2'<xF2>alternate F2<xF2>t_k3<F3>function key 3<F3>t_k3't_k3'<xF3>alternate F3<xF3>t_k4<F4>function key 4<F4>t_k4't_k4'<xF4>alternate F4<xF4>t_k5<F5>function key 5<F5>t_k5't_k5't_k6<F6>function key 6<F6>t_k6't_k6't_k7<F7>function key 7<F7>t_k7't_k7't_k8<F8>function key 8<F8>t_k8't_k8't_k9<F9>function key 9<F9>t_k9't_k9't_k;<F10>function key 10<F10>t_k;'t_k;'t_F1<F11>function key 11<F11>t_F1't_F1't_F2<F12>function key 12<F12>t_F2't_F2't_F3<F13>function key 13<F13>t_F3't_F3't_F4<F14>function key 14<F14>t_F4't_F4't_F5<F15>function key 15<F15>t_F5't_F5't_F6<F16>function key 16<F16>t_F6't_F6't_F7<F17>function key 17<F17>t_F7't_F7't_F8<F18>function key 18<F18>t_F8't_F8't_F9<F19>function key 19<F19>t_F9't_F9'<S-F1>shifted function key 1<S-xF1>alternate<S-F1><S-xF1><S-F2>shifted function key 2<S-F2><S-xF2>alternate<S-F2><S-xF2><S-F3>shifted function key 3<S-F3><S-xF3>alternate<S-F3><S-xF3><S-F4>shifted function key 4<S-F4><S-xF4>alternate<S-F4><S-xF4><S-F5>shifted function key 5<S-F5><S-F6>shifted function key 6<S-F6><S-F7>shifted function key 7<S-F7><S-F8>shifted function key 8<S-F8><S-F9>shifted function key 9<S-F9><S-F10>shifted function key 10<S-F10><S-F11>shifted function key 11<S-F11><S-F12>shifted function key 12<S-F12>t_%1<Help>help keyt_%1't_%1't_&8<Undo>undo keyt_&8't_&8't_kI<Insert>insert keyt_kI't_kI'<kInsert>keypadinsert keyt_kD<Del>delete keyt_kD't_kD't_kb<BS>backspace keyt_kb't_kb't_kB<S-Tab>back-tab (shift-tab)<S-Tab>t_kB't_kB't_kh<Home>home keyt_kh't_kh't_#2<S-Home>shiftedhome key<S-Home>t_#2't_#2'<xHome>alternatehome key<xHome>t_@7<End>end keyt_@7't_@7't_*7<S-End>shiftedend key<S-End>t_star7't_star7'<xEnd>alternateend key<xEnd>t_kP<PageUp>page-up keyt_kP't_kP't_kN<PageDown>page-down keyt_kN't_kN't_K1<kHome>keypadhome keyt_K1't_K1't_K4<kEnd>keypadend keyt_K4't_K4't_K3<kPageUp>keypadpage-up keyt_K3't_K3't_K5<kPageDown>keypadpage-down keyt_K5't_K5't_K6<kPlus>keypad plus key<kPlus>t_K6't_K6't_K7<kMinus>keypad minus key<kMinus>t_K7't_K7't_K8<kDivide>keypad divide<kDivide>t_K8't_K8't_K9<kMultiply>keypad multiply<kMultiply>t_K9't_K9't_KA<kEnter>keypad enter key<kEnter>t_KA't_KA't_KB<kPoint>keypad decimal point<kPoint>t_KB't_KB't_KC<k0>keypad0<k0>t_KC't_KC't_KD<k1>keypad 1<k1>t_KD't_KD't_KE<k2>keypad 2<k2>t_KE't_KE't_KF<k3>keypad 3<k3>t_KF't_KF't_KG<k4>keypad 4<k4>t_KG't_KG't_KH<k5>keypad 5<k5>t_KH't_KH't_KI<k6>keypad 6<k6>t_KI't_KI't_KJ<k7>keypad 7<k7>t_KJ't_KJ't_KK<k8>keypad 8<k8>t_KK't_KK't_KL<k9>keypad 9<k9>t_KL't_KL'<Mouse>leader of mouse code<Mouse>t_PS<PasteStart>start of bracketed pastet_PS't_PS'xterm-bracketed-pastet_PE<PasteEnd>end of bracketed pastet_PE't_PE'xterm-bracketed-paste<FocusGained>Vimwindow got focus (internal only)<FocusLost>Vimwindow lost focus (internal only)Note aboutt_so and t_mr: When thetermcap entry "so"is not present theentry for "mr"is used. And vice versa. The sameis done for "se" and "me".If yourterminal supports both inversion andstandout mode, you can see twodifferent modes. If yourterminal supports only one of the modes, both willlook the same.keypad-commaThe keypad keys, when they are not mapped, behave like the equivalent normalkey. Thereis one exception: if you havea comma on the keypad instead ofadecimal point, Vim will usea dot anyway. Use these mappings to fix that::noremap <kPoint> ,:noremap! <kPoint> ,xterm-codesThereisa special trick to obtain the key codes which currently only worksfor xterm. Whent_RVis defined anda responseis received which indicatesan xterm with patchlevel 141 or higher, Vim uses specialescape sequences torequest the key codes directly from the xterm. The responses are used toadjust thevarious t_ codes. This avoids the problem that the xterm canproduce different codes, depending on the modeitis in (8-bit, VT102,VT220, etc.). The resultis that codes like<xF1> are no longer needed.One of the codes that can changeis't_Co', the number of colors. This willtriggera redraw. If thisisa problem, reset the'xtermcodes' optionasearlyas possible:set noxtermcodesNote: Requesting the key codesis only done on startup. If the xtermoptionsare changed after Vim has started, theescape sequences may not be recognizedanymore.xterm-true-colorVim supports usingtrue colors in theterminal (taken fromhighlight-guifgandhighlight-guibg), given that theterminal supports this. To make thiswork the'termguicolors' option needs to be set.Seehttps://github.com/termstandard/colors foralist of terminals thatsupporttrue colors.For telling theterminal what RGB color to use thet_8f andt_8btermcapentries are used. These are set by default to values that work for mostterminals. If that does not work for yourterminal you can set them manually.The default values are set like this: let &t_8f = "\<Esc>[38;2;%lu;%lu;%lum" let &t_8b = "\<Esc>[48;2;%lu;%lu;%lum"Some terminals accept similar sequences, with semicolons replaced by colonsand an extra colon after the number 2 (thisis conformant to the ISO 8613-6standard, butless widely supported): let &t_8f = "\<Esc>[38:2::%lu:%lu:%lum" let &t_8b = "\<Esc>[48:2::%lu:%lu:%lum"Theseoptions contain printf strings, withprintf() (actually, itsCequivalent hencel modifier) invoked with the t_ option value and threeunsigned long integers that may have any value between0 and 255 (inclusive)representing red, green and blue colors respectively.xterm-resizeWindow resizing with xterm only works if the allowWindowOps resourceisenabled. On some systems and versions of xterm it's disabled by defaultbecause someone thoughtit would bea security issue. It's not clear if thisis actually the case.To overrule the default,put this line in your ~/.Xdefaults or~/.Xresources:XTerm*allowWindowOps:trueAnd run "xrdb -merge .Xresources" to makeit effective. You can check thevalue with the context menu (right mouse button while CTRL keyis pressed),there should bea tickat allow-window-ops.xterm-focus-eventSome terminals including xterm support the focus event tracking feature.If this featureis enabled by the't_fe' sequence, special key sequences aresent from theterminal to Vim every time theterminal gains or loses focus.Vim fires focus events(FocusGained/FocusLost) by handling them accordingly.Focus event trackingis disabled bya't_fd' sequence whenexiting "raw" mode.If you would like to disable this feature, add the following to your .vimrc:set t_fd=set t_fe=If yourterminal does support this but Vim does not recognize the terminal,you may have to set theoptions yourself:let &t_fe = "\<Esc>[?1004h"let &t_fd = "\<Esc>[?1004l"execute "set <FocusGained>=\<Esc>[I" execute "set <FocusLost>=\<Esc>[O"If this causes garbage to show when Vim starts up thenit doesn't work.termcap-colorsNote about colors: The't_Co' option tells Vim the number of colors available.Whenitis non-zero, the't_AB' and't_AF'options are used to set the color.If one of theseis not available,'t_Sb' and't_Sf' are used.'t_me'is usedto reset to the default colors. Also see'termguicolors'.When theGUIis running't_Co'is set to 16777216.termcap-cursor-shapetermcap-cursor-colorWhen Vim entersInsert mode the't_SI'escape sequenceis sent. When VimentersReplace mode the't_SR'escape sequenceis sent ifitis set, otherwise't_SI'is sent. When leavingInsert mode orReplace mode't_EI'is used.Note: When't_EI'is not set then't_SI' and't_SR' will not be sent. Andwhen't_SI' or't_SR'is not set then't_EI'is sent only once.This can be used to change the shape or color of the cursor inInsert orReplace mode. These are not standard termcap/terminfo entries, you need to setthem yourself.Example for an xterm, this changes the color of the cursor: if &term =~ "xterm"let &t_SI = "\<Esc>]12;purple\x7"let &t_SR = "\<Esc>]12;red\x7"let &t_EI = "\<Esc>]12;blue\x7" endifNOTE: When Vim exits the shape forNormal mode will remain. The shape frombefore Vim started will not be restored.For Windows Terminal you can use something like this: " Note: This should be set after `set termguicolors` or `set t_Co=256`. if &term =~ 'xterm' || &term == 'win32'" Use DECSCUSR escape sequenceslet &t_SI = "\e[5 q" " blink barlet &t_SR = "\e[3 q" " blink underlinelet &t_EI = "\e[1 q" " blink blocklet &t_ti ..= "\e[1 q" " blink blocklet &t_te ..= "\e[0 q" " default (depends on terminal, normally blink" block) endif{not available when compiled without the |+cursorshape| feature}termcap-titleThe't_ts' and't_fs'options are used to set thewindow title if theterminalallows title setting via sending strings. They are sent before and after thetitle string, respectively. Similar't_IS' and't_IE' are used to set theicon text. These are Vim-internal extensions of theUnix termcap, so theycannot be obtained from an external termcap. However, the builtintermcapcontains suitable entries for xterm and iris-ansi, so you don't need to setthem here.hptermIf inversion or other highlighting does not work correctly, try setting the't_xs' option toa non-empty string. This makes the't_ce' code be used toremove highlighting froma line. Thisis required for "hpterm". Setting the'weirdinvert' option has the same effectas making't_xs' non-empty, and viceversa.scroll-regionSome termcapsdo not include an entry for "cs" (scroll region), although theterminal does support it. For example: xterm ona Sun. You can use thebuiltin_xterm or definet_cs yourself. For example::set t_cs=^V^[[%i%d;%drWhere ^VisCTRL-V and ^[is<Esc>.The vertical scroll regiont_CVis nota standardtermcap code. Vim usesitinternally in the GUI. Butit can also be defined fora terminal, if you canfind one that supports it. The two arguments are the left and right column ofthe region which to restrict thescrolling to. Just liket_cs defines the topand bottom lines. Definingt_CV will makescrolling in vertically splitwindowsa lot faster. Don't sett_CV whent_da ort_dbis set (text isn'tcleared when scrolling).Unfortunatelyitis not possible to deduce from thetermcap how cursorpositioning should be done when usingascrolling region: Relative to thebeginning of the screen or relative to the beginning of thescrolling region.Most terminals use the first method. The't_CS' option should be set to anystring when cursor positioningis relative to the start of thescrollingregion. It should be set to an emptystring otherwise.Note for xterm users: The shifted cursor keys normally don't work. You canmake them work with the xmodmap command and some mappings in Vim.Give these commands in the xterm:xmodmap -e "keysym Up = Up F13"xmodmap -e "keysym Down = Down F16"xmodmap -e "keysym Left = Left F18"xmodmap -e "keysym Right = Right F19"And use these mappings in Vim::map <t_F3> <S-Up>:map! <t_F3> <S-Up>:map <t_F6> <S-Down>:map! <t_F6> <S-Down>:map <t_F8> <S-Left>:map! <t_F8> <S-Left>:map <t_F9> <S-Right>:map! <t_F9> <S-Right>Instead of, say,<S-Up> you can use any other command that you want to use theshift-cursor-up key for. (Note: Tohelp people that havea Sun keyboard withleft side keys F14is not used becauseitis confused with theundo key; F15is not used, becauseit doesa window-to-front; F17is not used, becauseitcloses the window. On other systems you can probably use them.)==============================================================================3. Window sizewindow-size[Thisis about the size of the wholewindow Vimis using, notawindow thatiscreated with the ":split" command.]If you are running Vim on anAmiga and theterminal nameis "amiga" or"builtin_amiga", the amiga-specificwindow resizing will be enabled. OnUnixsystems three methods are tried to get thewindow size:- an ioctl call (TIOCGSIZE or TIOCGWINSZ, depends on your system)- the environmentvariables "LINES" and "COLUMNS"- from thetermcap entries "li" and "co"If everything failsa default size of 24 lines and 80 columnsis assumed. Ifawindow-resize signalis received the size will be set again. If thewindowsizeis wrong you can use the'lines' and'columns'options to set thecorrect values.One command can be used to set the screen size::mod:modeE359:mod[e][mode]Without argument this only detects the screen size and redraws the screen.[mode] was used on MS-DOS, butit doesn't work anymore. InVim9 thiscommandis not supported.==============================================================================4. Slow and fast terminalsslow-fast-terminalslow-terminalIf you havea fastterminal you may like to set the'ruler' option. Thecursor positionis shown in the status line. If you are using horizontalscrolling ('wrap' option off) consider setting'sidescroll' toa smallnumber.If you havea slowterminal you may want to reset the'showcmd' option.The command characters will not be shown in the status line. If theterminalscrolls very slowly, set the'scrolljump' to 5 or so. If the cursoris movedoff the screen (e.g., with "j") Vim will scroll 5 linesata time. Anotherpossibilityis to reduce the number of lines that Vim uses with the command"z{height}<CR>".If the characters from theterminal are arriving with more than 1 secondbetween them you might want to set the'timeout' and/or'ttimeout' option.See the "Options" chapteroptions.If yourterminal does not supportascrolling region, butit does supportinsert/delete line commands,scrolling with multiplewindows may make thelines jump up and down. This would happen if the'ttyfast' option has beenreset. Check that with:verbose set ttyfast?If yourterminal scrolls very slowly, but redrawingis not slow, set the'ttyscroll' option toa small number, e.g., 3. This will make Vim redraw thescreen instead of scrolling, when there are more than 3 lines to be scrolled.If you are usinga colorterminal thatis slow, use this command:hi NonText cterm=NONE ctermfg=NONEThis avoids that spaces are sent when they have different attributes. On mostterminals you can't see this anyway.If you are using Vim overa slow serial line, you might want to try runningVim inside the "screen" program. Screen will optimize theterminal I/O quitea bit.If you aretestingtermcap options, but you cannot see whatis happening, youmight want to set the'writedelay' option. When non-zero, one characterissent to theterminalata time. This makes the screen updatinga lot slower,makingit possible to see whatis happening.==============================================================================5. Using the mousemouse-usingThissectionis about using the mouse onaterminal oraterminal window. Howto use the mouse inaGUIwindowis explained ingui-mouse. Forscrollingwitha mouse wheel seescroll-mouse-wheel.Don't forget to enable the mouse with this command::set mouse=aOtherwise Vim won't recognize the mouse in all modes (See'mouse').Currently the mouseis supported forUnix in an xterm window, ina *BSDconsole withsysmouse, ina Linux console (with GPMgpm-mouse), andina Windows console.Mouse clicks can be used to position the cursor, select an area and paste.These characters in the'mouse' option tell in which situations the mouse willbe used by Vim:nNormal modevVisual modeiInsert modecCommand-line modehall previous modes when inahelp fileaall previous modesrforhit-enter promptThe default for'mouse'is empty, the mouseis not used. Normally you woulddo::set mouse=ato start using the mouse (thisis equivalent to setting'mouse' to "nvich").If you only want to use the mouse ina few modes or also want to useit forthe two questions you will have to concatenate the letters for those modes.For example::set mouse=nvWill make the mouse work inNormal mode andVisual mode.:set mouse=hWill make the mouse work inhelp files only (so you can use "g<LeftMouse>" tojump to tags).Whether the selection thatis started with the mouseis inVisual mode orSelect mode depends on whether "mouse"is included in the'selectmode'option.terminal-mouseIn an xterm, with the currently active mode included in the'mouse' option,normal mouse clicks are used by Vim, mouse clicks with theshift orctrl keypressedgo to the xterm. With the currently active mode not included in'mouse' all mouse clicksgo to the xterm.For terminals whereitis not possible to have the mouse events be used by theterminal itself by usinga modifier,a workaroundis to not use mouse eventsfor Vim in command-line mode::set mouse=nviThen to select text with the terminal, use ":" togo to command-line mode,select and copy the text to the system, then press Esc.Another wayis to temporarily use ":sh" to runa shell, copy the text, thenexit the shell.'mouse' can remain set to "a" then.xterm-clipboardIn theMotifGUI version, when running inaterminal and thereisaccess to the X-server (DISPLAYis set), the copy and paste will behave likein the GUI. If not, the middle mouse button willinsert the unnamed register.In that case, hereis how you copy and pastea piece of text:Copy/paste with the mouse andVisual mode ('mouse' optionmust be set, seeabove):1. Press left mouse button on firstletter of text, move mouse pointer to lastletter of the text and release the button. This will startVisual mode and highlight the selected area.2. Press "y" toyank theVisual text in the unnamed register.3. Click the left mouse buttonat theinsert position.4. Click the middle mouse button.Shortcut: If theinsert positionis on the screenat the same timeas theVisual text, you cando 2, 3 and 4 all in one: Click the middle mouse buttonat theinsert position.Note: When the-X command line argumentis used, Vim will not connect to theX server and copy/paste to theXclipboard (selection) will not work. Use theshift key with the mouse buttons to let the xtermdo the selection.xterm-command-serverWhen the X-serverclipboardis available, the command server described inx11-clientserver can be enabled with the--servername command line argument.xterm-copy-pasteNOTE: In some (older) xterms, it's not possible to move the cursor past column95 or 223. Thisis an xterm problem, not Vim's. Geta newer xtermcolor-xterm. Also see'ttymouse'.Copy/paste in xterm with (current mode NOT included in'mouse'):1. Press left mouse button on firstletter of text, move mouse pointer to lastletter of the text and release the button.2. Use normal Vim commands toput the cursorat theinsert position.3. Press "a" to startInsert mode.4. Click the middle mouse button.5. Press ESC toendInsert mode.(The same can be done with anything in'mouse' if you keep theshift keypressed while using the mouse.)Note: if you lose the 8th bit when pasting (special characters are translatedinto other characters), you may have todo "stty cs8 -istrip -parenb" in yourshell beforestarting Vim.Thus in an xterm theshift andctrl keys cannot be used with the mouse. Mousecommands requiring the CTRL modifier can be simulated by typing the "g" keybefore using the mouse:"g<LeftMouse>"is "<C-LeftMouse>(jump totag under mouse click)"g<RightMouse>"is "<C-RightMouse>("CTRL-T")mouse-mode-tablemouse-overviewA short overview of what the mouse buttons do, when'mousemodel'is "extend":Normal Mode:event position selection change action cursor window<LeftMouse> yesend yes<C-LeftMouse> yesend yes "CTRL-]" (2)<S-LeftMouse> yes no change yes "*" (2)<S-LeftMouse><LeftDrag> yesstart or extend (1) no<LeftDrag><LeftRelease> yesstart or extend (1) no<MiddleMouse> yes if not active noput<MiddleMouse> yes if active noyank andput<RightMouse> yesstart or extend yes<A-RightMouse> yes start or extend blockw. yes<A-RightMouse><S-RightMouse> yes no change yes "#" (2)<S-RightMouse><C-RightMouse> no no change no "CTRL-T"<RightDrag> yes extend no<RightDrag><RightRelease> yes extend no<RightRelease>Insert orReplace Mode:event position selection change action cursor window<LeftMouse> yes (cannot be active) yes<C-LeftMouse> yes (cannot be active) yes "CTRL-O^]" (2)<S-LeftMouse> yes (cannot be active) yes "CTRL-O*" (2)<LeftDrag> yes start or extend (1) no likeCTRL-O (1)<LeftRelease> yes start or extend (1) no likeCTRL-O (1)<MiddleMouse> no (cannot be active) noputregister<RightMouse> yes start or extend yes likeCTRL-O<A-RightMouse> yes start or extend blockw. yes<S-RightMouse> yes (cannot be active) yes "CTRL-O#" (2)<C-RightMouse> no(cannot be active) no "CTRL-OCTRL-T"Inahelp window:event position selection change action cursor window<2-LeftMouse> yes (cannot be active) no "^]" (jump tohelp tag)When'mousemodel'is "popup", these are different:Normal Mode:event position selection change action cursor window<S-LeftMouse>yesstart or extend (1) no<A-LeftMouse> yes start or extend blockw. no<A-LeftMouse><RightMouse>nopopup menu noInsert orReplace Mode:event position selection change action cursor window<S-LeftMouse> yes start or extend (1) no likeCTRL-O (1)<A-LeftMouse> yes start or extend blockw. no<RightMouse> nopopup menu no(1) only if mouse pointer moved since press(2) only if clickis in same bufferClicking the left mouse button causes the cursor to be positioned. If theclickis in anotherwindow thatwindowis made the active window. Whenediting the command-line the cursor can only be positioned on thecommand-line. When inInsert mode Vim remains inInsert mode. If'scrolloff'is set, and the cursoris positioned within'scrolloff' lines from thewindowborder, the textis scrolled.A selection can be started by pressing the left mouse button on the firstcharacter, moving the mouse to the last character, then releasing the mousebutton. You will not always see the selection until you release the button,only in some versions (GUI, Win32) will the dragging be shown immediately.Note that you can make the text scroll by moving the mouseat least onecharacter in the first/last line in thewindow when'scrolloff'is non-zero.In Normal,Visual andSelect mode clicking the right mouse button causes theVisual area to be extended. When'mousemodel'is "popup", the left button hasto be used while keeping theshift key pressed. When clicking inawindowwhichis editing another buffer, theVisual orSelect modeis stopped.In Normal,Visual andSelect mode clicking the right mouse button with thealtkey pressed causes theVisual area to become blockwise. When'mousemodel'is"popup" the left button has to be used with thealt key.Note that this won'twork on systems where thewindow manager consumes the mouse events when thealt keyis pressed (it may move the window).double-clickDouble, triple and quadruple clicks are supported when theGUIis active, forWin32, and for an xterm (if the gettimeofday() functionis available). Forselecting text, extra clicks extend the selection:clickselectdoubleword or% match<2-LeftMouse>tripleline<3-LeftMouse>quadruplerectangular block<4-LeftMouse>Exception: Ina Helpwindowa double click jumps tohelp for theword thatisclicked on.A double click onaword selects that word.'iskeyword'is used to specifywhich characters are included ina word.A double click ona characterthat hasa match selects until that match (like using "v%"). If the matchisan #if/#else/#endif block, the selection becomes linewise.ForMS-Windows and xterm the time for double clicking can be set with the'mousetime' option. For the other systems this timeis defined outside of Vim.An example, for usinga double click to jump to thetag under the cursor::map <2-LeftMouse> :exe "tag " .. expand("<cword>")<CR>Dragging the mouse witha double click (button-down, button-up, button-downand then drag) will result in whole words to be selected. This continuesuntil the buttonis released,at which point the selectionis per characteragain.Forscrolling with the mouse seescroll-mouse-wheel.gpm-mouseThe GPM mouseis only supported when the+mouse_gpm feature was enabledatcompile time. The GPM mouse driver (Linux console) does not support quadrupleclicks.InInsert mode, whena selectionis started, Vim goes intoNormal modetemporarily. WhenVisual orSelect mode ends,it returns toInsert mode.Thisis like usingCTRL-O inInsert mode.Select modeis used when the'selectmode' option contains "mouse".sysmouseThesysmouseis only supported when the+mouse_sysmouse feature was enabledat compile time. Thesysmouse driver(*BSD console) does not support keyboardmodifiers.drag-status-lineWhen working with several windows, the size of thewindows can be changed bydragging the status line with the mouse. Point the mouseata status line,press the left button, move the mouse to the new position of the status line,release the button. Just clicking the mouse ina status line makes thatwindowthe current window, without moving the cursor. If by selectingawindowitwill change position or size, the dragging of the status line will lookconfusing, butit will work (just try it).<MiddleRelease><MiddleDrag>Mouse clicks can be mapped. The codes for mouse clicks are: code mouse button normal action<LeftMouse> left pressed set cursor position<LeftDrag> left moved while pressed extend selection<LeftRelease> left released set selectionend<MiddleMouse> middle pressed paste textat cursor position<MiddleDrag> middle moved while pressed-<MiddleRelease> middle released-<RightMouse> right pressed extend selection<RightDrag> right moved while pressed extend selection<RightRelease> right released set selectionend<X1Mouse> X1 button pressed-X1Mouse<X1Drag> X1 moved while pressed-X1Drag<X1Release> X1 button release-X1Release<X2Mouse> X2 button pressed-X2Mouse<X2Drag> X2 moved while pressed-X2Drag<X2Release> X2 button release-X2ReleaseThe X1 and X2 buttons refer to the extra buttons found on some mice. The'Microsoft Explorer' mouse has these buttons available to the right thumb.Currently X1 and X2 only work onWin32 andX11 environments.Examples::noremap <MiddleMouse> <LeftMouse><MiddleMouse>Pasteat the position of the middle mouse button click (otherwise the pastewould be doneat the cursor position).:noremap <LeftRelease> <LeftRelease>yImmediatelyyank the selection, when usingVisual mode.Note the use of ":noremap" instead of "map" to avoida recursive mapping.:map <X1Mouse> <C-O>:map <X2Mouse> <C-I>Map the X1 and X2 buttons togo forwards and backwards in the jump list, seeCTRL-O andCTRL-I.mouse-swap-buttonsTo swap the meaning of the left and right mouse buttons::noremap<LeftMouse><RightMouse>:noremap<LeftDrag><RightDrag>:noremap<LeftRelease><RightRelease>:noremap<RightMouse><LeftMouse>:noremap<RightDrag><LeftDrag>:noremap<RightRelease><LeftRelease>:noremapg<LeftMouse><C-RightMouse>:noremapg<RightMouse><C-LeftMouse>:noremap!<LeftMouse><RightMouse>:noremap!<LeftDrag><RightDrag>:noremap!<LeftRelease><RightRelease>:noremap!<RightMouse><LeftMouse>:noremap!<RightDrag><LeftDrag>:noremap!<RightRelease><LeftRelease> vim:tw=78:ts=8:noet:ft=help:norl: