[metacity] replace mutter with metacity
- From: Alberts Muktupāvels <muktupavels src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [metacity] replace mutter with metacity
- Date: Wed, 12 Sep 2018 11:55:07 +0000 (UTC)
commit 92f4cd4e9d939350caa2a60b55b8d36d7c86ea9d
Author: Alberts Muktupāvels <alberts muktupavels gmail com>
Date: Sun Sep 9 20:06:58 2018 +0300
replace mutter with metacity
libmetacity/meta-theme-metacity.c | 2 +-
src/core/above-tab-keycode.c | 4 ++--
src/core/display.c | 2 +-
src/core/window.c | 2 +-
4 files changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/libmetacity/meta-theme-metacity.c b/libmetacity/meta-theme-metacity.c
index aed09cfb..538fd5a8 100644
--- a/libmetacity/meta-theme-metacity.c
+++ b/libmetacity/meta-theme-metacity.c
@@ -3519,7 +3519,7 @@ find_version (const gchar **attribute_names,
/* Returns whether the version element was successfully parsed.
* If successfully parsed, then two additional items are returned:
*
- * satisfied: whether this version of Mutter meets the version check
+ * satisfied: whether this version of Metacity meets the version check
* minimum_required: minimum version of theme format required by version check
*/
static gboolean
diff --git a/src/core/above-tab-keycode.c b/src/core/above-tab-keycode.c
index e980f522..8f03dd33 100644
--- a/src/core/above-tab-keycode.c
+++ b/src/core/above-tab-keycode.c
@@ -30,12 +30,12 @@
* implemented here, but unfortunately, fetching the geometry is rather
* slow (It could take 20ms or more.)
*
- * If you looking for a way to optimize Mutter startup performance:
+ * If you looking for a way to optimize Metacity startup performance:
* On all Linux systems using evdev the key above TAB will have
* keycode 49. (KEY_GRAVE=41 + the 8 code point offset between
* evdev keysyms and X keysyms.) So a configure option
* --with-above-tab-keycode=49 could be added that bypassed this
- * code. It wouldn't work right for displaying Mutter remotely
+ * code. It wouldn't work right for displaying Metacity remotely
* to a non-Linux X server, but that is pretty rare.
*/
diff --git a/src/core/display.c b/src/core/display.c
index b048f5f4..ed0aaf7f 100644
--- a/src/core/display.c
+++ b/src/core/display.c
@@ -1503,7 +1503,7 @@ request_xserver_input_focus_change (MetaDisplay *display,
meta_error_trap_push (display);
- /* In order for mutter to know that the focus request succeeded, we track
+ /* In order for Metacity to know that the focus request succeeded, we track
* the serial of the "focus request" we made, but if we take the serial
* of the XSetInputFocus request, then there's no way to determine the
* difference between focus events as a result of the SetInputFocus and
diff --git a/src/core/window.c b/src/core/window.c
index 325f9294..3cd5c654 100644
--- a/src/core/window.c
+++ b/src/core/window.c
@@ -1208,7 +1208,7 @@ meta_window_unmanage (MetaWindow *window,
}
/* If we're unmanaging a window that is not withdrawn, then
- * either (a) mutter is exiting, in which case we need to map
+ * either (a) Metacity is exiting, in which case we need to map
* the window so the next WM will know that it's not Withdrawn,
* or (b) we want to create a new MetaWindow to replace the
* current one, which will happen automatically if we re-map
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]