Home
last modified time | relevance | path

Searched refs:changes (Results 1 – 25 of 261) sorted by relevance

1234567891011

/vim-8.2.3635/
H A DLICENSE15 a) If you make changes to Vim yourself, you must clearly describe in
18 must make your changes, including source code, available to the
20 include your changes in the official version of Vim. What the
25 changes it will be announced in appropriate places (most likely
29 received your changes they will not have to be sent again.
33 text under a) applies to those changes.
38 making their own changes to the official version of Vim.
41 changes if the following three conditions are met:
46 - You keep the changes for at least three years after last
62 not conflict with the license used for the changes.
[all …]
/vim-8.2.3635/runtime/doc/
H A Dusr_32.txt8 Vim provides multi-level undo. If you undo a few changes and then make a new
13 |32.2| Numbering changes
24 Sometimes you make several changes, and then discover you want to go back to
39 made changes after undoing some changes. It's explained in the next section.
45 *32.2* Numbering changes
48 possible to branch off. This happens when you undo a few changes and then
49 make a new change. The new changes become a branch in the undo tree.
53 two changes, numbered 1 and 2, and three states of the text:
83 What matters here is the order in which the changes are made. Undo and redo
89 it. But sometimes by the number of one of the changes below it, especially
[all …]
H A Duganda.txt43 must make your changes, including source code, available to the
45 include your changes in the official version of Vim. What the
46 maintainer will do with your changes and under what license they
50 changes it will be announced in appropriate places (most likely
54 received your changes they will not have to be sent again.
58 text under a) applies to those changes.
62 add. The changes and their license must not restrict others from
63 making their own changes to the official version of Vim.
66 changes if the following three conditions are met:
71 - You keep the changes for at least three years after last
[all …]
H A Dundo.txt22 u Undo [count] changes.
31 CTRL-R Redo [count] changes which were undone.
37 U Undo all latest changes on one line, the line where
43 changes again, getting back the text before the undo.
52 Use "u" to undo changes until the buffer becomes unchanged.
92 :undoj[oin] Join further changes with the previous undo block.
94 properly undoing changes. Don't use this after undo
126 :undol[ist] List the leafs in the tree of changes. Example:
127 number changes when saved ~
136 The "changes" column is the number of changes to this
[all …]
H A Dusr_11.txt19 Previous chapter: |usr_10.txt| Making big changes
32 bits and pieces of the original file. If Vim recovered your changes you will
39 and run diff with the original file to check for changes) ~
68 file after making changes. It is safe to delete the swap file now.
74 the system went down, the changes after the last flush will be lost.
163 different instances of the same file when making changes. ~
168 to recover the changes (see ":help recovery"). ~
233 yourself did the last changes under a different login name, a logout
242 that file, be prepared to redo your last changes.
255 changes.
[all …]
H A Dusr_07.txt33 file and open the new one. If the current file has unsaved changes, however,
50 Or you can force Vim to discard your changes and edit the new file, using the
55 If you want to edit another file, but not write the changes in the current
60 The text with changes is still there, but you can't see it. This is further
76 If you have unsaved changes in the current file, you will get an error
78 ":edit" mentioned in the previous section. To abandon the changes: >
164 has changes, you can either write the file first, or use ":args!" (with !
165 added) to abandon the changes.
310 If you make further changes to the file, Vim will notice that
429 If you really want to forbid making changes in a file, do this: >
[all …]
H A Dvimdiff.man18 nice way to inspect changes and to move changes from one version to an‐
29 without changes in a fold. 'foldcolumn' is set to two to make it easy
H A Dusr_08.txt79 windows has changes, you will get an error message and that window won't be
286 This stands for "quit all". If any of the windows contain changes, Vim will
288 changes. You can then either use ":write" to save the changes, or ":quit!" to
291 If you know there are windows with changes, and you want to save all these
292 changes, use this command: >
297 changes. Vim knows it doesn't make sense to write files that were not
305 Finally, there is a command that quits Vim and throws away all changes: >
437 changes. Use this command to jump forward to the next change: >
471 Since there are no changes left now, Vim puts all text in a closed fold.
586 changes in the current tab page.
[all …]
H A Dediting.txt222 Edit {file} always. Discard any changes to the
619 the first one. Discard any changes to the current
693 changes to the current buffer. When [count] is
703 Edit [count] next file, discard any changes to the
714 fails when changes have been made and Vim does not
720 any changes to the buffer. Also see |++opt| and
1139 Like ":wq", but write only when changes have been
1170 :qa[ll]! Exit Vim. Any changes to buffers are lost.
1314 On MS-Windows this also changes the active drive.
1477 changes.
[all …]
H A Dusr_toc.txt14 |usr_04.txt| Making small changes
20 |usr_10.txt| Making big changes
92 |usr_04.txt| Making small changes
148 |usr_10.txt| Making big changes
280 |32.2| Numbering changes
H A Dusr_31.txt85 changes. If you do something that might be a bad thing to do, Vim produces an
89 For example, you are editing a file and made changes to it. You start
98 | ? Save changes to "bar.txt"? |
103 Now make your choice. If you do want to save the changes, select "YES". If
104 you want to lose the changes for ever: "NO". If you forgot what you were
106 the same file, with the changes still there.
127 < Save changes to "Untitled"? ~
H A Dusr_04.txt5 Making small changes
78 it leaves you in Insert mode. For example, "cw" changes a word. Or more
106 Like "dd" deletes a whole line, "cc" changes a whole line. It keeps the
109 Just like "d$" deletes until the end of the line, "c$" changes until the end
180 The "." command works for all changes you make, except for "u" (undo), CTRL-R
198 To delete simple items the operator-motion changes work quite well. But often
226 When you move left or right nothing changes. When you move up or down the
409 Using text objects is the third way to make changes in Vim. We already had
497 There are a few common commands to make changes that didn't fit somewhere
503 command. It does work in Visual mode, where it changes case
H A Dos_vms.txt20 9. VMS related changes |vms-changes|
766 9. VMS related changes *vms-changes*
778 - make necessary changes to build v8.1 on VMS
783 - minor VMS port related changes
811 - minor changes in vimrc (just in VMS runtime)
852 - Make file changes
864 - Make file changes
876 - menu changes (fixed printing, CTAGS and XXD usage)
905 - VMS filename related changes:
950 - Minor changes in the code
[all …]
H A Ddevelop.txt163 These are the rules to use when making changes to the Vim source code. Please
169 MAKING CHANGES *style-changes*
171 The basic steps to make changes to the code:
174 changes will be included). You do need to spend some time learning git,
177 your changes affect the user.
178 3. Make the source code changes.
194 Please don't make changes everywhere to use the C99 features, it causes merge
507 check for a match with the bad word. The changes are deleting a character,
510 matches, possibly with a few changes like with the first mechanism.
515 reducing memory use and being able to try sensible changes. For example, when
[all …]
H A Ddiff.txt74 make changes after loading a file, these will be included in the displayed
75 diffs. You might have to do ":diffupdate" now and then, not all changes are
107 files as well, the results are unpredictable. Vim changes
164 - changes have been made to the text
176 possible to view the changes you have made to a buffer since the file was
192 Vim attempts to keep the differences updated when you make changes to the
194 line and more complicated changes do not cause the differences to be updated.
306 that is triggered by |FileChangedRO| changes buffers the command will fail.
H A Dft_rust.txt137 Compiles and runs the current file. If it has unsaved changes,
157 changes, it will be saved first using |:update|. If the
174 in a new split. If the current file has unsaved changes, it
185 in a new split. If the current file has unsaved changes, it
H A Dmessage.txt258 changes.
263 When the file name changes, Vim tries to rename the |swap-file| as well.
310 changes to: >
447 You are trying to |abandon| a file that has changes. Vim protects you from
452 changes to: >
461 don't throw away changes you really want to keep. You might have forgotten
484 out-of-memory situation. First make sure that any changes are saved. Then
513 changes to: >
617 making changes to a file.
644 - Disable "automatically adjust clock for daylight saving changes".
[all …]
H A Dnetbeans.txt193 responsibility for saving changes to this file and the
194 Vim Controller will no longer know of these changes.
198 Vim normally allows changes to a read-only file and only
200 However, NetBeans does not let you make changes to a file
457 endAtomic End an atomic operation. The changes between "startAtomic"
601 Mark the buffer to report changes to the IDE with the
603 changes.
609 Mark the buffer to stop reporting changes to the IDE.
654 have changes, one if it does have changes.
656 number of buffers with changes. When the result is zero it's
[all …]
H A Dusr_10.txt5 Making big changes
8 In chapter 4 several ways to make small changes were explained. This chapter
9 goes into making changes that are repeated or can affect a large amount of
85 example above, "@a" can do several changes, and move around as well.
87 you to make any changes and then still use "@a" to replay the recorded
152 This command changes the "from" string to the "to" string in the lines
167 By default, the ":substitute" command changes only the first occurrence on
168 each line. For example, the preceding command changes the line:
186 out the last line it changes. The c (confirm) flag tells ":substitute" to ask
203 q Quit; don't make any more changes.
[all …]
/vim-8.2.3635/src/testdir/
H A Dtest_listener.vim35 " the two changes are not merged
169 " two disconnected changes
240 func MyListener(x, bufnr, start, end, added, changes) argument
262 for l:change in a:changes
307 let s:changes = []
308 func s:ExtendList(bufnr, start, end, added, changes) argument
309 call extend(s:changes, a:changes)
317 call assert_equal(2, s:changes->len())
325 unlet s:changes
330 func Listener(bufnr, start, end, added, changes) argument
[all …]
H A Dtest_undo.vim2 " Since this script is sourced we need to explicitly break changes up in
97 " will only undo the last 5 changes, end up with 13 - (5 + 1) = 7 lines
106 " will only undo the last 2 changes, end up with 13 - (2 + 1) = 10 lines
204 " 1 leaf (2 changes).
208 call assert_match("^\nnumber changes when *saved\n *2 *2 .*$", a)
214 call assert_match("^\nnumber changes when *saved\n *2 *2 *.*\n *3 *2 .*$", a)
555 " Explicitly break changes up in undo-able pieces by setting 'undolevels'.
/vim-8.2.3635/runtime/spell/
H A DREADME.txt58 Every language should have a maintainer. His tasks are to track the changes
64 find out what changed and take over these changes in your patch. When there
65 are very many changes you can do it the other way around: re-apply the changes
87 too big you might consider writing a Vim script to do systematic changes.
95 changes the .new.dic and .new.aff files will appear. You can now figure
H A Dmain.aap29 # changes. Depending on the Vim executable does that, but results in doing it
31 # that they are outdated when it changes.
/vim-8.2.3635/src/libvterm/
H A DREADME12 - Other changes to support embedding in Vim.
21 To merge in changes from Github, do this:
22 - Commit any pending changes.
/vim-8.2.3635/runtime/syntax/
H A Dgitcommit.vim40 syn match gitcommitNoChanges "\%(^# \)\@<=No changes$" contained containedin=gitcommitComment
62 syn match gitcommitWarning "^\%(no changes added to commit\|nothing \%(added \)\=to commit\)\>.*…

1234567891011