Age | Commit message (Collapse) | Author | Files | Lines |
|
Fixes https://github.com/mate-desktop/caja/issues/688
*Split caja.css. Much of it can load with GTK_STYLE_PROVIDER_PRIORITY_THEME to allow themes that support Caja to set their own style. CSS required for the desktop background to show and to keep the white text suitable for most backgrounds needs GTK_STYLE_PROVIDER_PRIORITY_APPLICATION so it is loaded separately from new file caja-desktop.css
*Move all css items that must not be overridden by themes (most of them are for the desktop) to caja-desktop.css and keep those that are only needed when themes do not set them at all in caja.css
|
|
inspired by:
https://git.gnome.org/browse/nautilus/commit/?id=dad5d12
|
|
|
|
|
|
|
|
|
|
it wasn't properly unref'ed and caused a runtime warning
|
|
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..)
|
|
|
|
Guard the g_bus_unwatch_name() call to only run when we
actually have set a watcher to the screensaver.
|
|
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
|
|
Closes https://github.com/mate-desktop/caja/pull/372
|
|
This reverts commit 08bc0644ebc869ff1db320cc2bdfc4a471a6f9ac.
|
|
|
|
|
|
|
|
Closes https://github.com/mate-desktop/caja/issues/125
Closes https://github.com/mate-desktop/caja/issues/226
|
|
|
|
|
|
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
|
|
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
|
|
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
|
|
including a silly mistake in caja-window where destroy function's return type
was accidently ommitted during the addition of gtk version checks.
|
|
Also fixes a double-free regression in lc-p/caja-query from 7a42b9b0
|
|
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
|
|
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
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|