Update info on connecting to existing notebook kernels with qtconsole.

docs/source/interactive/htmlnotebook.txt

@@ -132,15 +132,31 b' console, is that it can not run any code that expects input from the kernel'
 that the ``%debug`` magic does *not* work in the notebook!  We intend to
 correct this limitation, but in the meantime, there is a way to debug problems
 in the notebook: you can attach a Qt console to your existing notebook kernel,
-and run ``%debug`` from the Qt console.  Simply look for the lines in the
-terminal where you started the kernel that read something like::
+and run ``%debug`` from the Qt console.  If your notebook is running on a local
+computer (i.e. if you are accessing it via your localhost address at
+127.0.0.1), you can just type ``%qtconsole`` in the notebook and a Qt console
+will open up connected to that same kernel.
+
+In general, the notebook server prints the full details of how to connect to
+each kernel at the terminal, with lines like:
 
     [IPKernelApp] To connect another client to this kernel, use:
-    [IPKernelApp] --existing --shell=53328 --iopub=53817 --stdin=34736 --hb=45543
+    [IPKernelApp] --existing kernel-3bb93edd-6b5a-455c-99c8-3b658f45dde5.json
+
+This is the name of a JSON file that contains all the port and validation
+information necessary to connect to the kernel.  You can manually start a
+qt console with::
+
+    ipython qtconsole --existing kernel-3bb93edd-6b5a-455c-99c8-3b658f45dde5.json
+
+and if you only have a single kernel running, simply typing::
 
-and then start a qt console pointing to that kernel::
+    ipython qtconsole --existing
 
-    ipython qtconsole --existing --shell=53328 --iopub=53817 --stdin=34736 --hb=45543
+will automatically find it (it will always find the most recently started
+kernel if there is more than one).  You can also request this connection data
+by typing ``%connect_info``; this will print the same file information as well
+as the content of the JSON data structure it contains.
 
     
 Text input