The issue is that when pressing enter in search while the search entry
has the focus, right after the callback to activate the selection is
called, Nautilus also tries to activate the location corresponding to
the base of the search, as the view is still searching.
This occurs because in the activated signal the search is set as not
visible manually, which will make Nautilus check immediatly if it should
go back to the base of the search location, without waiting for the view
to update.
To fix this, don't set the search as not visible in the activated callback,
as when the search-mode-enabled property changes, if necessarry, the
cancel signal will be emitted which will set the search as not visible,
which will happen only after the view is updated. This is the behavior for
activating the selection in other ways, so activation with focus on the
entry should behave the same.
https://bugzilla.gnome.org/show_bug.cgi?id=764981
The problem is that when we have a file conflict dialog, we can write
a new name for the file in GtkEntry in the expander "Select a new
name for the destination", but after typing in a new file name,
pressing <ENTER> does nothing, but should close this dialog and
confirm the renaming.
To fix this we enable "activates-default" flag for the GtkEntry.
https://bugzilla.gnome.org/show_bug.cgi?id=780449
When using Wayland the menu for selecting the visible columns (right
clicking on the column headers in the list view) can be misplaced when
using two monitors because src/nautilus-list-view.c still uses the
deprecated gtk_menu_popup_for_device() instead of the new
gtk_menu_popup_at_pointer().
https://bugzilla.gnome.org/show_bug.cgi?id=781073
nautilus_file_get_mime_type() returns a newly
allocated string, which should be freed when no longer
required.
using g_autofree() automatically frees the string fixing the leak
https://bugzilla.gnome.org/show_bug.cgi?id=782070
This hides the autostart from Ubuntu's Startup Applications
app since we don't want users to easily disable this without
understanding why it's there.
https://bugzilla.gnome.org/show_bug.cgi?id=781874
The script broke after killing off Autotools support, since the libgd
submodule was moved to /subprojects/libgd. Additionally, this commit
makes the script exit on error and makes xz print verbose output.
https://bugzilla.gnome.org/show_bug.cgi?id=781892
Drag&drop of native Google Drive files doesn't work correctly, because
target path is used, which causes requests for HTTP backend and fails.
The activation URI is used for drag&drop since commit 1d1488c. Recently,
this behavior has been disabled for trash locations by commit bc22321.
This behavior seems to make sense for recent locations in order to allow
dropping in applications, which are not based on GLib/GIO. It also makes
sense for afpbrowse, dnssd, network, and smbbrowse backends when mounting
and bookmarking. Let's set the activation URI only for the mentioned.
This change should not affect nautilus links (i.e. desktop files and
symlinks), which are handled by different codepath, it should affect
only certain GVfs backends.
https://bugzilla.gnome.org/show_bug.cgi?id=768168
As of 0.40.0, Meson has the ability to initialize subprojects that are
git submodules. This removes the need for a separate script to achieve
that.
https://bugzilla.gnome.org/show_bug.cgi?id=781653
We were prepending the items but in regular order, instead of inverse
to preserve the order.
To fix it the patch invert the order of the items when prepending.
https://bugzilla.gnome.org/show_bug.cgi?id=774724
Currently we support the mailing list as a way to communicate with the
developers.
However mailing lists are not used as much as they were used years ago,
and they became a burden to maintain in our side.
To fix this situation, remove the mailing list from the README so users
doesn't use it anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=778952
For next release I hope they are good enough to be able to enable them
by user preference, and also makes easier for us to switch between them
in order to test everything is fine in both.
Items are not allocated at that time yet, so it needs some time to be
able to calculate the correct allocation of the item, and therefore the
correct adjustment for the scrolled window.
https://bugzilla.gnome.org/show_bug.cgi?id=780380
Until now we weren't selecting the item that was selected.
However it really helps to do that so the user can navigate after
searching. For instance this is pretty good to have for the "type-ahead"
use case.
This commit select the file after the user opens the item location
and reveals the file.
https://bugzilla.gnome.org/show_bug.cgi?id=780380
So users can drag the window from the buttons of the pathbar too, as it
seems it's more important feature for them instead of dnd the path in
the pathbar, which is also quite undiscoverable.
https://bugzilla.gnome.org/show_bug.cgi?id=776663
Currently, the extraction starts without checking
for enough filesystem space to store the extracted files.
This commit checks for filespace before the extraction takes place.
https://bugzilla.gnome.org/show_bug.cgi?id=775253
After creating a new folder through the hamburger menu, the
keyboard focus stays on the hamburger menu button, so you
can't go to the newly created folder by simply pressing enter
again.
To solve that, we simply need focus the NautilusFilesView after
destroy the dialog, in the case where name is accepted.
https://bugzilla.gnome.org/show_bug.cgi?id=754744
Sometimes, the extractions starts without enough filesystem
space to store the extracted files.
This commit checks for filespace before the extraction takes place.
https://bugzilla.gnome.org/show_bug.cgi?id=775253
