[Pkg-mozext-commits] [itsalltext] 399/459: Bill von Hagen's suggestions for DEBUG.mk

David Prévot taffit at moszumanska.debian.org
Tue Feb 24 23:26:42 UTC 2015


This is an automated email from the git hooks/post-receive script.

taffit pushed a commit to branch master
in repository itsalltext.

commit d5d2f606b6bc0a514efe574f57acaf39c9e47ba7
Author: Christian Höltje <docwhat at gerf.org>
Date:   Thu Sep 22 09:59:04 2011 -0400

    Bill von Hagen's suggestions for DEBUG.mk
---
 DEBUGGING.md | 16 ++++++++++------
 1 file changed, 10 insertions(+), 6 deletions(-)

diff --git a/DEBUGGING.md b/DEBUGGING.md
index eb92039..50cc9fd 100644
--- a/DEBUGGING.md
+++ b/DEBUGGING.md
@@ -3,13 +3,13 @@
 
 Thank you for considering helping me debug a problem with [It's All Text!](http://github.com/docwhat/itsalltext).
 
-This document will help you set up debugging and then remove it once you're done.  You'll probably want to remove some of these debugging methods when you finish because it slows down Firefox.  Unless you debug regularly (you're a web or extension developer) you probably don't need these tools day-to-day.
+This document will help you set up debugging and then remove it once you're done.  You'll probably want to undo some of the debugging when you finish because it slows down Firefox.  Unless you debug regularly (you're a web or extension developer) you probably don't need these tools day-to-day.
 
 ## Preparation
 
 You may want to save a copy of this document to disk or open it in a different browser so you can read it while you're restarting and debugging Firefox.
 
-You'll also want at text editor or an open email to collect any interesting information.
+You'll also want a text editor or a new open email to collect any interesting information.
 
 ### Setting up a new profile (optional)
 
@@ -19,12 +19,12 @@ There are several advantages to setting up a new profile for debugging IAT:
 
 1. You won't change your normal settings.
 2. Cleanup is easy, just switch profiles back to your normal profile.
-3. It makes debugging problems caused by extensions interacting with IAT.
+3. It makes debugging problems caused by extensions interacting with IAT possible without destroying your day-to-day profile.
 4. You start with default settings for your platform.
 
 If this sounds good to you, then go read the [managing profiles article](http://support.mozilla.com/en-US/kb/Managing-profiles) in the Mozilla knowledge-base.
 
-Once you've set up a new debugging profile and are running it by restarting Firefox, then you'll want to go install the version of It's All Text! you'll be debugging.  You should have either gotten an `.xpi` file directly from Christian Höltje or you can get any previously released version from [Addons.Mozzilla.Org](https://addons.mozilla.org/en-US/firefox/addon/its-all-text/versions/).
+Once you've set up a new debugging profile and are running it by restarting Firefox and activating that profile you'll want to go install the version of It's All Text! you'll be debugging.  You should have either gotten an `.xpi` file directly from Christian Höltje or you can get any previously released version from [Addons.Mozilla.Org](https://addons.mozilla.org/en-US/firefox/addon/its-all-text/versions/).
 
 The TL;DR version is to run the following command (for Windows and Linux only, alas):
 
@@ -48,13 +48,13 @@ You open the Error Console via <kbd>CTRL</kbd>+<kbd>SHIFT</kdb>+<kbd>J</kbd>.
 
 1. Verify that it is set to show "all" errors, messages, etc.  Click the "all" tab/button.
 2. Check the Error Console for any errors from It's All Text! during startup.  If there are any, then you should copy and paste them into your notes and mark them as start-up errors.
-3. Clear the console. This is to make finding problems easier.
+3. Clear the console. This is to make finding subsequent problems easier.
 
 ### Debug
 
 If you're debugging "normal usage" of IAT, then you can go to [http://docwhat.org/files/iat] and walk through those tests one by one.
 
-After each step check your Error Console and see if any errors from IAT have appeared.  Make note of any that do appear.  It's okay to record too much, we can clean up the info later.
+After each step check your Error Console and see if any errors from IAT have appeared and make a note of them.  It's okay to record too much, we can clean up the info later.
 
 You may want to clear the Error Console regularly to make finding new messages easier.
 
@@ -155,6 +155,10 @@ If you're proficient enough to do this, I won't need to explain too much to you.
 
 You'll also want to install [Venkman](https://developer.mozilla.org/en/Venkman), even if you use Firebug to do JS debugging.
 
+Since you are knowledgable enough to be using a debugger, I assume you'll figure out how to continue from here.
+
+The latest source (and tagged releases) are all on [github](http://github.com/docwhat/itsalltext).
+
 ## Getting Help
 
 You can contact me via [email](http://docwhat.org/email/) or via IM or IRC.  See [my homepage](http://docwhat.org/) for my "Alter Egos" (in the sidebar) to find a way to talk to me directly.

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-mozext/itsalltext.git



More information about the Pkg-mozext-commits mailing list