devel-docs: more s/2.9/2.10/

This commit is contained in:
Michael Natterer 2018-04-27 11:02:38 +02:00
parent 9cb91971ea
commit 26c67cf7d2
1 changed files with 3 additions and 3 deletions

View File

@ -19,7 +19,7 @@ comma-separated list of domain.
For instance, for `GIMP_LOG (XCF, "some string")` to be outputted, For instance, for `GIMP_LOG (XCF, "some string")` to be outputted,
run GIMP like this: run GIMP like this:
> GIMP_DEBUG=xcf gimp-2.9 > GIMP_DEBUG=xcf gimp-2.10
Special flags are: Special flags are:
- "all" to output all domain logs; - "all" to output all domain logs;
@ -31,7 +31,7 @@ If you encounter a CRITICAL or WARNING message on console, you can make
so that GIMP crashes on it, which will make it very easy to be tracked so that GIMP crashes on it, which will make it very easy to be tracked
down in a debugger (for instance GDB), by running GIMP with: down in a debugger (for instance GDB), by running GIMP with:
> gimp-2.9 --g-fatal-warnings > gimp-2.10 --g-fatal-warnings
Note that if all you want is a stacktrace, it is not necessary anymore Note that if all you want is a stacktrace, it is not necessary anymore
to use a debugger and --g-fatal-warnings. In Preferences > Debugging, to use a debugger and --g-fatal-warnings. In Preferences > Debugging,
@ -68,7 +68,7 @@ back to the old lcms implementation, which can be useful for comparison.
Make X calls synchronous so that your crashes happen immediately with: Make X calls synchronous so that your crashes happen immediately with:
> gimp-2.9 --sync > gimp-2.10 --sync
You can also break on `gdk_x_error()`. You can also break on `gdk_x_error()`.