diff options
| -rw-r--r-- | .github/ISSUE_TEMPLATE/bug_report.yml | 6 | ||||
| -rw-r--r-- | CONTRIBUTING.md | 1 |
2 files changed, 4 insertions, 3 deletions
diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml index fa8d05f6b5..11f27dde21 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.yml +++ b/.github/ISSUE_TEMPLATE/bug_report.yml @@ -36,7 +36,7 @@ body: - type: input attributes: label: "$TERM environment variable" - placeholder: "echo $TERM" + placeholder: "xterm-256color" validations: required: true @@ -52,11 +52,11 @@ body: attributes: label: "How to reproduce the issue" description: | - - Steps to reproduce using `nvim -u NORC` or `nvim -u NONE` (try both). + - Steps to reproduce using `nvim --clean` ("factory defaults"). - For build failures: list the exact steps including CMake flags (if any). - For shell-related problems: try `env -i TERM=ansi-256color "$(which nvim)"`. placeholder: | - nvim -u NONE + nvim --clean :edit foo yiwp validations: diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index fe3540f1f6..e9c1173007 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -19,6 +19,7 @@ Reporting problems - [Check the FAQ][wiki-faq]. - [Search existing issues][github-issues] (including closed!) - Update Neovim to the latest version to see if your problem persists. +- Try to reproduce with `nvim --clean` ("factory defaults"). - [Bisect](https://neovim.io/doc/user/starting.html#bisect) your config: disable plugins incrementally, to narrow down the cause of the issue. - [Bisect][git-bisect] Neovim's source code to find the cause of a regression, if you can. This is _extremely_ helpful. - When reporting a crash, [include a stacktrace](https://github.com/neovim/neovim/wiki/FAQ#backtrace-linux). |