diff options
| author | Bram Moolenaar <Bram@vim.org> | 2005-09-01 20:46:49 +0000 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2005-09-01 20:46:49 +0000 |
| commit | e344bead3ecc16a0982d157e8c19050f6dff4e0c (patch) | |
| tree | 34da48120172b9e2efc8c559733c2b69db5a24ba /runtime/doc/intro.txt | |
| parent | da2303d96b0f55d30e9b5b57d3459d5e1ea22ec2 (diff) | |
| download | vim-git-e344bead3ecc16a0982d157e8c19050f6dff4e0c.tar.gz | |
updated for version 7.0140v7.0140
Diffstat (limited to 'runtime/doc/intro.txt')
| -rw-r--r-- | runtime/doc/intro.txt | 28 |
1 files changed, 8 insertions, 20 deletions
diff --git a/runtime/doc/intro.txt b/runtime/doc/intro.txt index 3f8e35d5b..89f020c50 100644 --- a/runtime/doc/intro.txt +++ b/runtime/doc/intro.txt @@ -1,4 +1,4 @@ -*intro.txt* For Vim version 7.0aa. Last change: 2005 Jun 12 +*intro.txt* For Vim version 7.0aa. Last change: 2005 Sep 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -151,31 +151,19 @@ example and try to find out which settings or other things influence the appearance of the bug. Try different machines, if possible. Send me patches if you can! -In case of doubt, use: > +It will help to include information about the version of Vim you are using and +your setup. You can get the information with this command: > :so $VIMRUNTIME/bugreport.vim This will create a file "bugreport.txt" in the current directory, with a lot of information of your environment. Before sending this out, check if it doesn't contain any confidential information! - *debug-vim* -When Vim crashes in one of the test files, and you are using gcc for -compilation, here is what you can do to find out exactly where Vim crashes: +If Vim crashes, please try to find out where. You can find help on this here: +|debug.txt|. -1. Compile Vim with the "-g" option (there is a line in the Makefile for this, - which you can uncomment). - -2. Execute these commands (replace "11" with the test that fails): > - cd testdir - gdb ../vim - run -u unix.vim -U NONE -s dotest.in test11.in - -3. Check where Vim crashes, gdb should give a message for this. - -4. Get a stack trace from gdb with this command: > - where -< You can check out different places in the stack trace with: > - frame 3 -< Replace "3" with one of the numbers in the stack trace. +In case of doubt or when you wonder if the problem has already been fixed but +you can't find a fix for it, become a member of the vim-dev maillist and ask +your question there. |maillist| *year-2000* *Y2K* Since Vim internally doesn't use dates for editing, there is no year 2000 |