| /vim-8.2.3635/.github/workflows/ |
| H A D | ci.yml | 59 run: | 80 run: | 90 run: | 142 run: | 163 run: | 175 run: | 180 run: | 186 run: | 194 run: | 199 run: | [all …]
|
| H A D | coverity.yml | 19 run: | 27 run: | 45 run: | 53 run: | 59 run: | 66 run: | 70 run: |
|
| H A D | codeql-analysis.yml | 46 # If this step fails, then you should remove it and run the build manually (see below) 50 # ℹ️ Command-line programs to run using the OS shell. 57 #- run: |
|
| /vim-8.2.3635/runtime/ftplugin/ |
| H A D | zsh.vim | 23 …command! -buffer -nargs=1 RunHelp silent exe '!MANPAGER= zsh -ic "autoload -Uz run-help; run-help … 25 …command! -buffer -nargs=1 RunHelp silent exe ':term zsh -ic "autoload -Uz run-help; run-help <args… 27 …command! -buffer -nargs=1 RunHelp echo system('zsh -ic "autoload -Uz run-help; run-help <args> 2>/…
|
| /vim-8.2.3635/src/testdir/ |
| H A D | shared.vim | 13 " This test requires the Python command to run the test server. 228 " Get $VIMPROG to run the Vim executable. 240 " Get the command to run Vim, with -u NONE and --not-a-term arguments. 271 " If using valgrind, make sure every run uses a different log file. 280 " Get the command to run Vim, with --clean instead of "-u NONE". 289 " Optionally run Vim under valgrind 295 " Get the command to run Vim, with --clean, and force to run in terminal so it 298 " Add -v to have gvim run in the terminal (if possible) 323 " Optionally run Vim under valgrind
|
| H A D | test_channel.vim | 13 " Can't run this test without Python. 512 call assert_equal("run", job_status(job)) 595 call assert_equal("run", job_status(job)) 631 call assert_equal("run", job_status(job)) 759 call assert_equal("run", job_status(job)) 807 call assert_equal("run", job_status(job)) 846 call assert_equal("run", job_status(job)) 885 call assert_equal("run", job_status(job)) 914 call assert_equal("run", job_status(job)) 993 call assert_equal("run", job_status(job)) [all …]
|
| H A D | term_util.vim | 10 " For most tests we need to be able to run terminal Vim with 256 colors. On 11 " MS-Windows the console only has 16 colors and the GUI can't run in a 130 " Starting a terminal to run Vim is always considered flaky. 138 " Using a terminal to run Vim is always considered flaky. 177 call assert_match("{'job': 'process \\d\\+ run'}", string)
|
| H A D | test_alot_latin.vim | 1 " A series of tests that can run in one Vim invocation. 5 " files, so that they can be run by themselves.
|
| H A D | Make_amiga.mak | 2 # Makefile to run all tests for Vim, on Amiga 35 # Delete the .out file(s) to run test(s).
|
| H A D | Make_vms.mms | 2 # Makefile to run all tests for Vim on VMS 19 # NOTE: You can run this script just in X/Window environment. It will 58 -@ !run the test
|
| /vim-8.2.3635/runtime/doc/ |
| H A D | os_win32.txt | 189 To use the installer, simply run the exe file. The following switches are 274 Q. How can I asynchronously run an external command or program, or open a 276 A. When using :! to run an external command, you can run it with "start". For 277 example, to run notepad: > 298 Q. How do I avoid getting a window for programs that I run asynchronously? 300 1) You may use the /min flag in order to run program in a minimized state 303 2) You can use the /b flag to run console applications without creating a 305 should use this flag only if the application you run doesn't require any 309 Example for a console application, run Exuberant ctags: > 314 Now delete the "tags" file and run this command: >
|
| H A D | if_ole.txt | 126 registry. In order to do this, Vim should be run with a single parameter of 131 If gvim with OLE support is run and notices that no Vim OLE server has been 136 registry is not writable. If you run into this problem you need to run gvim 161 The OLE version can be used to run Vim as the editor in Microsoft Visual
|
| H A D | pi_spec.txt | 24 It means that you may run the plugin inside a spec file by pressing 29 Every time you run the plugin, it will check to see if the last entry in the 67 a format string, when you run the SpecChangelog command for the first
|
| H A D | debug.txt | 31 run -u unix.vim -U NONE -s dotest.in test11.in 55 Note: Vim will run much slower. If your .vimrc is big or you have several 56 plugins you need to be patient for startup, or run with the "--clean" 128 debugger. To set WinDbg as your postmortem debugger, run "windbg -I".
|
| /vim-8.2.3635/runtime/indent/ |
| H A D | sas.vim | 24 " Regex that captures the end of a run-processing section 25 let s:section_run = '\v%(^|;)\s*run\s*;' 42 " List of procs supporting run-processing 84 " Check if the section supports run-processing 116 " Check if the previous section supports run-processing
|
| /vim-8.2.3635/src/ |
| H A D | config.mk.in | 5 # Edit Makefile and run "make" or run ./configure with other arguments. 10 # b) Modifications to the makefile are not lost when configure is run. 176 # Make sure that "make first" will run "make all" once configure has done its
|
| H A D | msvc2015.bat | 6 rem For x86 builds run this without options: 8 rem For x64 builds run this with "x86_amd64" option:
|
| H A D | INSTALL | 34 1. make run configure, compile and link 105 If you run configure by hand (not using the Makefile), remember that any 116 run configure again. 167 automatically. If you want to use it anyway, run configure with 207 And run configure with "--disable-motif-check".
|
| /vim-8.2.3635/runtime/indent/testdir/ |
| H A D | README.txt | 85 Now run "make test" from the parent directory. After Vim has done the 90 rename it to overwrite the FILETYPE.ok file. If you now run "make test" again, 94 If you try to run "make test" again you will notice that nothing happens, 97 newer than the FILETYPE.out file, the test will also run.
|
| /vim-8.2.3635/runtime/macros/life/ |
| H A D | click.me | 2 To run the "Conway's game of life" macros: 5 2. Type "g" to run the macros.
|
| H A D | life.vim | 10 " - Made "g" run the whole thing, "C" run one generation. 54 " Time to run 30 generations on my 233 AMD K6 (FreeBSD 3.0): 64 " Time to run 30 generations on my 850 AMD Duron (FreeBSD 4.2): 207 " line, and then run the edit command. (used by work out square).
|
| /vim-8.2.3635/runtime/autoload/ |
| H A D | context.vim | 54 let l:jobs = filter(g:context_jobs, 'job_status(v:val) == "run"') 65 let l:jobs = filter(g:context_jobs, 'job_status(v:val) == "run"') 72 if job_status(job) == "run" 85 if index(g:context_jobs, a:job) != -1 && job_status(a:job) != 'run' " just in case
|
| /vim-8.2.3635/runtime/macros/maze/ |
| H A D | README.txt | 1 To run the maze macros with Vim: 17 1. run uudecode on the file "maze.vi.macros.uu" to 21 3. run maze > maze.out and input a small number (for example 10 if
|
| /vim-8.2.3635/runtime/pack/dist/opt/termdebug/plugin/ |
| H A D | termdebug.vim | 12 " There are two ways to run gdb: 30 " Gdb is run as a job with callbacks for I/O. 189 if gdbproc == v:null || job_status(gdbproc) !=# 'run' 232 " Open a terminal window to run the debugger. 270 " Set arguments to be run. 338 " Open a window with a prompt buffer to run gdb in. 369 if job_status(s:gdbjob) != "run" 421 " Set arguments to be run 473 call s:SendCommand('-exec-run') 981 call s:SendCommand('-exec-run') [all …]
|
| /vim-8.2.3635/runtime/macros/hanoi/ |
| H A D | poster | 20 Save this article, unshar it, and run uudecode on hanoi.vi.macros.uu. 22 Then run vi (with no file: just type "vi") and type:
|