All patches and comments are welcome. Please squash your changes to logical
commits before using git-format-patch and git-send-email to
patches@git.madduck.net.
If you'd read over the Git project's submission guidelines and adhered to them,
I'd be especially grateful.
4 about: Report a bug with ALE.
9 This is the template for reporting ALE bugs. Make sure you try updating ALE
10 to a more recent version before reporting a bug. Look through existing bug
11 reports for similar issues before reporting a new one. Don't leave comments
12 about new bugs in the comment section for old issues.
14 Make sure to try disabling other plugins and trying to repeat your bug before
15 reporting it in ALE. Some times problems can arise when two plugins are used
16 together, but often your issues might be problems with other plugins.
23 <!-- Paste just the first two lines of :version here. -->
25 Operating System: <!-- Describe your operating system version. -->
29 <!-- Describe what went wrong here. Be specific. -->
31 Something went wrong in specifically this place, and I also searched through both open and closed issues for the same problem before reporting a bug here.
33 Are you having trouble configuring ALE? Try asking for help on [Stack Exchange](https://vi.stackexchange.com/) or perhaps on [Reddit](https://www.reddit.com/r/vim/) instead. The GitHub issue tracker should be used for reporting bugs or asking for new features.
35 ## Reproducing the bug
37 <!-- Write a list of steps below. -->
40 2. Then this happened.
44 <summary>Expand</summary>
45 <!-- Paste the output of :ALEInfo here. Try :ALEInfo -clipboard -->
46 <!-- Make sure to run :ALEInfo from the buffer where the bug occurred. -->
47 <!-- Read the output. You might figure out what went wrong yourself. -->