| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
|
|
| |
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, the flow view tries to reveal the selection even if it is
empty. That can result in a crash if the selection is empty.
https://bugzilla.gnome.org/show_bug.cgi?id=780732
|
|
|
|
|
|
| |
It is no longer used as of 8b26778710510c9a1d3e7aa8ea82d4dfd7c4a3e9.
https://bugzilla.gnome.org/show_bug.cgi?id=780730
|
|
|
|
|
|
| |
A copy paste error from the set_items function.
https://bugzilla.gnome.org/show_bug.cgi?id=780380
|
|
|
|
|
|
| |
It was missing in the new GtkFlowBox based view.
https://bugzilla.gnome.org/show_bug.cgi?id=780380
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Forgot to delete it after coding :(
|
|
|
|
|
| |
It's not longer necessary. This patch removes it and also fixes
a compiler warning.
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
| |
Currently when the move to/copy to file chooser dialog is launched
during search, the dialog shows an error as the location is invalid.
Change this so that the base of the search is displayed in the dialog
when this dialog is launched while searching.
https://bugzilla.gnome.org/show_bug.cgi?id=778113
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With a batch renaming using a template, the extension is removed.
That is, if we have a file named "some.txt", after renaming using
template "[Original file name]YOLO" we will get "someYOLO.txt",
and this is correct.
But if we renaming folders with a name where there is a dot and
subsequent symbols, these characters will be mistakenly considered
an extension. For example, after renaming folders "file" -> "fileYOLO",
"FILEZ." -> "FILEZ.YOLO" (is correct), but "org.package.library" ->
"org.packageYOLO.library", "project-2.0" -> "project-2YOLO.0",
"my.files" -> "myYOLO.files", "extra-0.85" -> "extra-0YOLO.85" (is
incorrect)
To fix this bug we won't search extension if current NautilusFile
is a directory.
https://bugzilla.gnome.org/show_bug.cgi?id=780326
|
|
|
|
|
|
|
|
|
|
|
| |
If the user tries to replace a folder with a symbolic link with the same
name,the content of the destination folder was being deleted.
To fix this behaviour, the UI disables the replace button allowing the
user only to skip or to rename in order to avoid the deletion of the
destination folder's content.
https://bugzilla.gnome.org/show_bug.cgi?id=632323
|
| |
|
| |
|
| |
|
|
|
|
| |
GtkPlacesView now supports monitoring networks.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Otherwise meson install libnautilus into lib64, which is wrong for
flatpak or other distributions.
Seems this is always going to guess it wrong, let's always specify
libdir.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit a84bf6ac79175e831feaf5e061dad3e822f1e816.
Meson can be used now from builder, although it compiles everytime due
to ninja issue https://github.com/ninja-build/ninja/issues/1120 it's
still faster than autotools for me (quite surprising), so switching for
it as default build system.
Developers can still use autotools just switching the buildsystem in the
flatpak manifest.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
EXIF and Exempi are currently only being detected due to an oversight.
This commit makes Meson define the preprocessor macros needed to use the
libraries.
https://bugzilla.gnome.org/show_bug.cgi?id=779879
|
| |
|
|
|
|
| |
Builder and ninja is not ready for a good experience with meson.
|
|
|
|
| |
We removed the option in 2475e9a1f7af7a6
|
| |
|
| |
|