vim/UltiSnips
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add note about contributing to traceback (#969)

Browse Source 
There too many issues with traceback only. While it is good to have traceback, it is sell useful when it is the only info in the issue description. I think that contributing manual should be mentioned here even if we have issue template now. At least further new issues with traceback may follow contributing guide.
This commit is contained in:
Andrey Orst 2018-04-11 22:55:30 +03:00 committed by UltiBot
parent f4304d59cc
commit 943156d879
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
pythonx/UltiSnips/err_to_scratch_buffer.py
View File

@ -18,7 +18,9 @@ def wrap(func):
msg = \ msg = \
"""An error occured. This is either a bug in UltiSnips or a bug in a """An error occured. This is either a bug in UltiSnips or a bug in a
snippet definition. If you think this is a bug, please report it to snippet definition. If you think this is a bug, please report it to
https://github.com/SirVer/ultisnips/issues/new. https://github.com/SirVer/ultisnips/issues/new
Please read and follow:
https://github.com/SirVer/ultisnips/blob/master/CONTRIBUTING.md#reproducing-bugs
Following is the full stack trace: Following is the full stack trace:
""" """