| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until now archives were managed only if activated from Nautilus itself
and if a setting was set.
There are two main problems with this.
1- Archives opened in other apps cannot be handled by Nautilus
2- Users cannot use the regular myme type handling for setting Nautilus
as the app handling archives, or unsetting it.
This patch add support for archives myme types handled by gnome-autoar
and removes the UI and setting used in the previous version.
|
| |
|
|
|
|
| |
It was removed long ago
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The filename is likely to match the display name, which is already
prominently used as the result name, so including it in the description
doesn't add any information. In fact, as gnome-shell is about to
display name and description on a single line[0], duplicating the
filename increases the chances of less information being displayed
due to ellipsization.
[0] https://raw.githubusercontent.com/gnome-design-team/gnome-mockups/master/shell/search/search-list-layout.png
https://bugzilla.gnome.org/show_bug.cgi?id=784105
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=785062
|
|
|
|
|
|
|
|
|
|
|
|
| |
Searching makes Nautilus have no files in the view sometimes, even
if there are search results, because the view connects to the
files-added signal after it added a monitor to the directory
and the signal might be emitted before connecting to it.
To fix this, first connect to the files-added and files-changed
signals, before adding the monitor to the directory.
https://bugzilla.gnome.org/show_bug.cgi?id=785722
|
|
|
|
|
|
|
|
| |
Assuming that the location cannot be null can leads to crashes in cases
when the user is trying to open non-existent locations, e.g. broken
bookmarks.
https://bugzilla.gnome.org/show_bug.cgi?id=785317
|
|
|
|
|
|
|
|
| |
Opening the file properties window causes a crash with images that have
embedded XMP information. This is caused by not initializing the library
properly.
https://bugzilla.gnome.org/show_bug.cgi?id=785292
|
|
|
|
|
|
|
|
| |
When marking the file as gone, clearing its file info after removing it
from the parent directory will result in a crash in cases where it is
the last reference being dropped.
https://bugzilla.gnome.org/show_bug.cgi?id=785562
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=785062
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=785062
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=784941
|
|
|
|
|
|
|
|
| |
There's no reason for archives on, say, SMB remote shares couldn't be
decompressed through the "Extract Here" functionality, so remove the
remote files check.
https://bugzilla.gnome.org/show_bug.cgi?id=784941
|
|
|
|
|
|
|
|
| |
A large number of core features require Tracker to work, and many of the
new features using Tracker don't have any fallback support, failing to
build when Tracker is not available, so make tracker a hard requirement.
https://bugzilla.gnome.org/show_bug.cgi?id=784940
|
|
|
|
|
|
|
| |
Make sure that tracker-sparql is optional and auto-detected by default
and that tracker-sparql-1.0 is still supported.
https://bugzilla.gnome.org/show_bug.cgi?id=784940
|
|
|
|
|
|
| |
Since some files were GPL3 already.
Discussion happened at nautilus mailing list
https://mail.gnome.org/archives/nautilus-list/2017-May/msg00001.html
|
| |
|
| |
|
|
|
|
|
|
|
| |
This was causing problems for Launchpad's translation importer
for Ubuntu.
"Line 7166: Unsupported plural case number."
|
| |
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
|
|
|
|
|
|
|
| |
Opening the batch rename dialog and immediately closing it results in a
crash, due to the async operation not being canceled, thus resulting in
invalid memory access on callback.
https://bugzilla.gnome.org/show_bug.cgi?id=784336
|
|
|
|
|
| |
No code changes required. It remains API compatible with the current
usage in nautilus.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
When the operation is freed on the first if, the operation will
still be accessed on the second if.
To fix this, merge the two if's since they both complete the
operation.
https://bugzilla.gnome.org/show_bug.cgi?id=783873
|
|
|
|
|
| |
get_zoom_level_percentage() does not return a value in the specified
range, as there are zoom levels beyond 100%.
|
|
|
|
|
|
|
|
|
| |
The reset zoom button is sensitive even though the zoom percentage is already at
100%.
Let the button be inactive if the zoom percentage is already at 100%.
https://bugzilla.gnome.org/show_bug.cgi?id=771481
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=781095
|
|
|
|
|
|
|
| |
'Create Link' button does nothing when the clipboard is empty. In order to fix
that, disable the button when the clipboard is empty.
https://bugzilla.gnome.org/show_bug.cgi?id=781095
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The search text can now also match the contents of a file, besides
the file name.
This is done with the help of a Tracker query, using fts:match, which
matces both the contents of a file and the filename.
The user also has the option to choose whether to use or not the
Full Text Search. This can be done with a preference, which represents
the default option when opening a new tab/window or from the search
popover.
https://bugzilla.gnome.org/show_bug.cgi?id=775961
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
If "/org/gnome/desktop/wm/preferences/action-middle-click-titlebar"
is set to "minimize", a click on the pathbar will open a new tab
but also minimize the window.
By handling the event already on the button press (not release),
the window is not minimized anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=757439
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Wayland allows multiple pointers to be active at the same time, e.g. when
a Wacom tablet and mouse are both connected to a system. This means that
it is possible to recieve a "rubberband start" event from a second tool
while a rubberband is already active. At the moment, this results in stray
selection rectangles since the canvas does not properly perform cleanup.
To prevent these graphical glitches from occuring, we can simply cancel
any existing rubberband operation if a second one attempts to start. The
only additional minor complication is ensuring that the new rubberband
is not stopped when the first tool sends a button-up event.
https://bugzilla.gnome.org/show_bug.cgi?id=783797
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Nautilus assumes that the pointer returned by gdk_seat_get_pointer will
return the same GdkDevice which started a rubberband action. This is
not necessarily the case, however. Under Wayland, for example, tablet
tools have pointers (and GdkDevice's) which are entirely separate from
the seat's primary mouse-driven pointer. Attempting to use a pen to
perform rubberband selection will result in the rectangle being drawn
with the incorrect coordinates.
This patch has the code store the GdkDevice which generated the event
and provides it in place of the call to gdk_seat_get_pointer.
https://bugzilla.gnome.org/show_bug.cgi?id=783797
|
| |
|