Home
last modified time | relevance | path

Searched refs:handled (Results 1 – 25 of 49) sorted by relevance

12

/vim-8.2.3635/runtime/indent/
H A Dpascal.vim181 " Most "begin"s will have been handled by now. Any remaining
191 " Note that extended-pascal is handled here, unless it is simpler to
/vim-8.2.3635/src/
H A DREADME.md163 Ex commands are handled by the function `do_cmdline()`. It does the generic
177 The Normal mode commands are handled by the `normal_cmd()` function. It also
209 a menu action. Key hits are handled by the system-specific GUI code, which
/vim-8.2.3635/runtime/syntax/
H A Dsqlinformix.vim107 " Highlight "on" (if it's not followed by some words we've already handled)
110 " Highlight "end" (if it's not followed by some words we've already handled)
H A Dpod.vim54 " Inline textual items handled specially by POD
H A Dgift.vim45 … "<" contained "HTML characters that might need to be handled/escaped
H A Drust.vim63 " {} are handled by rustFoldBraces
/vim-8.2.3635/runtime/tools/
H A Defm_filter.txt3 Some compilers produce an error message that cannot be handled with
/vim-8.2.3635/src/testdir/
H A DREADME.txt32 to check memory allocation failures are handled gracefully. You need to
H A Dtest_channel.vim74 " check that getjob without a job is handled correctly
112 " handled before getting the response, but it's not guaranteed, thus wait a
295 " Test that a server crash is handled gracefully.
1365 " This caused a crash, because messages were handled while peeking for a
1868 " Check that backslash in $COMSPEC is handled properly.
2355 " Check that in the BufEnter autocommand events are being handled
H A Dtest_recover.vim87 " the GUI dialog can't be handled
H A Dtest_mksession.vim541 " create two window on the same terminal to check this is handled OK
/vim-8.2.3635/src/libvterm/src/
H A Dstate.c958 int handled = 1; in on_csi() local
1531 handled = 0; in on_csi()
1567 handled = 0; in on_csi()
1571 if (!handled) { in on_csi()
/vim-8.2.3635/runtime/ftplugin/
H A Docaml.vim259 " - latin1 accents are handled
260 " - lists are handled, even on multiple lines, you don't need the visual mode
263 " and '{...}') are handled the same way
/vim-8.2.3635/runtime/doc/
H A Dchannel.txt135 not handled otherwise. It gets two arguments: the channel
245 To send a message and letting the response handled by a specific function,
294 handled by Vim internally, it does not require a handler for the channel.
409 To send a message and letting the response handled by a specific function,
1179 positive number will be handled by a callback, commands are handled as usual.
H A Dmbyte.txt417 the same way, because all Unicode is handled
473 handled internally.
623 Setting the 'guifontset' option also means that all font names will be handled
769 In |IM-server| type input structures, the input event is handled by either
1342 Bytes which are not part of a valid UTF-8 byte sequence are handled like a
1346 Overlong sequences are not handled specially and displayed like a valid
H A Dusr_26.txt96 programs. If you do not want a number with leading zeros to be handled as
H A Dvim.man300 be handled as a file name. This can be used to edit a
H A Dgui_w32.txt414 handled by windows, other ALT keys can be mapped. This doesn't allow a
H A Dvisual.txt491 Otherwise, typed characters are handled as in Visual mode.
H A Dversion5.txt670 "y$" in an empty line now is handled as an error (Vi
1249 before <EOL> was not handled Vi compatible. (Acevedo)
1861 ":set t_Co=0" was not handled like a normal term. Now it's translated into
2209 'winaltkeys' Win32 and Motif GUI. When "yes", ALT keys are handled
2467 Setting 'keywordprg' to "man -s" is handled specifically. The "-s" is removed
2785 Unix: tgoto() can return NULL, which was not handled correctly in configure.
4051 handled that way. broke ":s/foo/some^Mtext/".
4146 When using "set mouse=a" in Ex mode, mouse events were handled like typed
4615 highlighting was not correct. Now overlapping matches are handled correctly.
5588 Problem: In the option-window, ":set go&" resulted in 'go' being handled
[all …]
H A Dversion7.txt530 CTRL-T cannot be handled then.
2430 not handled correctly.
3593 toplevel. Let garbagecollect() set a flag that is handled at the
4353 Problem: Some characters of the "gb18030" encoding are not handled
7884 Problem: "killed" netbeans events are not handled correctly.
7918 Problem: Recursive structures are not handled properly in Python
9900 Problem: Commas in 'langmap' are not always handled correctly.
11827 Problem: Python: Errors in Unicode characters not handled nicely.
14027 Problem: Not all zero-width matches handled correctly for "gn".
17469 Problem: Python: non-import errors not handled correctly.
[all …]
H A Dusr_02.txt614 < for how the '|' is handled in mappings.
H A Dusr_40.txt237 Abbreviations are a lot like Insert mode mappings. The arguments are handled
H A Dusr_30.txt539 Notice that Vim properly handled the beginning of each line.
/vim-8.2.3635/runtime/spell/
H A DREADME.txt60 added/removed from the LibreOffice lists can also be handled by the patches.

12