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 780449 - File conflict dialog: <ENTER> does not confirm when renaming a file
File conflict dialog: <ENTER> does not confirm when renaming a file
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File and Folder Operations
3.22.x
Other Linux
: Normal enhancement
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
: 751139 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-03-23 14:46 UTC by dev.nipe.systems
Modified: 2017-08-21 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Bugfix (1.72 KB, text/plain)
2017-03-23 16:15 UTC, Evgeny Shulgin
  Details
Bugfix (as patch) (1.72 KB, patch)
2017-03-23 16:17 UTC, Evgeny Shulgin
none Details | Review
Bugfix (955 bytes, patch)
2017-04-04 09:26 UTC, Evgeny Shulgin
reviewed Details | Review
Bugfix (1.27 KB, patch)
2017-04-04 12:38 UTC, Evgeny Shulgin
none Details | Review
Patch version over 9000 (1.31 KB, text/plain)
2017-04-12 19:37 UTC, Evgeny Shulgin
  Details
Patch version over 9001 (1.31 KB, patch)
2017-04-12 19:37 UTC, Evgeny Shulgin
committed Details | Review

Description dev.nipe.systems 2017-03-23 14:46:36 UTC
Overview:
<ENTER> does not confirm the file-conflict-dialog when renaming a file.

Steps to Reproduce:
1) Copy any file (Ctrl+C).
2) Go into another directory.
3) Paste the copied file (Ctrl+V).
4) Paste the copied file again (Ctrl+V), which causes the file conflict dialog to open.
5) Open the expander "Select a new name for the destination".
6) Type a new filename into the GtkEntry (a.k.a. text field).
7) Press <ENTER>.

Actual result:
Step 7 (see above) does nothing.

Expected result:
Step 7 will trigger (press/click) the "confirm"-button of the dialog (which then closes the dialog and renames the file).

Additional informations:
The GtkEntry gets created in "src/nautilus-file-conflict-dialog.c" line 351 ff.
Comment 1 Evgeny Shulgin 2017-03-23 16:15:36 UTC
Created attachment 348583 [details]
Bugfix

In all other places we can save/rename files with ENTER, so why not fixing it?
Comment 2 Evgeny Shulgin 2017-03-23 16:17:11 UTC
Created attachment 348584 [details] [review]
Bugfix (as patch)

Sry, forget to press "patch" checkbox
Comment 3 Carlos Soriano 2017-03-27 20:05:57 UTC
Review of attachment 348584 [details] [review]:

Hey thanks for the patch. You can actually use “activates-default” and is much straightforward.
Comment 4 Evgeny Shulgin 2017-04-04 09:26:45 UTC
Created attachment 349221 [details] [review]
Bugfix

Bugfix with activates-default

P.S. Sorry for the long delay, I could not use my home PC for a few days.
Comment 5 Carlos Soriano 2017-04-04 10:55:40 UTC
Review of attachment 349221 [details] [review]:

Much better code now! The commit message is still lacking. See https://wiki.gnome.org/Newcomers/CodeContributionWorkflow#Commit_guidelines
Comment 6 Evgeny Shulgin 2017-04-04 12:38:32 UTC
Created attachment 349238 [details] [review]
Bugfix

Added patch description
Comment 7 Ernestas Kulik 2017-04-12 19:31:15 UTC
Review of attachment 349238 [details] [review]:

The commit message looks good, but somewhere along the way you broke the patch itself. :/

::: src/nautilus-file-conflict-dialog.c
@@ +302,3 @@
     g_signal_connect (widget, "changed",
                       G_CALLBACK (entry_text_changed_cb), dialog);
+    gtk_entry_set_activated (GTK_ENTRY (widget), TRUE);

This isn’t in the API.
Comment 8 Evgeny Shulgin 2017-04-12 19:37:06 UTC
Created attachment 349745 [details]
Patch version over 9000

Really sorry, I can't remember how I was able to break my code... Fixed now.
Comment 9 Evgeny Shulgin 2017-04-12 19:37:57 UTC
Created attachment 349746 [details] [review]
Patch version over 9001

Patch
Comment 10 Ernestas Kulik 2017-04-12 19:54:17 UTC
Review of attachment 349746 [details] [review]:

Ah, sorry, I missed the subject line. It should have the modified file in it (as you know from your other patches).

Everything else is great.
Comment 11 Ernestas Kulik 2017-05-02 18:22:00 UTC
Attachment 349746 [details] pushed as 941b3fe - file-conflict-dialog: confirm filename change with return key
Comment 12 António Fernandes 2017-08-21 09:22:49 UTC
*** Bug 751139 has been marked as a duplicate of this bug. ***