aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLibravatar Brian Ashworth <bosrsf04@gmail.com>2020-04-29 01:16:35 -0400
committerLibravatar Simon Ser <contact@emersion.fr>2020-04-29 08:33:20 +0200
commit8fd450db16e70ee2983d7e31d87575ba020920ba (patch)
tree085d9881ef132f27581d7886df144758851be904
parentRedirect questions to wiki/IRC (diff)
downloadsway-8fd450db16e70ee2983d7e31d87575ba020920ba.tar.gz
sway-8fd450db16e70ee2983d7e31d87575ba020920ba.tar.zst
sway-8fd450db16e70ee2983d7e31d87575ba020920ba.zip
ISSUE_TEMPLATE: note debug logs should be from TTY
It is common for user to attach a debug log from the Wayland backend because they are running the command from inside of Sway. This just adds a note that the debug logs should be obtained from a TTY. Anyone who is actually using the Wayland or X11 backends and submitting an issue related to them likely is already familiar with how to obtain a debug log for the appropriate backend.
-rw-r--r--ISSUE_TEMPLATE.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
index f3553c40..4b715aeb 100644
--- a/ISSUE_TEMPLATE.md
+++ b/ISSUE_TEMPLATE.md
@@ -21,7 +21,7 @@ If this doesn't work, use:
21 21
22* Sway Version: 22* Sway Version:
23 23
24Obtain a debug log like so: 24Obtain a debug log by running the following command from a TTY:
25 25
26 sway -d 2> ~/sway.log 26 sway -d 2> ~/sway.log
27 27