Mercurial > vim

comparison runtime/doc/debug.txt @ 11666:5cd9ba96561d v8.0.0716

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 8.0.0716: not easy to start Vim cleanly commit https://github.com/vim/vim/commit/c4da113ef98dcfd6f2a088b1693c0317dcb5bf42 Author: Bram Moolenaar <Bram@vim.org> Date: Sat Jul 15 19:39:43 2017 +0200 patch 8.0.0716: not easy to start Vim cleanly Problem: Not easy to start Vim cleanly without changing the viminfo file. Not possible to know whether the -i command line flag was used. Solution: Add the --clean command line argument. Add the 'viminfofile' option. Add "-u DEFAULTS".
author Christian Brabandt <cb@256bit.org>
date Sat, 15 Jul 2017 19:45:03 +0200
parents 9f48eab77d62
children 1174611ad715
comparison
equal deleted inserted replaced
11665:d7fe6dc88ea4 11666:5cd9ba96561d
1 *debug.txt* For Vim version 8.0. Last change: 2012 Feb 11 1 *debug.txt* For Vim version 8.0. Last change: 2017 Jul 15
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
51 Use this command to start Vim: 51 Use this command to start Vim:
52 > 52 >
53 valgrind --log-file=valgrind.log --leak-check=full ./vim 53 valgrind --log-file=valgrind.log --leak-check=full ./vim
54 54
55 Note: Vim will run much slower. If your .vimrc is big or you have several 55 Note: Vim will run much slower. If your .vimrc is big or you have several
56 plugins you need to be patient for startup, or run with the "-u NONE" 56 plugins you need to be patient for startup, or run with the "--clean"
57 argument. 57 argument.
58 58
59 There are often a few leaks from libraries, such as getpwuid() and 59 There are often a few leaks from libraries, such as getpwuid() and
60 XtVaAppCreateShell(). Those are unavoidable. The number of bytes should be 60 XtVaAppCreateShell(). Those are unavoidable. The number of bytes should be
61 very small a Kbyte or less. 61 very small a Kbyte or less.