| /vim-8.2.3635/src/ |
| H A D | cindent.c | 2416 look = skipwhite(look); in get_c_indent() 3909 if (*look == '*' || *look == '!') in in_cinkeys() 3929 && look[1] >= '?' && look[1] <= '_' in in_cinkeys() 4010 while (*look && *look != '>') in in_cinkeys() 4017 else if (*look == '=' && look[1] != ',' && look[1] != NUL) in in_cinkeys() 4029 p = look + STRLEN(look); in in_cinkeys() 4059 ? MB_STRNICMP(s, look, p - look) in in_cinkeys() 4060 : STRNCMP(s, look, p - look)) == 0) in in_cinkeys() 4072 ? MB_STRNICMP(line - (p - look), look, p - look) in in_cinkeys() 4073 : STRNCMP(line - (p - look), look, p - look)) in in_cinkeys() [all …]
|
| H A D | INSTALL | 130 NOTE: This is incomplete, look in Makefile for more info. 142 --enable-gui defaults to "auto", so it will automatically look for a GUI (in 152 For example, if --enable-gui is set to "auto", but you don't want it look for
|
| /vim-8.2.3635/runtime/doc/ |
| H A D | usr_06.txt | 56 Vim will use bold, italic and underlined text, but this doesn't look 72 still doesn't work, have a look at |xterm-color|, which shows a few 87 < To see which types are available, look in the directory 132 it look further back, see the help for the specific syntax file. For 181 If you want to see what the most often used color combinations look like, use 187 readable and look nice. These aren't the only colors available to you though. 248 few settings. If you have a color printer, the paper output should look the 250 colors will be adjusted to look good on white paper. 286 well, the output should look exactly as it does in Vim. See |2html.vim| for 290 others look at the colored text.
|
| H A D | usr_11.txt | 91 Vim will list the swap files that it can find. It will also look in other 95 The output could look like this: 112 If there are several swap files that look like they may be the one you want to 114 number of the one you want to use. Carefully look at the dates to decide 177 line with "process ID". It might look like this: 254 else is editing the file, but you just want to look in it and not make
|
| H A D | pi_spec.txt | 60 You can easily customize how your spec file entry will look like. To do 72 To discover which format options you can use, take a look at the strftime()
|
| H A D | os_390.txt | 118 look at the following Redbook: 126 Also look at:
|
| H A D | usr_22.txt | 242 look for your file. 254 This tells Vim to look in the directory "proto", below the directory where the 256 look for "proto/inits.h", starting in the directory of the file. 257 Without the "./", thus "proto", Vim would look in the "proto" directory 341 The output could look like this:
|
| H A D | farsi.txt | 14 If you would like to bring Farsi support back, please have a look at the old
|
| H A D | usr_90.txt | 59 To get the Vim archives, look in this file for a mirror near you, this should 98 If there are errors while compiling, carefully look at the error messages. 121 You could look in the |maillist-archive| for a solution. If everything else 214 To get the Vim archives, look in this file for a mirror near you, this should 257 Carefully look through the messages and select the options you want to use.
|
| H A D | gui_x11.txt | 134 which make Motif applications look even better, highly recommended! 411 have a quick look at GTK+ CSS through simple, illustrative examples. 420 than those of the GTK+ 2 GUI. Some people may want to make them look similar 495 Note: Theming can be difficult since it must make every application look 625 files in a directory where configure doesn't look, edit the Makefile to enter 649 menus look a bit better. Edit the Makefile and look for "XAW_LIB". The 651 3D (in fact, they look more like Motif).
|
| H A D | usr_44.txt | 176 and end of the region. But what about strings that look like this? 199 Take a look at this comment: 252 includes a "contains=xComment" argument. Now look what happens with this 544 tells Vim the minimum number of lines to look backward, and "maxlines" tells 546 For example, the following command tells Vim to look at least 10 lines 573 Finally, you can specify a syntax group to look for by using this command: 689 If you select specific colors it will look bad with some color schemes. And
|
| H A D | usr_21.txt | 58 <Enter>. This allows you to have a look at the output from the command before 61 a look at an overview: 115 Take a look at how you can build up your own viminfo string. First, the ' 411 folds open, you can set the options to make the window look that way. Then 479 that Vim will use. This allows making it look like a comment, like what was
|
| H A D | vimdiff.man | 27 The 'wrap' and 'scrollbind' options are set to make the text look good.
|
| H A D | ft_ps1.txt | 55 To look up keywords using PowerShell's Get-Help, press the |K| key. For more
|
| H A D | usr_43.txt | 37 see where Vim will look for the "ftplugin" directory: > 150 (same place where filetype.vim goes). It might look like this: >
|
| /vim-8.2.3635/src/testdir/ |
| H A D | test_packadd.vim | 254 call writefile(['look here: *look-here*'], docdir1 . '/bar.txt') 255 call writefile(['look away: *look-away*'], docdir2 . '/foo.txt') 261 call assert_match('look-here', tags1[0]) 263 call assert_match('look-away', tags2[0])
|
| /vim-8.2.3635/runtime/indent/ |
| H A D | dtd.vim | 141 " Finally, look for any additions and/or exceptions to the content model. 218 " Finally look for the attribute’s default value. If non exists, indent 224 " We need to look for the fixed value. If non exists, indent three 253 " that this is an external unparsed entity. In that case we have to look
|
| H A D | html.vim | 444 " look back for <pre, </pre, <script, </script, <style, </style tags 449 " look back in result range (stopline, startline) for comment 456 " look back to get indent of comment opener 459 " look back for a blocktag 498 " else look back for comment 890 " Limited to look up to b:html_indent_line_limit lines away.
|
| /vim-8.2.3635/runtime/spell/am/ |
| H A D | am_ET.diff | 8 + # Aspell has sound folding for Amharic, but it doesn't look right, it uses
|
| /vim-8.2.3635/runtime/compiler/ |
| H A D | README.txt | 7 If you want to write your own compiler plugin, have a look at the other files
|
| /vim-8.2.3635/ |
| H A D | README.txt | 102 For the most recent information about sponsoring look on the Vim web site: 117 If you have problems, have a look at the Vim documentation or tips:
|
| H A D | README.md | 119 For the most recent information about sponsoring look on the Vim web site: 134 If you have problems, have a look at the Vim documentation or tips:
|
| /vim-8.2.3635/READMEdir/ |
| H A D | README_ami.txt | 27 Vim version 5.4 will look for your vimrc file in $VIM, and for the runtime
|
| /vim-8.2.3635/runtime/syntax/ |
| H A D | antlr.vim | 32 " remove function definitions (they look different) (first define in
|
| /vim-8.2.3635/runtime/plugin/ |
| H A D | tarPlugin.vim | 9 " Also look there for further comments and documentation.
|