Mercurial > vim

comparison src/README.txt @ 13353:8412df1479a3 v8.0.1550

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.0.1550: various small problems in source files commit https://github.com/vim/vim/commit/792f0e36593d1ec13ccb8a622ca5542c500577b4 Author: Bram Moolenaar <Bram@vim.org> Date: Tue Feb 27 17:27:13 2018 +0100 patch 8.0.1550: various small problems in source files Problem: Various small problems in source files. Solution: Fix the problems.
author Christian Brabandt <cb@256bit.org>
date Tue, 27 Feb 2018 17:30:08 +0100
parents 073ff46fe397
children a6330a49e036
comparison
equal deleted inserted replaced
13352:764ce635fdc7 13353:8412df1479a3
6 You might also want to read ":help development". 6 You might also want to read ":help development".
7 7
8 8
9 JUMPING AROUND 9 JUMPING AROUND
10 10
11 First of all, use ":make tags" to generate a tags file, so that you can use 11 First of all, use ":make tags" to generate a tags file, so that you can jump
12 the ":tag" command to jump around the source code. 12 around in the source code.
13 13
14 To jump to a function or variable definition, move the cursor on the name and 14 To jump to a function or variable definition, move the cursor on the name and
15 use the CTRL-] command. Use CTRL-T or CTRL-O to jump back. 15 use the CTRL-] command. Use CTRL-T or CTRL-O to jump back.
16 16
17 To jump to a file, move the cursor on its name and use the "gf" command. 17 To jump to a file, move the cursor on its name and use the "gf" command.
39 syntax.c syntax and other highlighting 39 syntax.c syntax and other highlighting
40 tag.c tags 40 tag.c tags
41 term.c terminal handling, termcap codes 41 term.c terminal handling, termcap codes
42 undo.c undo and redo 42 undo.c undo and redo
43 window.c handling split windows 43 window.c handling split windows
44
45
46 DEBUGGING
47
48 If you have a reasonable recent version of gdb, you can use the :Termdebug
49 command to debug Vim. See ":help :Termdebug".
50
51 When something is time critical or stepping through code is a hassle, use the
52 channel logging to create a time-stamped log file. Add lines to the code like
53 this:
54 ch_log(NULL, "Value is now %02x", value);
55 After compiling and starting Vim, do:
56 :call ch_logfile('debuglog', 'w')
57 And edit "debuglog" to see what happens. The channel functions already have
58 ch_log() calls, thus you always see that in the log.
44 59
45 60
46 IMPORTANT VARIABLES 61 IMPORTANT VARIABLES
47 62
48 The current mode is stored in "State". The values it can have are NORMAL, 63 The current mode is stored in "State". The values it can have are NORMAL,