2019-07-11 03:13:32 +08:00
|
|
|
---
|
2019-07-11 23:23:10 +08:00
|
|
|
name: Bug report
|
2019-11-29 04:32:50 +08:00
|
|
|
about: Doom might be misbehaving
|
2019-07-11 23:23:10 +08:00
|
|
|
labels: is:bug
|
2019-07-11 03:13:32 +08:00
|
|
|
title: "[BUG] "
|
2019-07-11 23:23:10 +08:00
|
|
|
assignees: ''
|
2019-07-11 03:13:32 +08:00
|
|
|
---
|
|
|
|
|
|
2019-07-11 23:23:10 +08:00
|
|
|
**Describe the issue**
|
2019-11-29 04:32:50 +08:00
|
|
|
- What did you expect to happen?
|
|
|
|
|
- What actually happened?
|
|
|
|
|
- Do you have screenshots/casts of your issue?
|
|
|
|
|
- What commands are bound to any keys you've referenced? (use `SPC h k` to
|
|
|
|
|
inspect keys)
|
|
|
|
|
- Can you include a link to your private config?
|
|
|
|
|
- Were any warnings or errors logged to \*Messages\* (`SPC h e` or `M-x
|
|
|
|
|
view-echo-area-messages` will open it).
|
2019-07-11 23:23:10 +08:00
|
|
|
|
|
|
|
|
<details><pre>
|
2019-11-29 04:32:50 +08:00
|
|
|
Include a backtrace of the error.
|
2019-07-11 23:23:10 +08:00
|
|
|
|
2019-11-29 04:32:50 +08:00
|
|
|
How to acquire a backtrace:
|
|
|
|
|
https://github.com/hlissner/doom-emacs/blob/develop/docs/getting_started.org#how-to-extract-a-backtrace-from-an-error
|
2019-07-11 23:23:10 +08:00
|
|
|
</pre></details>
|
2019-07-11 03:13:32 +08:00
|
|
|
|
|
|
|
|
|
|
|
|
|
**Steps to reproduce**
|
|
|
|
|
1. Select these example steps,
|
|
|
|
|
2. Delete them,
|
|
|
|
|
3. And replace them with precise steps to reproduce your issue.
|
|
|
|
|
4. Fill in "system information" below.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**System information**
|
|
|
|
|
<details><pre>
|
2019-07-11 23:23:10 +08:00
|
|
|
Place the output of `M-x doom/info` or `~/.emacs.d/bin/doom info` here.
|
2019-07-11 03:13:32 +08:00
|
|
|
</pre></details>
|
