| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
| |
After the port to GNotifications, libnotify is only used to check
whether the server supports persistence. Just call the underlying
DBus method directly and remove the dependency.
https://bugzilla.gnome.org/show_bug.cgi?id=740886
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=740886
|
| |
|
| |
|
|
|
|
|
|
| |
Fallout from 37be3809bc0d25d28298b38bc0b893a6fd3a665f
https://bugzilla.gnome.org/show_bug.cgi?id=740383
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Renaming an item on Google Drive does not change the actual GVfs path
because the path is made up of document-ids, which do not change. A
rename operation only affects the title of the entry. In GIO terms,
only the standard::display-name changes, but the standard::name remains
the same.
Therefore, if there is already a file with the same standard::name,
then don't mark it as gone if it is the same file that we are renaming.
https://bugzilla.gnome.org/show_bug.cgi?id=740383
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Until now we were using --no-default-window in cases when we wanted to
manage the icons on the desktop, which is the most common use case of
this setting.
The problems were:
- When using --no-default-window for the first inscante, the user
couldn't open a new window of nautilus, since the only window allowed
was the desktop one in the first instance. The code was just early
returning in activate if the private setting of the instance is set.
- When using --no-default-window for the consecutive instances after
starting nautilus without --no-default-window it was creating a new
window anyway, since the first instance doesn't have the setting set in
its private and the second instance was just calling the activate of the
first instance. For instance that was happening when the user
activate/deactivate the show-desktop-icons gsetting, since the
nautilus-autostart desktop file was running nautilus
--no-default-window, but the first instance was a instance withouth the
--no-default-window.
So the solution for both cases is avoiding calling activate if the
--no-default-window is an arggument, instead of a private setting of the
instance.
To avoid calling activate we can return a value less than 0 to the
GApplication in the handle_local_options function. So if the
--no-default-window is passed as an argument, we just skip the activate
call.
Since when launching consecutive instances they take care of its own
handle_local_options they can skip as well the activate call redirected
to the first instance.
Big thanks to Ray Strode for discussion, debugging and base of this
patch, and Debarshy Ray for discussion and debugging.
https://bugzilla.gnome.org/show_bug.cgi?id=737515
|
|
|
|
| |
Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
... instead of our own. The only difference between the two is that
GtkSearchEntry does not queue up the timeout when the text in the
entry has been cleared and emits the signal immediately. I don't think
that is a big issue for us.
https://bugzilla.gnome.org/show_bug.cgi?id=740000
|
| |
|
| |
|
|
|
|
|
|
| |
Commit 032f37f49778c1b8214b88b764ac29c1654b12e0 removed the action from
the menu, but won't keep the accelerator unless explicitly specified in
the XML file; add it in the XML file so Ctrl+w works.
|
|
|
|
| |
It doesn't seem to do anything really useful.
|
|
|
|
| |
Make it a bit smoother.
|
|
|
|
|
|
|
|
|
|
| |
Currently if the view is resized, the column name is resized as well
given that use ellipsization allowing the column to become unreadable.
To avoid that, use width-chars property to set a desired width, but at
the same time allowing the user to resize without limits the name column
if desired.
https://bugzilla.gnome.org/show_bug.cgi?id=732004
|
|
|
|
|
|
|
|
| |
"Header bar menus shouldn't include a close menu item, since this action
is already provided by the header bar. It can also be ambiguous as to
what a close menu item refers to." -- the HIG
https://bugzilla.gnome.org/show_bug.cgi?id=735539
|
|
|
|
|
|
|
|
|
|
|
| |
In commit 2780ce8790fc575ea we restored the --new-window option, but at
the same time we were creating a new window for any glib option like
gapplication-service.
Instead of that, check for known application options, and if not found
any, let gapplication manage them.
https://bugzilla.gnome.org/show_bug.cgi?id=738430
|
| |
|
|
|
|
|
|
|
|
|
|
| |
In case of no further arguments, open home folder. Commit
4e192481 "application: minimal port to handle_local_options()"
removed this, presumably accidentally. It makes clicking the "Files"
from favorites do nothing if Nautilus is already running (and it
always is running in classic mode as it handles desktop).
https://bugzilla.gnome.org/show_bug.cgi?id=738280
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently custom_basename_to_string uses the base name or display name
of the files for the copying and moving dialog.
In the cases of unlabeled removable drives, the name is a code, showing
in the dialog a not very friendly name.
gtkplacessidebar and nautilus-pathbar uses the mount name retrieved by
g_mount_name if available.
Use that fir the operations dialogs as well to display a more friendly
name to the user and to be consistent with the sidebar and pathbar name.
https://bugzilla.gnome.org/show_bug.cgi?id=738087
|
|
|
|
|
|
|
| |
Not setting it can lead to very wide windows, because gtk doesn't
enforce a maximum window size anymore.
https://bugzilla.gnome.org/show_bug.cgi?id=732117
|
|
|
|
|
|
|
| |
I think this is the third time I've changed this. The sidebar keeps
getting bigger. We might need to compute this dynamically when it's
unset, to ensure four columns of results regardless of theme or filename
length.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Don't SIGSEGV when changing any of the three combo boxes in the
preferences' Display tab. This issue existed since commit d8a8ab3.
https://bugzilla.gnome.org/show_bug.cgi?id=728503
|
|
|
|
|
|
| |
Or it won't follow the window size when resizing.
https://bugzilla.gnome.org/show_bug.cgi?id=728637
|
|
|
|
|
|
|
| |
Or we'll possibly eat the event for the entry itself, which will have
bad consequences to the state tracking of editable GtkCellRendererText.
https://bugzilla.gnome.org/show_bug.cgi?id=732513
|
|
|
|
|
|
|
|
| |
The refactoring in commit ecc8fdbca6acb446ffa89a6fea31616b77a4224a made
this use a function to fetch selected files instead of selected icons,
which will cause a crash when iterating through the selection.
https://bugzilla.gnome.org/show_bug.cgi?id=736599
|
| |
|
|
|
|
| |
Fix typo
|