| /vim-8.2.3635/runtime/indent/ |
| H A D | vhdl.vim | 77 " where: start of current line
126 " where: start of previous line
137 " where: start of previous line
139 " where: start of previous line
248 " where: start of current line
255 " where: start of current line
264 " where: start of current line
273 " where: start of current line
299 " where: end of previous line
310 " where: end of previous line
[all …]
|
| H A D | fortran.vim | 21 setlocal indentkeys+==~end,=~case,=~if,=~else,=~do,=~where,=~elsewhere,=~select
109 "where, else where, forall, type, interface and associate statements
110 if prevstat =~? '^\s*\(case\|class\|else\|else\s*if\|else\s*where\)\>'
112 \ ||prevstat=~?'^\s*\(\d\+\s\)\=\s*\(\a\w*\s*:\)\=\s*\(forall\|where\|block\)\>'
145 " end where, end select, end forall, end interface, end associate,
148 \. '\(else\|else\s*if\|else\s*where\|case\|class\|'
149 \. 'end\s*\(if\|where\|select\|interface\|'
|
| H A D | rust.vim | 105 " for cases like "/*" where the next line should start " * ", not
129 " Handle where clauses nicely: subsequent values should line up nicely.
131 \ && prevline =~# '^\s*where\s'
144 " One case where this doesn't work out is where *this* line contains
148 " Another case where we don't want to is one like a function
166 " There are probably other cases where we don't want to do this as
|
| H A D | sdl.vim | 64 " Put each alternatives where the corresponding decision was
71 " Put each state where the preceding state was
81 " Put each end* where the corresponding begin was
|
| /vim-8.2.3635/src/ |
| H A D | vim9type.c | 449 where_T where = WHERE_INIT; in check_typval_arg_type() local
451 where.wt_index = arg_idx; in check_typval_arg_type()
494 where_T where = WHERE_INIT; in arg_type_mismatch() local
496 where.wt_index = arg_idx; in arg_type_mismatch()
507 if (where.wt_index > 0) in type_mismatch_where()
510 semsg(_(where.wt_variable in type_mismatch_where()
515 semsg(_(where.wt_variable in type_mismatch_where()
518 where.wt_index, typename1, typename2, where.wt_func_name); in type_mismatch_where()
565 FALSE, where); in check_type()
574 FALSE, where); in check_type()
[all …]
|
| H A D | gui_haiku.cc | 938 BPoint where;
940 v->MouseUp(where);
1711 BPoint where; in mchDrawString() local
1716 DrawString(p, clen, where); in mchDrawString()
1718 where.x += 1.0; in mchDrawString()
1720 DrawString(p, clen, where); in mchDrawString()
1732 DrawString((char*)s, len, where); in mchDrawString()
1734 where.x += 1.0; in mchDrawString()
1886 BPoint where; in DrawIMString() local
1913 DrawString((s+i), clen, where); in DrawIMString()
[all …]
|
| H A D | INSTALLvms.txt | 41 where X.X is the version number.
294 Defines the directory where the necessary include files are.
347 Edit PERL_INC = to point to perl includes directory where is extern.h
357 PYTHON_INCLUDE should point to Python include files where for ex:
372 Edit TCL_INC = to point to TCL includes directory where is tcl.h
|
| /vim-8.2.3635/src/proto/ |
| H A D | vim9type.pro | 14 int check_typval_type(type_T *expected, typval_T *actual_tv, where_T where);
17 void type_mismatch_where(type_T *expected, type_T *actual, where_T where);
18 int check_type(type_T *expected, type_T *actual, int give_msg, where_T where);
|
| H A D | message.pro | 14 void internal_error(char *where);
15 void internal_error_no_abort(char *where);
|
| /vim-8.2.3635/READMEdir/ |
| H A D | README_dos.txt | 23 - When selecting a directory to install Vim, use the same place where other
28 - After selecting the directory where to install Vim, clicking on "Next" will
37 1. Go to the directory where you want to put the Vim files. Examples:
41 located. Check the $VIM setting to see where it points to:
64 to another location. That is where they will stay, the install program
125 opportunity to set defaults for the Console where Vim runs in.
|
| H A D | README_ami.txt | 7 Unpack the distributed files in the place where you want to keep them. It is
32 the search path to include the directory where the Vim executable is.
|
| /vim-8.2.3635/runtime/doc/ |
| H A D | usr_03.txt | 18 |03.6| Telling where you are
229 *03.6* Telling where you are
231 To see where you are in a file, there are three ways:
238 This shows the name of the file you are editing, the line number where the
259 a numerical value and string options. You will see examples of this where
432 where it's used. You could move the cursor to "nr" and use the "*" command
477 find out where it is: >
490 "G" moves to the end of the file. "o" starts a new line, where you type the
519 Let's mark the places where "/the" matches in this example line with "x"s:
564 where you came from, use this command: >
[all …]
|
| H A D | usr_21.txt | 36 You are right back where you left Vim, nothing has changed.
44 When you are running the GUI you can't go back to the shell where Vim was
60 The "!" is also used in other places where a program is run. Let's take
164 And you are right back where you left Vim. So you can get on with your work.
168 The |:marks| command is useful to find out where '0 to '9 will take you.
240 work and pick up where you left off the next day. You can do this by saving
298 next time you load the secret session you can continue where you were at this
307 where you are now, by saving the current setup in a session, or keep the
404 Vim will decide where to store the view. When you later edit the same file
450 A typical example is a C program where you make indents by a multiple of 4
[all …]
|
| H A D | usr_07.txt | 198 of where you are in the list of files. Only commands like ":next" and
212 This takes you to the position where the cursor was when you left the file.
213 Another mark that is remembered is the position where you made the last
222 last line of the file. Using `. takes you to the position where you deleted
252 and where it is placed. For example, use the H mark in a header file, M in
255 To see where a specific mark is, give an argument to the ":marks" command: >
283 Another option that matters here is 'backupdir'. It specifies where the
331 character where you want the text to appear after. Use "p" to put the text
351 A register is a place where Vim stores text. Here we will use the
373 another file, move around and place the text where you want it: >
|
| H A D | debug.txt | 21 compilation, here is what you can do to find out exactly where Vim crashes.
33 3. Check where Vim crashes, gdb should give a message for this.
36 where
105 to the directory where you have the PDB file and click Open.
109 appear. Navigate to the directory where the Vim source is (if you have it.)
|
| H A D | usr_29.txt | 9 contains many features to aid in writing programs. Jump around to find where
26 What is a tag? It is a location where an identifier is defined. An example
29 tag, the place where an identifier is defined.
101 up again with CTRL-T. Use ":tags" to find out where you are.
154 Now you only need to tell Vim where your big tags file is: >
188 where the match is defined.
268 Cscope is a free program. It does not only find places where an identifier is
269 declared, but also where it is used. See |cscope|.
291 There is a script that automatically displays the text where the word under
542 jump back to where you started from.
[all …]
|
| H A D | usr_22.txt | 208 For a window where `:lcd` has been used a different current directory is
241 option to find the file. This option is a list of directory names where to
248 This directory is an absolute path. No matter where you are, it will be the
249 same place. What if you have located files in a subdirectory, below where the
254 This tells Vim to look in the directory "proto", below the directory where the
258 below the current directory. And the current directory might not be where the
261 The 'path' option allows specifying the directories where to search for files
350 and the line number where the cursor was the last time.
|
| H A D | usr_25.txt | 27 to press <Enter> yourself. This is useful when you are writing programs where
28 you want to decide where the line ends. It is not so good when you are
391 'breakat' specifies the characters where a break can be inserted.
473 Now you can move the cursor to positions where there isn't any text. This is
479 Now press "j" and you are right where you can enter the value for "input A".
488 of a white space separated word. Then "j" moves to the place where the next
509 6. Move the cursor to "test 1", where the new column must be placed.
518 Notice that the whole "test 1" column was shifted right, also the line where
|
| H A D | map.txt | 61 where the map command applies. The result, including
80 where the map command applies. Disallow mapping of
96 Remove the mapping of {lhs} for the modes where the
98 for other modes where it applies.
115 Remove ALL mappings for the modes where the map
132 List all key mappings for the modes where the map
148 with {lhs} in the modes where the map command applies.
1079 or this is where the line or insertion starts.
1134 column indicates the mode where the abbreviation is
1426 defined, not where it is invoked! Example:
[all …]
|
| H A D | usr_90.txt | 25 single user. The installation is almost the same, but the directory where Vim
28 used. But this may be different for your system. Try finding out where other
89 Change "path" to where you have downloaded the file.
148 If this doesn't work, use this command to check where Vim is looking for the
174 --prefix={directory} Top directory where to install Vim.
260 The install program doesn't move the runtime files. They remain where you
265 the same location as where the binaries are. You need a compiler for which a
|
| H A D | usr_28.txt | 115 - move around to where you want to do your work
140 It is sometimes difficult to see or remember where a fold is located, thus
141 where a |zo| command would actually work. To see the defined folds: >
208 Also check out the 'viewdir' option, which specifies where the views are
336 use this for text where something in the text indicates which lines belong
337 together. An example is an e-mail message where the quoted text is indicated
406 The main advantage of markers is that you can put them exactly where you
|
| H A D | repeat.txt | 52 lines within [range] where {pattern} matches.
56 lines within [range] where {pattern} does NOT match.
78 marking each line where a match occurs (for a multi-line pattern, only the
103 where the cursor was before the global command).
211 :ru[ntime][!] [where] {file} ..
230 When [where] is omitted only 'runtimepath' is used.
318 An error only causes sourcing the script where it
826 *>where*
829 where
855 context, where local variables can be inspected, and once just before
[all …]
|
| H A D | tips.txt | 17 Finding where identifiers are used |ident-search|
52 |[I| List all lines in current and included files where
83 Finding where identifiers are used *ident-search*
85 You probably already know that |tags| can be used to jump to the place where a
87 the places where a function or variable is being used. This is possible in
154 these two variables are the correct place where the above mentioned control
403 Where {dirname} is the directory where the help files are. The |gzip| plugin
405 You must make sure that $VIMRUNTIME is set to where the other Vim files are,
|
| /vim-8.2.3635/runtime/macros/maze/ |
| H A D | maze_mac | 25 " to where you started from, if you do not stop).
31 " there are four places where walls could be put - to the north, to the south,
39 " A wall exists to the south of you if the character where you are
42 " Note the difference for direction south, where we must examine the character
43 " where the cursor is rather than an adjacent cell.
54 " The names of the states are N1, N2, S1, S2, E1, E2, W1, W2, where each letter
73 " where F is a macro which yanks the character under the cursor into
|
| /vim-8.2.3635/src/GvimExt/ |
| H A D | README.txt | 17 directory, where the other DLL files are.
58 where are the locations for your rundll32.exe and setupapi.dll files. In
63 where %1 can be substituted by gvimext.inf
|