After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 548388 - Set title dialog should activate with Enter
Set title dialog should activate with Enter
Status: RESOLVED FIXED
Product: gnome-terminal
Classification: Core
Component: general
2.23.x
Other Linux
: Normal normal
: gnome-2-24
Assigned To: GNOME Terminal Maintainers
GNOME Terminal Maintainers
fixed-2-24
: 556627 571168 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2008-08-19 06:46 UTC by Diego Escalante Urrelo (not reading bugmail)
Modified: 2009-02-10 13:32 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A patch to fix default_response for the ok button, and fix the cancel button! (2.18 KB, patch)
2008-09-28 00:36 UTC, Ian Hands
needs-work Details | Review
A cleaner terminal-window patch, for the set titlle fix. (1.35 KB, patch)
2008-09-29 22:39 UTC, Ian Hands
committed Details | Review

Description Diego Escalante Urrelo (not reading bugmail) 2008-08-19 06:46:25 UTC
If you type a new title and hit enter, it will do nothing. You have to click Ok.
Evil!
Comment 1 Christian Persch 2008-08-19 11:18:58 UTC
Probably just need to fiddle with activates-default on the entry. Want to try your hands at it? :)
Comment 2 Ian Hands 2008-09-28 00:36:29 UTC
Created attachment 119505 [details] [review]
A patch to fix default_response for the ok button, and fix the cancel button!

Hope this works out. Do I get to slap my name/email somewhere if this is accepted? What about gnome-found? How substantial of a contribution does one have to make to get in? I also fixed/worked on http://bugzilla.gnome.org/show_bug.cgi?id=207 today.

There was a very simple GTK_RESPONSE_ACCEPT instead of GTK_RESPONSE_OK, but the cancel button was also broken (it ran the same code as the ok button). I put a check in the callback which skips the screen_set_user_title function call.

Thanks,
-Ian Page Hands
Comment 3 Diego Escalante Urrelo (not reading bugmail) 2008-09-28 04:59:11 UTC
Thanks for the patch!

Some comments, don't modify the indentation of already existing code, like in:

-                    G_CALLBACK (terminal_set_title_dialog_response_cb), priv->active_screen);
+		    G_CALLBACK (terminal_set_title_dialog_response_cb), priv->active_screen);

spaces where replaced by tabs. This clutters your patches.

Otherwise I think it looks pretty good, would you please update it to remove the uneeded indentation changed lines?

You get your name in the changelog for the patches you contribute and are acknowledged in the release notes for the next release of the module.
Your name is slapped in the file itself and in the authors file/about dialog when your contribution is significant, like if you added plugin capabilities to the text editor, or something like that. Or when you have contributed for quite some time a good number of patches.
Comment 4 Ian Hands 2008-09-29 22:39:12 UTC
Created attachment 119620 [details] [review]
A cleaner terminal-window patch, for the set titlle fix.

Sorry, I have a habit of wanting to "mark-all", "indent-region".

"Or when you have contributed for quite some time a good number of patches."
I would really like to start looking at and fixing bugs on a regular schedule (maybe a bug or two per week/weekend to start).

Let me know if this works,
-Ian
Comment 5 Christian Persch 2008-10-08 13:03:24 UTC
Thanks for the patch!

This problem has been fixed in our software repository. The fix will go into the next software release. Thank you for your bug report.
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.
Comment 6 Christian Persch 2008-10-16 21:33:21 UTC
*** Bug 556627 has been marked as a duplicate of this bug. ***
Comment 7 Christian Persch 2009-02-10 13:32:21 UTC
*** Bug 571168 has been marked as a duplicate of this bug. ***