summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
...
* Updated Slovak translationDušan Kazik2015-12-061-1307/+1900
|
* canvas-container: consider margins when calculating icon bounding boxIain Lane2015-12-041-2/+4
| | | | | | | | | | | Shells can fix docks, panels and other similar things which reduce the available space to draw on. This is called the canvas margin. When positioning things relative to icons within containers we need to adjust by this margin, otherwise they will be shifted away from the target. Do this when we calculate the bounding box. https://bugzilla.gnome.org/show_bug.cgi?id=759002
* Updated Spanish translationDaniel Mustieles2015-12-021-192/+165
|
* file: fix previous commitCarlos Soriano2015-12-021-1/+1
| | | | Conflict resolution in commit e6587b86b4c75 went wrong on my part.
* directory: assume recent as localCarlos Soriano2015-12-022-26/+2
| | | | | | | We were assuming trash and native_path as local, but not recent, which is wrong. So assume recent as local, with the benefit that we can use it for mime type polling and remove some dead code now.
* Don't trigger an int overflow on files' age computationSebastien Bacher2015-12-021-2/+1
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=758898
* Make libselinux dependency controllable by configure switchGilles Dartiguelongue2015-12-021-11/+12
| | | | https://bugzilla.gnome.org/show_bug.cgi?id=758632
* file: fix wrong date calculationCarlos Soriano2015-12-021-1/+8
| | | | | | | | | | | | | We were checking how many days ago the file was modified by checking directly the current time with the file modification time, which is wrong if the file was modified a few hours ago but the day already passed. What happened is that it was showing the time as in if it was modified in the same day, instead of saying "Yesterday". To fix it, check the time difference with the midnight time. https://bugzilla.gnome.org/show_bug.cgi?id=757272
* Updated Kazakh translationBaurzhan Muftakhidinov2015-11-281-1187/+1355
|
* Updated Portuguese translationPedro Albuquerque2015-11-281-183/+402
|
* files-view: fix leak and remove unneeded codeCarlos Soriano2015-11-271-18/+0
|
* files-view: formatting fixCarlos Soriano2015-11-271-9/+8
|
* files-view: don't hold a ref to the view on templates itemsCarlos Soriano2015-11-261-2/+0
| | | | | They shouldn't need to hold a ref to the whole view and makes ownership management more complex.
* files-view: unref action groupCarlos Soriano2015-11-261-3/+15
| | | | | | | | | | | | | We were leaking it, causing that the view was not free if there were some templates, since templates menu items were holding a ref to the view and are only freed when the closure of the action gets freed, which is the view action group. This was making the view to get never finalized, and therefore making all kind of problems afterwards. Upcoming patch will also make template not hold a ref to the view, even if the issue is fixed now, I think templates menu items holding a reference to the view is wrong.
* files-view: better memory management for widgetsCarlos Soriano2015-11-261-3/+6
| | | | | We were leaking them refing and not unrefing. ref sink them and unref them on finalize.
* Updated Hungarian translationGábor Kelemen2015-11-261-1266/+1853
|
* files-view: clarify comment about delete-permanentlyCarlos Soriano2015-11-261-1/+1
|
* files-view: add setting for always show delete permanentlyCarlos Soriano2015-11-264-0/+29
| | | | | | | Maintenance is not that much as long as we don't show it in any UI, and was requested by several people. https://bugzilla.gnome.org/show_bug.cgi?id=757375
* window-slot: remove wrong unrefCarlos Soriano2015-11-261-2/+0
| | | | Probably if didn't crash before because we are leaking elsewhere...
* window-slot: remove unneded unrefCarlos Soriano2015-11-261-3/+0
|
* general: always use nautilus_file_refCarlos Soriano2015-11-262-7/+5
| | | | So we can debug ref counting issues more comfortably.
* window-slot: remove duplicated assertCarlos Soriano2015-11-261-1/+0
|
* window-slot: remove unneeded constantCarlos Soriano2015-11-261-7/+0
|
* Updated Spanish translationDaniel Mustieles2015-11-241-85/+300
|
* Updated Finnish translationJiri Grönroos2015-11-231-104/+322
|
* Updated POTFILES.inPiotr Drąg2015-11-231-1/+2
|
* configure: bump gtk min version for GtkShortcutsWindowCarlos Soriano2015-11-231-1/+1
|
* application: let GtkApplication load the appmenuFelipe Borges2015-11-233-14/+1
| | | | | | | | | | | | Since bgo#757826 introduced g_application_set_resource_base_path, we don't need to use a GtkBuilder to load the appmenu. GtkApplication automatically loads menus from the GtkBuilder resource located at "gtk/menus.ui", relative to the application's resource base path (see g_application_set_resource_base_path ()). The menu with the ID "app-menu" is taken as the application's app menu. https://bugzilla.gnome.org/show_bug.cgi?id=757946
* configure: bump gtk min versionCarlos Soriano2015-11-231-1/+1
| | | | For behave accordingly with gtkplacessidebar and gtkplacesview.
* application: add app menu entry for shortcutsCarlos Soriano2015-11-232-0/+16
|
* application: add shortcuts help windowFelipe Borges2015-11-233-0/+375
| | | | | | | Use GTK+'s new shortcut window to document our shortcuts. See: https://wiki.gnome.org/Initiatives/GnomeGoals/ShortcutWindows https://bugzilla.gnome.org/show_bug.cgi?id=757826
* Updated Lithuanian translationAurimas Černius2015-11-201-1105/+1096
|
* Updated Hebrew translationYosef Or Boczko2015-11-191-1042/+1048
|
* Updated Serbian translationМарко Костић2015-11-181-257/+256
| | | | (cherry picked from commit 9f8f4fb12ecc8985ccf5bca5d0feeae4ce3a0473)
* Updated Greek translationEfstathios Iosifidis2015-11-171-1344/+1396
|
* Updated Spanish translationDaniel Mustieles2015-11-171-931/+937
|
* Updated Scottish Gaelic translationGNOME Translation Robot2015-11-171-1248/+1139
|
* mime-actions: fix indentationCosimo Cecchi2015-11-161-8/+8
|
* mime-actions: print error in a g_warning() when not in a dialogCosimo Cecchi2015-11-161-1/+4
| | | | | Make sure we don't eat errors without at least printing them on the terminal.
* mime-actions: fix double free in error pathCosimo Cecchi2015-11-161-2/+0
| | | | | The "unhelpful error dialog" code already takes care of freeing the activation parameters. Make sure it does not do that twice.
* mime-actions: check for name owner for PackageKitCosimo Cecchi2015-11-161-4/+7
| | | | | We might not have a PackageKit name owner. Check for that case, or the system will think that it can install extra applications.
* Updated Czech translationMarek Černocký2015-11-151-823/+829
|
* Updated Norwegian bokmål translation.Kjartan Maraas2015-11-151-1029/+1039
|
* preview: Don't assume XMatthias Clasen2015-11-141-2/+8
| | | | | | | We need to check at runtime if we are actually running under X, before calling gdk_x11 API. http://bugzilla.gnome.org/show_bug.cgi?id=758026
* Fix some GCC warningsCosimo Cecchi2015-11-142-2/+2
|
* Fix Russian translationYuri Myasoedov2015-11-141-167/+11
|
* Updated Portuguese translationPedro Albuquerque2015-11-141-821/+826
|
* progress-info-widget: increment max charsCarlos Soriano2015-11-131-1/+1
| | | | | | | On languages different than English was not enough, making the text not understandable. https://bugzilla.gnome.org/show_bug.cgi?id=754968
* nautilus-places-view: sink the reference on creationCarlos Soriano2015-11-131-1/+8
| | | | | | | | | Last patch now makes view reference counting works, however NautilusFilesView sink the ref on creation, and NautilusPlacesView was not, making NautilusPlacesView holding a reference less than other views and making nautilus crash. Follow what other views do and sink the reference.
* window-slot: don't ref all views on creationCarlos Soriano2015-11-131-1/+1
| | | | | | | | | | | | | This was leaking and making that no view was finalized, leading to all kind of problems and crashes due to signals and files updating the dangling view, and not letting files to be released. This was creating multiple non-related reports on Fedora Tracker making nautilus one of the top crashers. Downstream tracker bug: https://bugzilla.redhat.com/show_bug.cgi?id=1277625 The upcoming patch is also necessary for a complete fix.