summaryrefslogtreecommitdiff
path: root/src/caja-application.c
AgeCommit message (Collapse)AuthorFilesLines
2015-11-15fix g_object_unref callMonsta1-1/+5
it wasn't properly unref'ed and caused a runtime warning
2015-09-10When opening the first window, don't restore the position of the last closed ↵Clement Lefebvre1-23/+1
window. It's confusing to users (the last closed window is irrelevant within one session with multiple windows open) and it can lead to really bad issues which users consider bugs (why is my first window behaving differently than other windows? why is my first window appearing in the corner of my screen? why when I open caja for the first time my window doesn't appear on the monitor my mouse presently is? etc..)
2015-09-04Switch to org.gnome.SessionManagerClement Lefebvre1-24/+19
2015-04-07Fix g_bus_unwatch_name assertiontarakbumba1-2/+6
Guard the g_bus_unwatch_name() call to only run when we actually have set a watcher to the screensaver.
2015-04-07Fix for https://github.com/mate-desktop/caja/issues/398tarakbumba1-4/+228
On the Shmoocon at 2011 there was a presentation by Jon Larimer demonstrating how to abuse vulnerabilities and bugs, or even just creating socially or security compromising thumbnails in mounting and thumbnailing, which happens on automounting USB drives. This is a particular issue when this happens on a locked box where the attacker doesn't otherwise have access to the user account: http://www.net-security.org/secworld.php?id=10544 Disable automounting if the MATE screen saver is currently locked. See also https://bugzilla.gnome.org/show_bug.cgi?id=642020 This commit is merely based on : https://git.gnome.org/browse/nautilus/commit/?h=gnome-2-32&id=b7262fa945ef1ea936c15f0d248ad7a024d97dca
2015-01-13drop support for GLib < 2.36Monsta1-2/+0
Closes https://github.com/mate-desktop/caja/pull/372
2014-12-29Revert "dbus-manager: add a skeleton of NautilusDBusManager"infirit1-5/+0
This reverts commit 08bc0644ebc869ff1db320cc2bdfc4a471a6f9ac.
2014-12-16dbus-manager: add a skeleton of NautilusDBusManagerinfirit1-0/+5
2014-10-27implementation of extension interface and status management (gsoc2014)Alexander van der Meij1-2/+2
2014-10-05Use g_get_user_config_dir instead of harcoding to $HOME/.configinfirit1-1/+1
2014-03-19Remove ConsoleKit usageStefano Karapetsas1-159/+0
Closes https://github.com/mate-desktop/caja/issues/125 Closes https://github.com/mate-desktop/caja/issues/226
2014-03-18Possible solution for x-caja-desktop issueStefano Karapetsas1-3/+11
2013-07-24Update for mate-desktop changesStefano Karapetsas1-1/+1
2013-02-23Add support for freedesktop.org File Manager DBus InterfaceStefano Karapetsas1-0/+36
http://www.freedesktop.org/wiki/Specifications/file-manager-interface Most of code is adapted from Nautilus: http://git.gnome.org/browse/nautilus/tree/src/nautilus-freedesktop-dbus.c Closes https://github.com/mate-desktop/mate-file-manager/issues/3
2012-12-22[all] silence warnings from GCC 4.6Jasmine Hassan1-5/+0
GCC 4.6 introduced a new warning about variables declared and initialized, but not really used in the function body. Remove all of these occurrences to build cleanly. http://git.gnome.org/browse/nautilus/commit/?id=d4230de8667764e02dbb966b5d806ff78ced2fd5
2012-12-03[global-prefs|application] use MATE global 'show-desktop-icons' settingJasmine Hassan1-3/+6
instead of a local-to-caja setting 'show-desktop' This key would indicate that file managers (by default Caja, but applies to others like Thunar or ROX) should handle desktop, i.e. draw a background and place icons there. Otherwise (when false), mate-settings-daemon will take over drawing desktop background. This is different from 'draw-background', which is a separate option used only for drawing background without icons (by mate-settings-daemon). To Caja, 'show-desktop-icons' implies 'draw-background', and so if set to false, Caja won't (needlessly) draw the desktop. However, if the user uses the "Background & Emblems dialog" to drop an image-pattern/color/reset on the desktop, Caja will again draw the desktop. For reference: https://bugzilla.gnome.org/show_bug.cgi?id=632225
2012-11-23[src] fix some incompatible pointer type warningsJasmine Hassan1-1/+5
including a silly mistake in caja-window where destroy function's return type was accidently ommitted during the addition of gtk version checks.
2012-11-23[all] include src/glibcompat.h & use g_list_free_full() where neededJasmine Hassan1-7/+5
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
2012-11-16[all] use g_list_free() and g_strcmp0 instead of eel functionsJasmine Hassan1-1/+2
Was: general: use g_list_free_full() instead of eel functions http://git.gnome.org/browse/nautilus/commit/?id=5e669515fd7f760382e6b7aa1449734a35a2d7f4 . Instead of g_list_free_full(), we use g_list_foreach and g_list_free() to avoid unnecessary glib dependency bump to 2.28
2012-11-16[src] don't use GtkObject (GTK3)Jasmine Hassan1-1/+5
the ::destroy signal of GtkObject has only been moved to GtkWidget in GTK3 (after GtkObject removal): http://developer.gnome.org/gtk3/3.0/ch25s02.html So we use conditionals in this case, to keep it working with GTK2. A tad similar: http://git.gnome.org/browse/nautilus/commit/?id=cc6cb51e827c0b15d4ef09f12d37b9f331ddcef8
2012-11-16[application] change the way spatial windows are createdJasmine Hassan1-105/+69
Use a _get() function + the standard caja_window_go_to() instead of using _present(). The new functions in caja-window-manage-views are smart enough to take care of re-using an existent window. http://git.gnome.org/browse/nautilus/commit/?id=d070d631545aac9114bc271481da603587c07c7c
2012-09-06remove old undo codeStefano Karapetsas1-6/+0
2012-09-05convert window-state to gsettingsStefano Karapetsas1-4/+4
2012-09-05convert always-use-browser to gsettingsStefano Karapetsas1-3/+3
2012-09-05start migration to gsettingsStefano Karapetsas1-13/+10
2012-08-12Fixed incorrect fsf addresses. Closes #28.Steve Zesch1-1/+1
2011-12-01moving from https://github.com/perberos/mate-desktop-environmentPerberos1-0/+2338