Age | Commit message (Collapse) | Author | Files | Lines | |
---|---|---|---|---|---|
2022-10-29 | tx: update resource | mbkma | 1 | -1954/+2003 | |
2022-10-28 | tx: migrate config file | mbkma | 2 | -6/+16 | |
2022-08-19 | image properties: Look for supported mime types at runtime | rbuj | 1 | -20/+38 | |
See https://gitlab.gnome.org/GNOME/nautilus/-/commit/7aef6be | |||||
2022-08-15 | caja-extensions: print filename when caja failed to open keys file | rbuj | 1 | -1/+1 | |
2022-08-04 | caja-bookmark: 'caja_bookmark_get_uri (CajaBookmark *)' may return NULL | rbuj | 2 | -8/+7 | |
2022-08-04 | configure.ac: Bump Autoconf version because of LT_INIT | rbuj | 1 | -1/+1 | |
2022-08-04 | image properties: Improve the layout | rbuj | 1 | -42/+59 | |
2022-07-22 | Fix build warning -Wmissing-field-initializers | rbuj | 21 | -20/+47 | |
2022-07-22 | Fix build warning -Wbad-function-cast | rbuj | 6 | -22/+43 | |
2022-06-08 | Document and fix default-sort-order preference | Gordon Norman Squash | 2 | -7/+36 | |
This patch resolves three related issues: The first issue was that the GSettings schema for Caja did not include an entry to sort by the "btime", or creation date, of files. If the user chose such an option in the Caja Preferences, GSettings would produce a warning (often out-of-sight, as it was usually redirected into the user's .xsession-errors file), and Caja would not actually change the default sort-order of files. This patch adds the btime as a valid setting in the schema. The second issue was that. because of the above (an entry in the settings schema was missing), some of the alternative sort orders listed in the schema (everything after and including "atime") were not assigned the same numbers as the sort orders listed elsewhere in the Caja source code. Specifically, in icon- and compact-views, if the default sort-order was "emblems", the observed / actual sort-order would be the entry before "emblems", namely "atime" -- so instead of sorting by the names of associated emblems, Caja would sort by each file's access time. An array in the code for the list-view also was missing many values and included some values out of order, so the default sort-order setting affected directories viewed in list-view mode seemingly randomly. The former is taken care of using the fix described in the above paragraph; the latter is fixed in this patch by adding / reorganizing the array for the list-view sort-orders appropriately. The third issue (admittedly, a lesser issue) was that the documentation for the default-sort-order setting was lacking -- it at least did not list all the possible values that the setting could accept. In this patch, I resolve this issue by listing all values in the setting's description, and also go into more detail about what each value does. (However, perhaps I included a little too much detail. It'll only benefit [supposed power users who may already know this stuff] who use GSettings or DConf directly, and it'll certainly be a headache for translators. I'll admit that.) | |||||
2022-06-08 | caja-file-conflict-dialog: Move to automatic signal disconnection | Colomban Wendling | 1 | -20/+11 | |
Instead of manually keeping tabs on the signals so we can disconnect them before the data parameter gets destroyed, let GObject automatically track lifetime of the data, which it can do as that data is a GObject itself. This does not change behavior in the normal case, but makes sure the callback simply cannot get called with invalid/freed parameters, even if we did screw anything up (which we used to). This actually would have solved #1630 as well with using the target widgets as data parameters as the signal would have been disconnected as soon as the widget got destroyed, no matter whether we got finalized ourselves or not. The signal IDs were also use as guards to whether the monitor was set up for the related files, but we can just as well use the state of the file list ready handle which should only be NULL when we actually have monitors set up. Even if it wasn't the case, worse case scenario would be removing a non-existent monitor, which is perfectly OK anyway. | |||||
2022-06-08 | caja-file-conflict-dialog: Properly release references on dispose() | Colomban Wendling | 1 | -6/+19 | |
Fixes #1630. | |||||
2022-06-08 | caja-file-conflict-dialog: update the icons once | rbuj | 1 | -16/+9 | |
2022-06-01 | build: Cleanup long deprecated macros usage | Colomban Wendling | 1 | -8/+7 | |
2022-06-01 | Properly initialize IconKey::scale | Colomban Wendling | 1 | -0/+1 | |
This value is used to look up icons in the cache, but somehow was not properly initialized. | |||||
2022-03-23 | caja-bookmark: Fix build warning -Wlogical-not-parentheses | rbuj | 1 | -1/+1 | |
2022-03-23 | caja-application: Variable is assigned a value that is never used | rbuj | 1 | -2/+1 | |
2022-03-22 | caja-bookmark: fix memory leak | rbuj | 1 | -0/+4 | |
2022-03-22 | caja-bookmark: drop create_image_cairo_for_bookmark | rbuj | 1 | -24/+10 | |
2022-02-09 | Fix implicit conversion changes signedness: 'gboolean' to 'guint' | rbuj | 10 | -57/+57 | |
2022-02-09 | Fix some -Wsign-compare warnings | rbuj | 16 | -63/+75 | |
2022-02-09 | caja-file-operations: overlapping comparisons always evaluate to true | rbuj | 1 | -1/+1 | |
2022-02-08 | remove '-' from a m4_define | Matija Skala | 1 | -3/+3 | |
it was not handled correctly | |||||
2022-01-30 | CI: Drop -Wunused-parameter for debian build | raveit65 | 1 | -1/+1 | |
2022-01-30 | eel-editable-label: remove unused method get_font_description | rbuj | 2 | -10/+0 | |
2022-01-30 | eel-editable-label: drop eel_editable_label_clear_layout | rbuj | 1 | -20/+7 | |
2022-01-28 | caja-property-browser: 'gdk_color_parse' is deprecated | rbuj | 1 | -13/+13 | |
2022-01-28 | caja-property-browser: Fix build warning -Wconstant-conversion | rbuj | 1 | -9/+11 | |
2021-12-31 | caja-module: fix memory leak | rbuj | 1 | -1/+4 | |
2021-12-31 | caja-sidebar-title: fix memory leak | rbuj | 1 | -1/+5 | |
2021-12-31 | fm-directory-view: fix memory leak | rbuj | 1 | -1/+5 | |
2021-12-31 | eel-background: fix memory leak | rbuj | 1 | -4/+10 | |
2021-12-21 | caja-application: avoid SEGV when profiling/debugging code | rbuj | 1 | -2/+1 | |
2021-12-19 | Use gresources for ui files | rbuj | 10 | -18/+41 | |
2021-12-19 | caja-mime-actions: fix memory leak | rbuj | 1 | -2/+9 | |
2021-11-20 | Remove whitespaces before #define, #if, and #endif | rbuj | 2 | -12/+12 | |
2021-11-20 | Use a blank line at most | rbuj | 176 | -709/+0 | |
2021-11-11 | caja-file: Remove unreachable code | rbuj | 1 | -1/+0 | |
2021-11-08 | caja-places-sidebar: fix right-click menu height | Benjamin Heiniger | 1 | -7/+18 | |
* caja-places-sidebar: fix right-click menu height - prevent error and right-click menu from appearing when clicking empty area | |||||
2021-11-08 | caja-dnd: wrong type field in printf format string | rbuj | 1 | -1/+1 | |
2021-10-11 | Fix Caja does not show icons of application launchers | mouse | 1 | -1/+1 | |
in /usr/share/applications and asks user for confirmation on launch of desktop-files here | |||||
2021-08-04 | release 1.26.0v1.26.0 | raveit65 | 2 | -33/+38 | |
2021-08-04 | tx: sync with transifex | raveit65 | 119 | -11319/+10878 | |
2021-08-04 | travis-Ci: use libera.chat as notification server | raveit65 | 1 | -1/+1 | |
2021-08-04 | tx: update resource | raveit65 | 1 | -92/+92 | |
2021-06-18 | Update copyright to 2021 | raveit65 | 16 | -2/+16 | |
2021-05-29 | release 1.25.3v1.25.3 | raveit65 | 2 | -4/+40 | |
2021-05-29 | tx: pull from transifex | raveit65 | 119 | -102455/+106626 | |
2021-05-29 | tx: update resource | raveit65 | 1 | -90/+86 | |
2021-05-29 | travis-ci: use ubuntu focal as host system | raveit65 | 1 | -1/+1 | |
fixes build issues with fedora:latest (f34) tag. |