[glib] Don't use computeroutput tag



commit faa007c8274d786d070884834b080e47a7951fa9
Author: Matthias Clasen <mclasen redhat com>
Date:   Sat Feb 1 12:09:14 2014 -0500

    Don't use computeroutput tag
    
    There was one occurrence of this.

 glib/gbacktrace.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)
---
diff --git a/glib/gbacktrace.c b/glib/gbacktrace.c
index 248e7a3..17ded63 100644
--- a/glib/gbacktrace.c
+++ b/glib/gbacktrace.c
@@ -96,7 +96,7 @@ volatile gboolean glib_on_error_halt = TRUE;
  *     gdk_init() or gtk_init() has been called)
  *
  * Prompts the user with
- * <computeroutput>[E]xit, [H]alt, show [S]tack trace or [P]roceed</computeroutput>.
+ * <literal>[E]xit, [H]alt, show [S]tack trace or [P]roceed</literal>.
  * This function is intended to be used for debugging use only.
  * The following example shows how it can be used together with
  * the g_log() functions.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]