Age | Commit message (Collapse) | Author | Files | Lines |
|
On this mode, after opening a folder, the hand cursor was used until the user
moved the cursor over a file or folder.
Based on Nautilus commit
https://git.gnome.org/browse/nautilus/commit/?id=2644c6ef4e7839e976d4861d6c86e16e34d46a13
|
|
Only those which match application/x-desktop directly.
Apply Nautilus commit
https://github.com/GNOME/nautilus/commit/b241fd28913e87fe01419e4922259949a11c973f
|
|
|
|
Apply https://git.gnome.org/browse/nautilus/commit/?h=gnome-3-4&id=b9c51fd4eb84a9f52ee4be1bf183fc516984130b
via
https://gist.github.com/raveit65/19cfc5fe706ac6a2ea5d663a94fb02af
|
|
|
|
|
|
|
|
This makes the string exposed to ATK more sensible, instead of having
unrelated words coupled together.
|
|
|
|
|
|
|
|
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
|
|
|
|
|
|
Fix for https://github.com/mate-desktop/caja/issues/686
Also checked in XFCE to make sure unkillable caja process did not return
Note that the combination of no icons on the desktop with exit on last window will still trigger a restart loop just as it always has
|
|
just to make sure it won't be built against GTK+2 version
|
|
|
|
|
|
option
*Remove GTK_VERSION_CHECK (3, 0, 0) and libunique selectors
*Remove GTK2 and libunique specific code.
*Leaves selector for specific GTK3 versions.
*Remove #DEFINES for vbox/hbox previously required for GTK2 compatability
*Keep vbox in caja-spatial-window.c, it is necessary for the desktop to work
*spatial-window vbox issue at https://github.com/mate-desktop/caja/issues/591
|
|
Since https://github.com/mate-desktop/caja/commit/edb2cc870fa87cf1c57a61c0af5c578461b20a20 we use /usr/include/libnotify/notify.h so check for it.
|
|
|
|
same as done upstream:
https://git.gnome.org/browse/nautilus/commit/?id=41da60c3a7156e504f7cf89cea87be49ef75a89c
it's not used after 7008129b5a16ceceafc3dd5868a8317b35561768
|
|
Apply https://git.gnome.org/browse/nautilus/commit/?id=87d24047f674ca941e2691602da2501945a82330
|
|
|
|
Apply patch by ZenWalker for horizontal scrollwheel mice, without it
scrolling left or right scrolls right only
|
|
Apply Nautilus commit https://github.com/GNOME/nautilus/commit/0832acdb4371fc7de957303e220e899c8fdcdf5c
|
|
based on nautilus commit:
https://git.gnome.org/browse/nautilus/commit/?id=b370817
Fixes partially #535
|
|
Do not send "it is not safe to remove the drive" notifcation on unmount of internal drive or other non-ejectable device. Also stop incorrect notification on cancelled eject operation (as when mounted by another user and not authorized to eject).
|
|
Defaults to TRUE
|
|
We no longer need to use any GtkApplication features for this so enable it in libunique builds too. Tested with and without libunique in GTK 3.22
|
|
The desktop icon eject code required a function in libcaja-private so we no longer need it in caja-application.c
|
|
Show desktop notifications for ejecting a drive from the desktop as well.The code in caja-file-operations won't show notifications from the sidebar so that code is still needed too.
|
|
Notify users when an external drive is still writing data on attempt to eject, and again when drive is safe to unmount. Notifications behave as they do in Nemo when ejecting/unmounting a flash drive. Tested with GTK 3.22 and a known slow flash drive.
This is in GtkApplication builds only, code is from Nemo. FIXME: build system does not limit libnotify dependency to GtkApplication builds and is rather improvised. Adding libnotify to CORE_MODULES via configure.ac did not work, and using Nemo's changes put -lnotify into CORE rather than ALL libs and that caused build failures on failure to link.
|
|
This text was borrowed from Nautilus 3.0 commits used in GtkApplication port, where all Nautilus references were changed to Caja
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|