Mercurial > vim

comparison runtime/doc/intro.txt @ 20753:661eb972cb22

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Update runtime files Commit: https://github.com/vim/vim/commit/acc224064033e5cea21ef7f1eefb356ca06ff11d Author: Bram Moolenaar <Bram@vim.org> Date: Sun Jun 7 21:07:18 2020 +0200 Update runtime files
author Bram Moolenaar <Bram@vim.org>
date Sun, 07 Jun 2020 21:15:04 +0200
parents af69c9335223
children bbca88cd13d5
comparison
equal deleted inserted replaced
20752:47b5de84b7f7 20753:661eb972cb22
1 *intro.txt* For Vim version 8.2. Last change: 2019 Nov 11 1 *intro.txt* For Vim version 8.2. Last change: 2020 May 30
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
119 http://www.vim.org/maillist.php 119 http://www.vim.org/maillist.php
120 120
121 121
122 Bug reports: *bugs* *bug-reports* *bugreport.vim* 122 Bug reports: *bugs* *bug-reports* *bugreport.vim*
123 123
124 There are two ways to report bugs, both work: 124 There are three ways to report bugs:
125 1. Send bug reports to: Vim Developers <vim-dev@vim.org> 125 1. Open an issue on GitHub: https://github.com/vim/vim/issues
126 The text will be forwarded to the vim-dev maillist.
127 2. For issues with runtime files, look in the header for an email address or
128 any other way to report it to the maintainer.
129 3. Send bug reports to: Vim Developers <vim-dev@vim.org>
126 This is a maillist, you need to become a member first and many people will 130 This is a maillist, you need to become a member first and many people will
127 see the message. If you don't want that, e.g. because it is a security 131 see the message. If you don't want that, e.g. because it is a security
128 issue, send it to <bugs@vim.org>, this only goes to the Vim maintainer 132 issue, send it to <bugs@vim.org>, this only goes to the Vim maintainer
129 (that's Bram). 133 (that's Bram).
130 2. Open an issue on GitHub: https://github.com/vim/vim/issues
131 The text will be forwarded to the vim-dev maillist.
132 134
133 Please be brief; all the time that is spent on answering mail is subtracted 135 Please be brief; all the time that is spent on answering mail is subtracted
134 from the time that is spent on improving Vim! Always give a reproducible 136 from the time that is spent on improving Vim! Always give a reproducible
135 example and try to find out which settings or other things trigger the bug. 137 example and try to find out which settings or other things trigger the bug.
136 138