update docs for 4.14.1

[i3/i3.github.io] / _docs / debugging

diff --git a/_docs/debugging b/_docs/debugging
index 925618acb9c9610a44b309c06081088bb9482422..8c6b2b7ca5147d577284c4bb0b17745ad943861d 100644 (file)
--- a/_docs/debugging
+++ b/_docs/debugging
@@ -10,7 +10,7 @@ Thank you for being interested in debugging i3. It really means
 something to us to get your bug fixed. If you have any questions about the
 process and/or need further help, do not hesitate to contact us!
 
 something to us to get your bug fixed. If you have any questions about the
 process and/or need further help, do not hesitate to contact us!
 

-== Verify you are using i3 ≥ 4.14
+== Verify you are using i3 ≥ 4.14.1

 
 Only the latest major version of i3 is supported. To verify which version
 you are running, use:
 
 Only the latest major version of i3 is supported. To verify which version
 you are running, use:


@@ -32,8 +32,8 @@ if you can.
 
 4.7-85-g9c15b95 (development version)::
 Your version is 85 commits newer than 4.7, and the git revision of your
 
 4.7-85-g9c15b95 (development version)::
 Your version is 85 commits newer than 4.7, and the git revision of your

-version is +9c15b95+. Go to http://code.i3wm.org/i3/commit/?h=next and see if
-the line "commit" starts with the same revision. If so, you are using the
+version is +9c15b95+. Go to https://github.com/i3/i3/commits/next and see if
+the most recent commit starts with the same revision. If so, you are using the

 latest version.
 
 Development versions of i3 have logging enabled by default and are compiled
 latest version.
 
 Development versions of i3 have logging enabled by default and are compiled


@@ -109,9 +109,9 @@ No matter whether i3 misbehaved in some way without crashing or whether it just
 crashed, the logfile provides all information necessary to debug the problem.
 
 To upload a compressed version of the logfile (for a bugreport), use:
 crashed, the logfile provides all information necessary to debug the problem.
 
 To upload a compressed version of the logfile (for a bugreport), use:

-------------------------------------------------------------------------------
-DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- http://logs.i3wm.org
-------------------------------------------------------------------------------
+-------------------------------------------------------------------------------
+DISPLAY=:0 i3-dump-log | bzip2 -c | curl --data-binary @- https://logs.i3wm.org
+-------------------------------------------------------------------------------

 
 This command does not depend on i3 (it also works while i3 displays
 the crash dialog), but it requires a working X11 connection.
 
 This command does not depend on i3 (it also works while i3 displays
 the crash dialog), but it requires a working X11 connection.


@@ -154,9 +154,9 @@ you found the section which clearly highlights the problem, additional
 information might be necessary to completely diagnose the problem.
 
 When debugging with us in IRC, be prepared to use a so called nopaste service
 information might be necessary to completely diagnose the problem.
 
 When debugging with us in IRC, be prepared to use a so called nopaste service

-such as http://nopaste.info or http://pastebin.com because pasting large
-amounts of text in IRC sometimes leads to incomplete lines (servers have line
-length limitations) or flood kicks.
+such as https://pastebin.com because pasting large amounts of text in IRC
+sometimes leads to incomplete lines (servers have line length limitations) or
+flood kicks.

 
 == Debugging i3bar
 
 
 == Debugging i3bar