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
|
|
|
---
|
|
|
|
|
|
2019-12-12 14:26:14 +08:00
|
|
|
**What did you expect to happen?**
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**What actually happened?**
|
|
|
|
|
...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
**Additional details:**
|
|
|
|
|
- Include a link to your private config
|
|
|
|
|
- Include screenshots/casts of your issue
|
|
|
|
|
- If you mention key sequences, include what commands they're bound to (use `SPC
|
|
|
|
|
h k KEY` or `C-h h k KEY` to inspect keys).
|
|
|
|
|
- Include any warnings or errors logged to \*Messages\* (use `M-x
|
|
|
|
|
view-echo-area-messages` to see it).
|
2019-07-11 23:23:10 +08:00
|
|
|
|
|
|
|
|
<details><pre>
|
2019-12-12 14:26:14 +08:00
|
|
|
If an error message is involved include a backtrace of it.
|
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
|
|
|
|
|
|
|
|
|
2019-12-12 14:26:14 +08:00
|
|
|
**Steps to reproduce:**
|
2019-07-11 03:13:32 +08:00
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
2019-12-12 14:26:14 +08:00
|
|
|
**System information:**
|
2019-07-11 03:13:32 +08:00
|
|
|
<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>
|
