summaryrefslogtreecommitdiff
path: root/glib/gmessages.c
diff options
context:
space:
mode:
authorArnaud Rebillout <arnaudr@kali.org>2023-05-10 10:11:24 +0700
committerArnaud Rebillout <arnaudr@kali.org>2023-05-10 10:56:44 +0700
commitf722f11e576f56d6029c9d09dcc04c185d34a28a (patch)
tree0be264a294427bd5b3fed9f84d7bc121b52972c3 /glib/gmessages.c
parent20964ad4ab18f5ba01f3bd1625fb9152eb8ca932 (diff)
downloadglib-f722f11e576f56d6029c9d09dcc04c185d34a28a.tar.gz
Rename GTK+ to GTK (mostly comments and documentation)
GTK lost it's '+' suffix back in 2019, according to <https://mail.gnome.org/archives/gtk-devel-list/2019-February/msg00000.html> This commit can be re-generated with: git grep -l GTK+ \ | grep -v -e ^NEWS -e ^glib/tests/collate.c \ | xargs sed -i 's/GTK+/GTK/g' Most of the changes are in comments and documentation.
Diffstat (limited to 'glib/gmessages.c')
-rw-r--r--glib/gmessages.c8
1 files changed, 4 insertions, 4 deletions
diff --git a/glib/gmessages.c b/glib/gmessages.c
index 541b08130..45906a754 100644
--- a/glib/gmessages.c
+++ b/glib/gmessages.c
@@ -241,7 +241,7 @@
* not advisable, as it cannot be filtered against using the `G_MESSAGES_DEBUG`
* environment variable.
*
- * For example, GTK+ uses this in its `Makefile.am`:
+ * For example, GTK uses this in its `Makefile.am`:
* |[
* AM_CPPFLAGS = -DG_LOG_DOMAIN=\"Gtk\"
* ]|
@@ -831,7 +831,7 @@ g_log_set_fatal_mask (const gchar *log_domain,
* | G_LOG_FLAG_RECURSION, my_log_handler, NULL);
* ]|
*
- * This example adds a log handler for all critical messages from GTK+:
+ * This example adds a log handler for all critical messages from GTK:
*
* |[<!-- language="C" -->
* g_log_set_handler ("Gtk", G_LOG_LEVEL_CRITICAL | G_LOG_FLAG_FATAL
@@ -3295,7 +3295,7 @@ g_log_default_handler (const gchar *log_domain,
* Any messages passed to g_print() will be output via
* the new handler. The default handler outputs
* the encoded message to stdout. By providing your own handler
- * you can redirect the output, to a GTK+ widget or a
+ * you can redirect the output, to a GTK widget or a
* log file for example.
*
* Since 2.76 this functions always returns a valid
@@ -3424,7 +3424,7 @@ g_print (const gchar *format,
* Any messages passed to g_printerr() will be output via
* the new handler. The default handler outputs the encoded
* message to stderr. By providing your own handler you can
- * redirect the output, to a GTK+ widget or a log file for
+ * redirect the output, to a GTK widget or a log file for
* example.
*
* Since 2.76 this functions always returns a valid