summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* README: Add hello worldadding-hello-worldCarlos Soriano2019-04-042-2/+2
| | | | | | | | The README was not welcoming enough Add hello world to the README Closes https://gitlab.gnome.org/GNOME/nautilus/issues/973
* Update .triage-policies.ymlCarlos Soriano2019-03-211-1/+1
|
* Flatpak: Remove gtk4 manifestCarlos Soriano2019-03-212-122/+0
| | | The gtk4 branch should have the proper manifest already
* Flatpak: Use Devel profile for Master and Gtk4Carlos Soriano2019-03-211-4/+4
| | | Was giving errors in the CI and doesn't really provide much benefits
* CI: Remove OpenSuse and UbuntuCarlos Soriano2019-03-211-61/+0
| | | | | Errors are usually old deps or such, and needs someone taking care of those. It's not much of a benefit upstream, so let's remove them.
* Update .gitlab-ci.ymlCarlos Soriano2019-03-201-2/+2
|
* window-slot: Don't initialize extra widgets if content view is not yet setAndrea Azzarone2019-03-191-1/+6
| | | | | | | | | | The signal 'trash-state-changed' could be emitted by NautilusTrashMonitor while a NautilusWindowSlot is still initializing the content view. In this case, don't show/hide extra location widgets to avoid deferencing invalid memory. They will be created anyway once the content view has been set. Closes: https://gitlab.gnome.org/GNOME/nautilus/issues/890 Closes: https://gitlab.gnome.org/GNOME/nautilus/issues/862
* Fix build in ClangAlbert Vaca Cintora2019-03-181-0/+2
| | | | | | I was getting: error: variable 'string' is used uninitialized whenever 'if' condition is false [-Werror,-Wsometimes-uninitialized]
* bookmark-list: Fix memory leakYi-Soo An2019-03-181-2/+2
| | | | | | | According to the documentation[1], GFileMonitor object must be freed when it is not necessary. g_file_monitor_cancel() doesn't free the object. [1]: https://developer.gnome.org/gio/stable/GFile.html#g-file-monitor-file
* bookmark-list: Clean up codeYi-Soo An2019-03-181-5/+7
| | | | | Clean up do_finalize method to use NautilusBookmarkList object instead of casting to itself every lines.
* Update .gitlab-ci.ymlCarlos Soriano2019-03-181-0/+2
|
* release: Prepare for 3.32.03.32.0Carlos Soriano2019-03-132-1/+4
|
* Flatpak: Sync json from yamlCarlos Soriano2019-03-131-133/+138
| | | | Generate the json from the yaml file.
* flatpak: Add --share=network to fix synchronous gvfs connectionsOndrej Holy2019-03-133-0/+3
| | | | | | | | | | | | | | | | | | | GVfs communicates with daemons over abstract sockets. Currently, synchronous GIO API doesn't work for GVfs locations, because abstract sockets seem to be blocked by sandbox permissions. This is not problem in most cases as Nautilus uses asynchronous API usually. But this breaks e.g. "Empty Trash" functionality as it is for some reason based on synchronous API. In order to fix this problems, it is necessary to allow access to sockets beginning with `unix:abstract=/dbus-vfs-daemon/socket-`, but I am not aware of better way than adding `--share=network`, which allows access to all abstract sockets: http://docs.flatpak.org/en/latest/sandbox-permissions-reference.html#f2 Just a note that it is not clear to me, why it affects only the synchronous API as the asynchronous API also uses abstract sockets. See the corresponding Flatpak bug: https://github.com/flatpak/flatpak/issues/2711
* Updated Slovenian translationMatej Urbančič2019-03-121-250/+267
|
* Update Greek translationEfstathios Iosifidis2019-03-091-31/+4
|
* Update Belarusian translationUladzimir Manulenka2019-03-081-758/+1003
|
* Update French translationCharles Monzat2019-03-081-791/+1043
|
* Update Esperanto translationKristjan SCHMIDT2019-03-061-467/+703
|
* Update Latvian translationRūdolfs Mazurs2019-03-041-757/+1021
|
* Updated Danish translationAlan Mortensen2019-03-031-18/+36
|
* Update Romanian translationDaniel Șerbănescu2019-03-021-839/+1080
|
* Update Dutch translationNathan Follens2019-03-011-234/+234
|
* Update Serbian translationМарко Костић2019-02-281-552/+798
|
* Update Italian translationMilo Casagrande2019-02-281-1209/+965
|
* Update Korean translationChangwoo Ryu2019-02-281-729/+979
|
* Updated Vietnamese translationTrần Ngọc Quân2019-02-281-728/+971
| | | | Signed-off-by: Trần Ngọc Quân <vnwildman@gmail.com>
* Update Friulian translationFabio Tomat2019-02-271-158/+382
|
* README: Include tracker miners in rundepsCarlos Soriano2019-02-271-1/+1
|
* Update Brazilian Portuguese translationRafael Fontenelle2019-02-271-805/+1045
|
* Update Russian translationStas Solovey2019-02-251-733/+978
|
* Fix a wrong string in the German translation - bug #797393Andre Klapper2019-02-251-1/+1
|
* Update Dutch translationNathan Follens2019-02-251-770/+991
|
* canvas-container: Remove unused signalCarlos Soriano2019-02-252-15/+0
| | | | | | | To be honest I don't know when it was used and where, but it's unused now. Fixes: https://gitlab.gnome.org/GNOME/nautilus/issues/801
* Update Basque translationAsier Sarasua Garmendia2019-02-241-4351/+1879
|
* Update Catalan translationJordi Mas2019-02-231-17/+35
|
* Update Japanese translationRyuta Fujii2019-02-231-343/+599
|
* search-engine-simple: Make some modifications to previous commitCarlos Soriano2019-02-221-69/+62
| | | | | | * Cleaner separation of phases * Avoid some races * Fix some leaks
* nautilus-search-engine-simple: Only spawn one idle each timeXiang Fan2019-02-221-23/+103
| | | | To avoid clogging up the main loop.
* eel-graphic-effects: Make hover light less intenseCarlos Soriano2019-02-221-1/+3
| | | | | | With the new icons most of the area was white. Fixes: https://gitlab.gnome.org/GNOME/nautilus/issues/827
* Apply suggestion to src/nautilus-directory-async.cCarlos Soriano2019-02-221-1/+1
|
* nautilus-directory: Implement monitor list with hash tableXiang Fan2019-02-223-74/+187
| | | | | The original linked list can be O(n^2) (n = the number of files) in the worst case.
* file: replace eel_ref_str with GRefStringJordan Petridis2019-02-228-223/+89
| | | | | | | | | | | | | | | | | glib now offers a reference counted api. This allows us to replace a lot of legacy code and get rid of eel_ref_str. GRefString [1] is almost a drop-in replacement. nautilus-file-operations.c was indirectly depending upon eel/eel-string.h from nautilus-file-private.h and thus a new include was added. This bumps the minimum version of glib to 2.58 Close #781 https://gitlab.gnome.org/GNOME/nautilus/issues/781 [1] https://developer.gnome.org/glib/stable/glib-Reference-counted-strings.html
* Update Polish translationPiotr Drąg2019-02-211-5/+5
|
* Update Icelandic translationSveinn í Felli2019-02-211-1062/+1119
| | | | (cherry picked from commit 9b69e5eb8f14b251390fd8dd7c8e20863acbff41)
* Update German translationTim Sabsch2019-02-211-349/+593
|
* Update Finnish translationJiri Grönroos2019-02-201-119/+338
|
* nautilus-list-view: Clear selection and cursor in clear()Xiang Fan2019-02-191-0/+31
| | | | | | | | | | | | | | | | | | When the current cursor's row gets deleted, GTK will move the cursor to the next row, and when setting the cursor it also selects the new cursor's row, thereby triggering selection signals. The new cursor will soon be deleted again and the loop repeats. Since clear() removes all entries, those selections are useless but they take up most of the time in clear(). For example, when a search returns a large list, exiting from the search view would make nautilus hang. At the time simply removing the cursor solves the problem, but to be future-proof in case GTK does anything fancy with the current selection, this commit also removes the selection. Because GTK internally seeking the cursor takes time, only blocking the selection signal like everywhere else will not remove that overhead.
* search-popover: Make search-popover modalGeorge Mocanu2019-02-191-1/+1
| | | | | | | | | | | | Currently, the search popover is not dismissed when clicking outside. Clicking anywhere other than on popover should close the popover. This patch fixes this behaviour by making the search-popover modal. Closes https://gitlab.gnome.org/GNOME/nautilus/issues/528
* triage-policies: Change feature closing to updated_atCarlos Soriano2019-02-181-3/+3
| | | | It could create bad blood to close a recently discussed or updated issue...