[glib] Use a code block instead of <screen>
- From: Matthias Clasen <matthiasc src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [glib] Use a code block instead of <screen>
- Date: Thu, 6 Feb 2014 13:07:33 +0000 (UTC)
commit 49c2223ee610a14a0101958acb634e37f5521ca8
Author: Matthias Clasen <mclasen redhat com>
Date: Wed Feb 5 22:01:54 2014 -0500
Use a code block instead of <screen>
glib/goption.c | 4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/glib/goption.c b/glib/goption.c
index da04596..17c35de 100644
--- a/glib/goption.c
+++ b/glib/goption.c
@@ -59,7 +59,7 @@
* #GOptionGroup) and write a text similar to the one shown in the
* following example to stdout.
*
- * <informalexample><screen>
+ * |[
* Usage:
* testtreemodel [OPTION...] - test tree model performance
*
@@ -75,7 +75,7 @@
* -v, --verbose Be verbose
* -b, --beep Beep when done
* --rand Randomize the data
- * </screen></informalexample>
+ * ]|
*
* GOption groups options in #GOptionGroups, which makes it easy to
* incorporate options from multiple sources. The intended use for this is
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]