Mercurial > vim

comparison CONTRIBUTING.md @ 16208:a23c883685cb

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/723dd946f94856be94a943876945fb1bd8169059 Author: Bram Moolenaar <Bram@vim.org> Date: Thu Apr 4 13:11:03 2019 +0200 Update runtime files.
author Bram Moolenaar <Bram@vim.org>
date Thu, 04 Apr 2019 13:15:07 +0200
parents 2a4a2dc35c55
children e71261a88630
comparison
equal deleted inserted replaced
16207:7e3a172a7f09 16208:a23c883685cb
19 We use GitHub issues, but that is not a requirement. Writing to the Vim 19 We use GitHub issues, but that is not a requirement. Writing to the Vim
20 maillist is also fine. 20 maillist is also fine.
21 21
22 Please use the GitHub issues only for actual issues. If you are not 100% sure 22 Please use the GitHub issues only for actual issues. If you are not 100% sure
23 that your problem is a Vim issue, please first discuss this on the Vim user 23 that your problem is a Vim issue, please first discuss this on the Vim user
24 maillist. Try reproducing the problem without any plugins or settings: 24 maillist. Try reproducing the problem without any of your plugins or settings:
25 25
26 vim -N -u NONE 26 vim --clean
27 27
28 If you report an issue, please describe exactly how to reproduce it. 28 If you report an issue, please describe exactly how to reproduce it.
29 For example, don't say "insert some text" but say what you did exactly: 29 For example, don't say "insert some text" but say what you did exactly:
30 "ahere is some text&lt;Esc&gt;". 30 "ahere is some text&lt;Esc&gt;".
31 Ideally, the steps you list can be used to write a test to verify the problem 31 Ideally, the steps you list can be used to write a test to verify the problem