|
195
|
1 *diff.txt* For Vim version 7.0aa. Last change: 2005 Mar 08
|
|
7
|
2
|
|
|
3
|
|
|
4 VIM REFERENCE MANUAL by Bram Moolenaar
|
|
|
5
|
|
|
6
|
|
|
7 *diff* *vimdiff* *gvimdiff* *diff-mode*
|
|
|
8 This file describes the +diff feature: Showing differences between two or
|
|
|
9 three versions of the same file.
|
|
|
10
|
|
|
11 The basics are explained in section |08.7| of the user manual.
|
|
|
12
|
|
|
13 1. Starting diff mode |vimdiff|
|
|
|
14 2. Viewing diffs |view-diffs|
|
|
|
15 3. Jumping to diffs |jumpto-diffs|
|
|
|
16 4. Copying diffs |copy-diffs|
|
|
|
17 5. Diff options |diff-options|
|
|
|
18
|
|
|
19 {not in Vi}
|
|
|
20
|
|
|
21 ==============================================================================
|
|
|
22 1. Starting diff mode
|
|
|
23
|
|
|
24 The easiest way to start editing in diff mode is with the "vimdiff" command.
|
|
|
25 This starts Vim as usual, and additionally sets up for viewing the differences
|
|
|
26 between the arguments. >
|
|
|
27
|
|
|
28 vimdiff file1 file2 [file3 [file4]]
|
|
|
29
|
|
|
30 This is equivalent to: >
|
|
|
31
|
|
|
32 vim -d file1 file2 [file3 [file4]]
|
|
|
33
|
|
|
34 You may also use "gvimdiff" or "vim -d -g". The GUI is started then.
|
|
|
35 You may also use "viewdiff" or "gviewdiff". Vim starts in readonly mode then.
|
|
|
36 "r" may be prepended for restricted mode (see |-Z|).
|
|
|
37
|
|
|
38 The second and following arguments may also be a directory name. Vim will
|
|
|
39 then append the file name of the first argument to the directory name to find
|
|
|
40 the file.
|
|
|
41
|
|
|
42 This only works when a standard "diff" command is available. See 'diffexpr'.
|
|
|
43
|
|
|
44 What happens is that Vim opens a window for each of the files. This is like
|
|
|
45 using the |-O| argument. This uses vertical splits. If you prefer horizontal
|
|
|
46 splits add the |-o| argument: >
|
|
|
47
|
|
|
48 vimdiff -o file1 file2 [file3]
|
|
|
49
|
|
|
50 In each of the edited files these options are set:
|
|
|
51
|
|
|
52 'diff' on
|
|
|
53 'scrollbind' on
|
|
|
54 'scrollopt' includes "hor"
|
|
|
55 'wrap' off
|
|
|
56 'foldmethod' "diff"
|
|
|
57 'foldcolumn' 2
|
|
|
58
|
|
|
59 These options are set local to the window. When editing another file they are
|
|
|
60 reset to the global value.
|
|
|
61
|
|
|
62 The differences shown are actually the differences in the buffer. Thus if you
|
|
|
63 make changes after loading a file, these will be included in the displayed
|
|
|
64 diffs. You might have to do ":diffupdate" now and then, not all changes are
|
|
|
65 immediately taken into account.
|
|
|
66
|
|
|
67 In your .vimrc file you could do something special when Vim was started in
|
|
|
68 diff mode. You could use a construct like this: >
|
|
|
69
|
|
|
70 if &diff
|
|
|
71 setup for diff mode
|
|
|
72 else
|
|
|
73 setup for non-diff mode
|
|
|
74 endif
|
|
|
75
|
|
|
76 While already in Vim you can start diff mode in three ways.
|
|
|
77
|
|
|
78 *E98*
|
|
|
79 :diffsplit {filename} *:diffs* *:diffsplit*
|
|
|
80 Open a new window on the file {filename}. The options are set
|
|
|
81 as for "vimdiff" for the current and the newly opened window.
|
|
|
82 Also see 'diffexpr'.
|
|
|
83
|
|
|
84 *:difft* *:diffthis*
|
|
|
85 :diffthis Make the current window part of the diff windows. This sets
|
|
16
|
86 the options like for "vimdiff".
|
|
7
|
87
|
|
|
88 :diffpatch {patchfile} *:diffp* *:diffpatch*
|
|
|
89 Use the current buffer, patch it with the diff found in
|
|
|
90 {patchfile} and open a buffer on the result. The options are
|
|
|
91 set as for "vimdiff".
|
|
|
92 {patchfile} can be in any format that the "patch" program
|
|
|
93 understands or 'patchexpr' can handle.
|
|
|
94 Note that {patchfile} should only contain a diff for one file,
|
|
|
95 the current file. If {patchfile} contains diffs for other
|
|
|
96 files as well, the results are unpredictable. Vim changes
|
|
|
97 directory to /tmp to avoid files in the current directory
|
|
|
98 accidentally being patched. But it may still result in
|
|
|
99 various ".rej" files to be created. And when absolute path
|
|
|
100 names are present these files may get patched anyway.
|
|
|
101
|
|
|
102 To make these commands use a vertical split, prepend |:vertical|. Examples: >
|
|
|
103
|
|
|
104 :vert diffsplit main.c~
|
|
|
105 :vert diffpatch /tmp/diff
|
|
|
106 <
|
|
|
107 *E96*
|
|
|
108 There can be up to four buffers with 'diff' set.
|
|
|
109
|
|
|
110 Since the option values are remembered with the buffer, you can edit another
|
|
|
111 file for a moment and come back to the same file and be in diff mode again.
|
|
16
|
112
|
|
|
113 *:diffo* *:diffoff*
|
|
|
114 :diffoff Switch off diff mode for the current window.
|
|
|
115
|
|
|
116 :diffoff! Switch off diff mode for all windows.
|
|
7
|
117
|
|
16
|
118 The ":diffoff" command resets the relevant options to their default value.
|
|
|
119 This may be different from what the values were before diff mode was started,
|
|
|
120 the old values are not remembered.
|
|
|
121
|
|
|
122 'diff' off
|
|
|
123 'scrollbind' off
|
|
|
124 'scrollopt' without "hor"
|
|
|
125 'wrap' on
|
|
|
126 'foldmethod' "manual"
|
|
|
127 'foldcolumn' 0
|
|
7
|
128
|
|
|
129 ==============================================================================
|
|
|
130 2. Viewing diffs *view-diffs*
|
|
|
131
|
|
|
132 The effect is that the diff windows show the same text, with the differences
|
|
|
133 highlighted. When scrolling the text, the 'scrollbind' option will make the
|
|
|
134 text in other windows to be scrolled as well. With vertical splits the text
|
|
|
135 should be aligned properly.
|
|
|
136
|
|
|
137 The alignment of text will go wrong when:
|
|
|
138 - 'wrap' is on, some lines will be wrapped and occupy two or more screen
|
|
|
139 lines
|
|
|
140 - folds are open in one window but not another
|
|
|
141 - 'scrollbind' is off
|
|
|
142 - changes have been made to the text
|
|
|
143 - "filler" is not present in 'diffopt', deleted/inserted lines makes the
|
|
|
144 alignment go wrong
|
|
|
145
|
|
|
146 All the buffers edited in a window where the 'diff' option is set will join in
|
|
|
147 the diff. This is also possible for hidden buffers. They must have been
|
|
|
148 edited in a window first for this to be possible.
|
|
|
149
|
|
|
150 Since 'diff' is a window-local option, it's possible to view the same buffer
|
|
|
151 in diff mode in one window and "normal" in another window. It is also
|
|
|
152 possible to view the changes you have made to a buffer, but since Vim doesn't
|
|
|
153 allow having two buffers for the same file, you need to make a copy of the
|
|
|
154 original file and diff with that. For example: >
|
|
|
155 :!cp % tempfile
|
|
|
156 :diffsplit tempfile
|
|
|
157
|
|
|
158 A buffer that is unloaded cannot be used for the diff. But it does work for
|
|
|
159 hidden buffers. You can use ":hide" to close a window without unloading the
|
|
195
|
160 buffer. If you don't want a buffer to remain used for the diff do ":set
|
|
|
161 nodiff" before hiding it.
|
|
7
|
162
|
|
|
163 *:diffu* *:diffupdate*
|
|
|
164 Vim attempts to keep the differences updated when you make changes to the
|
|
|
165 text. This mostly takes care of inserted and deleted lines. Changes within a
|
|
|
166 line and more complicated changes do not cause the differences to be updated.
|
|
|
167 To force the differences to be updated use: >
|
|
|
168
|
|
|
169 :diffupdate
|
|
|
170
|
|
|
171
|
|
|
172 Vim will show filler lines for lines that are missing in one window but are
|
|
|
173 present in another. These lines were inserted in another file or deleted in
|
|
|
174 this file. Removing "filler" from the 'diffopt' option will make Vim not
|
|
|
175 display these filler lines.
|
|
|
176
|
|
|
177
|
|
|
178 Folds are used to hide the text that wasn't changed. See |folding| for all
|
|
|
179 the commands that can be used with folds.
|
|
|
180
|
|
|
181 The context of lines above a difference that are not included in the fold can
|
|
|
182 be set with the 'diffopt' option. For example, to set the context to three
|
|
|
183 lines: >
|
|
|
184
|
|
|
185 :set diffopt=filler,context:3
|
|
|
186
|
|
|
187
|
|
|
188 The diffs are highlighted with these groups:
|
|
|
189
|
|
|
190 |hl-DiffAdd| DiffAdd Added (inserted) lines. These lines exist in
|
|
|
191 this buffer but not in another.
|
|
|
192 |hl-DiffChange| DiffChange Changed lines.
|
|
|
193 |hl-DiffText| DiffText Changed text inside a Changed line. Vim
|
|
|
194 finds the first character that is different,
|
|
|
195 and the last character that is different
|
|
|
196 (searching from the end of the line). The
|
|
|
197 text in between is highlighted. This means
|
|
|
198 that parts in the middle that are still the
|
|
|
199 same are highlighted anyway.
|
|
|
200 |hl-DiffDelete| DiffDelete Deleted lines. Also called filler lines,
|
|
|
201 because they don't really exist in this
|
|
|
202 buffer.
|
|
|
203
|
|
|
204 ==============================================================================
|
|
|
205 3. Jumping to diffs *jumpto-diffs*
|
|
|
206
|
|
|
207 Two commands can be used to jump to diffs:
|
|
|
208 *[c*
|
|
|
209 [c Jump backwards to the previous start of a change.
|
|
|
210 When a count is used, do it that many times.
|
|
|
211 *]c*
|
|
|
212 ]c Jump forwards to the next start of a change.
|
|
|
213 When a count is used, do it that many times.
|
|
|
214
|
|
|
215 It is an error if there is no change for the cursor to move to.
|
|
|
216
|
|
|
217 ==============================================================================
|
|
|
218 4. Diff copying *copy-diffs* *E99* *E100* *E101* *E102* *E103*
|
|
|
219
|
|
|
220 There are two commands to copy text from one buffer to another. The result is
|
|
|
221 that the buffers will be equal within the specified range.
|
|
|
222
|
|
|
223 *:diffg* *:diffget*
|
|
|
224 :[range]diffg[et] [bufspec]
|
|
|
225 Modify the current buffer to undo difference with another
|
|
|
226 buffer. If [bufspec] is given, that buffer is used.
|
|
|
227 Otherwise this only works if there is one other buffer in diff
|
|
|
228 mode.
|
|
|
229 See below for [range].
|
|
|
230
|
|
|
231 *:diffpu* *:diffput*
|
|
|
232 :[range]diffpu[t] [bufspec]
|
|
|
233 Modify another buffer to undo difference with the current
|
|
|
234 buffer. Just like ":diffget" but the other buffer is modified
|
|
|
235 instead of the current one.
|
|
|
236 See below for [range].
|
|
|
237
|
|
|
238 *do*
|
|
|
239 do Same as ":diffget" without argument or range. The "o" stands
|
|
|
240 for "obtain" ("dg" can't be used, it could be the start of
|
|
|
241 "dgg"!).
|
|
|
242
|
|
|
243 *dp*
|
|
|
244 dp Same as ":diffput" without argument or range.
|
|
|
245
|
|
|
246 When no [range] is given, the diff at the cursor position or just above it is
|
|
|
247 affected. When [range] is used, Vim tries to only put or get the specified
|
|
|
248 lines. When there are deleted lines, this may not always be possible.
|
|
|
249
|
|
|
250 There can be deleted lines below the last line of the buffer. When the cursor
|
|
|
251 is on the last line in the buffer and there is no diff above this line, the
|
|
|
252 ":diffget" and "do" commands will obtain lines from the other buffer.
|
|
|
253
|
|
|
254 To be able to get those lines from another buffer in a [range] it's allowed to
|
|
|
255 use the last line number plus one. This command gets all diffs from the other
|
|
|
256 buffer: >
|
|
|
257
|
|
|
258 :1,$+1diffget
|
|
|
259
|
|
|
260 Note that deleted lines are displayed, but not counted as text lines. You
|
|
|
261 can't move the cursor into them. To fill the deleted lines with the lines
|
|
|
262 from another buffer use ":diffget" on the line below them.
|
|
|
263
|
|
|
264 The [bufspec] argument above can be a buffer number, a pattern for a buffer
|
|
|
265 name or a part of a buffer name. Examples:
|
|
|
266
|
|
|
267 :diffget Use the other buffer which is in diff mode
|
|
|
268 :diffget 3 Use buffer 3
|
|
|
269 :diffget v2 Use the buffer which matches "v2" and is in
|
|
|
270 diff mode (e.g., "file.c.v2")
|
|
|
271
|
|
|
272 ==============================================================================
|
|
|
273 5. Diff options *diff-options*
|
|
|
274
|
|
|
275 Also see |'diffopt'| and the "diff" item of |'fillchars'|.
|
|
|
276
|
|
|
277
|
|
|
278 FINDING THE DIFFERENCES *diff-diffexpr*
|
|
|
279
|
|
|
280 The 'diffexpr' option can be set to use something else than the standard
|
|
|
281 "diff" program to compare two files and find the differences.
|
|
|
282
|
|
|
283 When 'diffexpr' is empty, Vim uses this command to find the differences
|
|
|
284 between file1 and file2: >
|
|
|
285
|
|
|
286 diff file1 file2 > outfile
|
|
|
287
|
|
|
288 The ">" is replaced with the value of 'shellredir'.
|
|
|
289
|
|
|
290 The output of "diff" must be a normal "ed" style diff. Do NOT use a context
|
|
|
291 diff. This example explains the format that Vim expects: >
|
|
|
292
|
|
|
293 1a2
|
|
|
294 > bbb
|
|
|
295 4d4
|
|
|
296 < 111
|
|
|
297 7c7
|
|
|
298 < GGG
|
|
|
299 ---
|
|
|
300 > ggg
|
|
|
301
|
|
|
302 The "1a2" item appends the line "bbb".
|
|
|
303 The "4d4" item deletes the line "111".
|
|
|
304 The '7c7" item replaces the line "GGG" with "ggg".
|
|
|
305
|
|
|
306 When 'diffexpr' is not empty, Vim evaluates to obtain a diff file in the
|
|
|
307 format mentioned. These variables are set to the file names used:
|
|
|
308
|
|
|
309 v:fname_in original file
|
|
|
310 v:fname_new new version of the same file
|
|
|
311 v:fname_out resulting diff file
|
|
|
312
|
|
|
313 Additionally, 'diffexpr' should take care of "icase" and "iwhite" in the
|
|
|
314 'diffopt' option. 'diffexpr' cannot change the value of 'lines' and
|
|
|
315 'columns'.
|
|
|
316
|
|
|
317 Example (this does almost the same as 'diffexpr' being empty): >
|
|
|
318
|
|
|
319 set diffexpr=MyDiff()
|
|
|
320 function MyDiff()
|
|
|
321 let opt = ""
|
|
|
322 if &diffopt =~ "icase"
|
|
|
323 let opt = opt . "-i "
|
|
|
324 endif
|
|
|
325 if &diffopt =~ "iwhite"
|
|
|
326 let opt = opt . "-b "
|
|
|
327 endif
|
|
|
328 silent execute "!diff -a --binary " . opt . v:fname_in . " " . v:fname_new .
|
|
|
329 \ " > " . v:fname_out
|
|
|
330 endfunction
|
|
|
331
|
|
|
332 The "-a" argument is used to force comparing the files as text, comparing as
|
|
|
333 binaries isn't useful. The "--binary" argument makes the files read in binary
|
|
|
334 mode, so that a CTRL-Z doesn't end the text on DOS.
|
|
|
335
|
|
|
336 *E97*
|
|
|
337 Vim will do a test if the diff output looks alright. If it doesn't, you will
|
|
|
338 get an error message. Possible causes:
|
|
|
339 - The "diff" program cannot be executed.
|
|
|
340 - The "diff" program doesn't produce normal "ed" style diffs (see above).
|
|
|
341 - The 'shell' and associated options are not set correctly. Try if filtering
|
|
|
342 works with a command like ":!sort".
|
|
|
343 - You are using 'diffexpr' and it doesn't work.
|
|
|
344 If it's not clear what the problem is set the 'verbose' option to see more
|
|
|
345 messages.
|
|
|
346
|
|
20
|
347 The self-installing Vim includes a diff program. If you don't have it you
|
|
|
348 might want to download a diff.exe. For example from
|
|
|
349 http://jlb.twu.net/code/unixkit.php.
|
|
|
350
|
|
7
|
351
|
|
|
352 USING PATCHES *diff-patchexpr*
|
|
|
353
|
|
|
354 The 'patchexpr' option can be set to use something else than the standard
|
|
|
355 "patch" program.
|
|
|
356
|
|
|
357 When 'patchexpr' is empty, Vim will call the "patch" program like this: >
|
|
|
358
|
|
|
359 patch -o outfile origfile < patchfile
|
|
|
360
|
|
|
361 This should work fine with most versions of the "patch" program. Note that a
|
|
|
362 CR in the middle of a line may cause problems, it is seen as a line break.
|
|
|
363
|
|
|
364 If the default doesn't work for you, set the 'patchexpr' to an expression that
|
|
|
365 will have the same effect. These variables are set to the file names used:
|
|
|
366
|
|
|
367 v:fname_in original file
|
|
|
368 v:fname_diff patch file
|
|
|
369 v:fname_out resulting patched file
|
|
|
370
|
|
|
371 Example (this does the same as 'patchexpr' being empty): >
|
|
|
372
|
|
|
373 let patchexpr=MyPatch
|
|
|
374 function MyPatch
|
|
|
375 :call system("patch -o " . v:fname_out . " " . v:fname_in .
|
|
|
376 \ " < " . v:fname_diff)
|
|
|
377 endfunction
|
|
|
378
|
|
|
379 Make sure that using the "patch" program doesn't have unwanted side effects.
|
|
|
380 For example, watch out for additionally generated files, which should be
|
|
|
381 deleted. It should just patch the file and nothing else.
|
|
|
382 Vim will change directory to "/tmp" or another temp directory before
|
|
|
383 evaluating 'patchexpr'. This hopefully avoids that files in the current
|
|
|
384 directory are accidentally patched. Vim will also delete files starting with
|
|
|
385 v:fname_in and ending in ".rej" and ".orig".
|
|
|
386
|
|
|
387 vim:tw=78:ts=8:ft=help:norl:
|
