summaryrefslogtreecommitdiff
path: root/gdk/gdk.c
diff options
context:
space:
mode:
authorWilliam Jon McCann <william.jon.mccann@gmail.com>2014-01-27 12:12:55 -0500
committerWilliam Jon McCann <william.jon.mccann@gmail.com>2014-01-29 12:45:49 -0500
commit768bc44081550be18ee19697ed36b5f92298ef11 (patch)
tree8a0600c37dd2cc07fb00426c76922d3e3f1085e5 /gdk/gdk.c
parenta74ea0770dfc3c7feaa156ab26c26b44162d1820 (diff)
downloadgtk+-768bc44081550be18ee19697ed36b5f92298ef11.tar.gz
docs: use |[ ]| instead of <programlisting></programlisting>
https://bugzilla.gnome.org/show_bug.cgi?id=723119
Diffstat (limited to 'gdk/gdk.c')
-rw-r--r--gdk/gdk.c12
1 files changed, 4 insertions, 8 deletions
diff --git a/gdk/gdk.c b/gdk/gdk.c
index a1fee6c476..3bc27f5ef2 100644
--- a/gdk/gdk.c
+++ b/gdk/gdk.c
@@ -502,8 +502,7 @@ gdk_init (int *argc, char ***argv)
*
* A minimal main program for a threaded GTK+ application
* looks like:
- * <informalexample>
- * <programlisting role="C">
+ * |[
* int
* main (int argc, char *argv[])
* {
@@ -522,8 +521,7 @@ gdk_init (int *argc, char ***argv)
*
* return 0;
* }
- * </programlisting>
- * </informalexample>
+ * ]|
*
* Callbacks require a bit of attention. Callbacks from GTK+ signals
* are made within the GTK+ lock. However callbacks from GLib (timeouts,
@@ -534,8 +532,7 @@ gdk_init (int *argc, char ***argv)
*
* Erik Mouw contributed the following code example to
* illustrate how to use threads within GTK+ programs.
- * <informalexample>
- * <programlisting role="C">
+ * |[
* /<!---->*-------------------------------------------------------------------------
* * Filename: gtk-thread.c
* * Version: 0.99.1
@@ -672,8 +669,7 @@ gdk_init (int *argc, char ***argv)
*
* return 0;
* }
- * </programlisting>
- * </informalexample>
+ * ]|
*
* Unfortunately, all of the above documentation holds with the X11
* backend only. With the Win32 or Quartz backends, GDK and GTK+ calls