From 00570a8645fda869eb106c8803f4e52935aab936 Mon Sep 17 00:00:00 2001 From: David Wells Date: Mon, 14 Sep 2015 10:04:04 -0400 Subject: [PATCH] Fix inconsistencies in our GDB documentation. 1. The GDB documentation consistently uses "pretty-print", not "pretty print". The previous version of this file used both. 2. The folder ".gdbscripts" was not consistently named (it was erroneously referred to as ".gdbfiles" in one place). --- doc/users/gdb.html | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/doc/users/gdb.html b/doc/users/gdb.html index 2ab1f4ae15..6315b13ff7 100644 --- a/doc/users/gdb.html +++ b/doc/users/gdb.html @@ -45,11 +45,11 @@ cp contrib/utilities/dotgdbinit.py ~/.gdbinit

Setting up GDB for deal.II and other sets of printers

- Configuring GDB to use multiple sets of pretty printers (i.e., sets of pretty - printers from deal.II as well as other projects) takes a - little more work. The recommended procedure is + Configuring GDB to use multiple sets of pretty-printers (i.e., sets of + pretty-printers from deal.II as well as other projects) + takes a little more work. The recommended procedure is

    -
  1. Decide on a directory where you will place all of your pretty printing +
  2. Decide on a directory where you will place all of your pretty-printing files. A good choice would be creating a new folder .gdbscripts in your home directory, and this is the choice assumed for the rest of this demonstration. @@ -78,11 +78,11 @@ end
     import deal
    executes the code necessary to enable the deal.II - pretty printers (it loads the file created in the last step). + pretty-printers (it loads the file created in the last step).
- Use a similar procedure on other pretty printing files (which should - also be located in .gdbfiles/) to set up any other pretty - printing code. + Use a similar procedure on other pretty-printing files (which should also be + located in .gdbscripts/) to set up any other pretty-printing + code.


-- 2.39.5