From: Masahiro Yamada <masahiroy@kernel.org>
To: linux-kbuild@vger.kernel.org
Cc: Masahiro Yamada <masahiroy@kernel.org>, linux-kernel@vger.kernel.org
Subject: [PATCH 4/6] kconfig: gconf: use hyphens in signals
Date: Thu, 17 Jul 2025 08:24:11 +0900 [thread overview]
Message-ID: <20250716232542.873747-4-masahiroy@kernel.org> (raw)
In-Reply-To: <20250716232542.873747-1-masahiroy@kernel.org>
Using hyphens in signal names is the official convention, even though
underscores also work.
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
---
scripts/kconfig/gconf.c | 14 +++++++-------
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/scripts/kconfig/gconf.c b/scripts/kconfig/gconf.c
index d9ea71664412..e4f89270d19f 100644
--- a/scripts/kconfig/gconf.c
+++ b/scripts/kconfig/gconf.c
@@ -997,25 +997,25 @@ static void init_main_window(const gchar *glade_file)
G_CALLBACK(on_window1_destroy), NULL);
g_signal_connect(main_wnd, "configure-event",
G_CALLBACK(on_window1_configure), NULL);
- g_signal_connect(main_wnd, "delete_event",
+ g_signal_connect(main_wnd, "delete-event",
G_CALLBACK(on_window1_delete_event), NULL);
hpaned = GTK_WIDGET(gtk_builder_get_object(builder, "hpaned1"));
vpaned = GTK_WIDGET(gtk_builder_get_object(builder, "vpaned1"));
tree1_w = GTK_WIDGET(gtk_builder_get_object(builder, "treeview1"));
- g_signal_connect(tree1_w, "cursor_changed",
+ g_signal_connect(tree1_w, "cursor-changed",
G_CALLBACK(on_treeview2_cursor_changed), NULL);
- g_signal_connect(tree1_w, "button_press_event",
+ g_signal_connect(tree1_w, "button-press-event",
G_CALLBACK(on_treeview1_button_press_event), NULL);
- g_signal_connect(tree1_w, "key_press_event",
+ g_signal_connect(tree1_w, "key-press-event",
G_CALLBACK(on_treeview2_key_press_event), NULL);
tree2_w = GTK_WIDGET(gtk_builder_get_object(builder, "treeview2"));
- g_signal_connect(tree2_w, "cursor_changed",
+ g_signal_connect(tree2_w, "cursor-changed",
G_CALLBACK(on_treeview2_cursor_changed), NULL);
- g_signal_connect(tree2_w, "button_press_event",
+ g_signal_connect(tree2_w, "button-press-event",
G_CALLBACK(on_treeview2_button_press_event), NULL);
- g_signal_connect(tree2_w, "key_press_event",
+ g_signal_connect(tree2_w, "key-press-event",
G_CALLBACK(on_treeview2_key_press_event), NULL);
text_w = GTK_WIDGET(gtk_builder_get_object(builder, "textview3"));
--
2.43.0
next prev parent reply other threads:[~2025-07-16 23:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 23:24 [PATCH 1/6] kconfig: gconf: fix single view to display dependent symbols correctly Masahiro Yamada
2025-07-16 23:24 ` [PATCH 2/6] kconfig: gconf: Fix Back button behavior Masahiro Yamada
2025-07-16 23:24 ` [PATCH 3/6] kconfig: gconf: replace GtkImageMenuItem with GtkMenuItem Masahiro Yamada
2025-07-16 23:24 ` Masahiro Yamada [this message]
2025-07-16 23:24 ` [PATCH 5/6] kconfig: gconf: remove unneeded variable in text_insert_msg Masahiro Yamada
2025-07-16 23:24 ` [PATCH 6/6] kconfig: gconf: refactor text_insert_help() Masahiro Yamada
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250716232542.873747-4-masahiroy@kernel.org \
--to=masahiroy@kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.