summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* test: Add copy operation undotestsalex-fazakas-operations-undo-redoAlexandru Fazakas2018-07-311-3/+831
| | | | | | | This patch adds undo tests for the copy operations. Redo is not included as undo for copy means permanently deleting the copied files, which renders redoing pointless.
* test: Add undo/redo tests for move operationAlexandru Fazakas2018-07-311-6/+1612
| | | | | This patch adds undo and redo testing for each test on the synchronous move operation.
* file-operations: Set sync operations undo infoAlexandru Fazakas2018-07-311-3/+59
| | | | | | | Since most synchronous operations rely on g_task_run_in_thread_sync and this doesn't reach callbacks, we need to manually set the undo info. This patch fixes this by moving the callback function content in-line.
* css: pathbar hover touchupsJakub Steiner2018-07-301-1/+1
| | | | | | - get rid of whitespace between border and the folder. https://gitlab.gnome.org/GNOME/nautilus/issues/548
* file-operations: Fix undo copy criticalsAlexandru Fazakas2018-07-301-1/+1
| | | | | This is a follow-up to commit e9f039e1 which fixes all introduced criticals and sets the undo information properly.
* files-view: Sink floating refs on initializationAntónio Fernandes2018-07-301-4/+2
|
* files-view: Use current-directory-properties on backgrond menuAntónio Fernandes2018-07-301-2/+2
| | | | | | | | | | The view.properties action opens the current directory properties when the selection is NULL, which we assume to be the case when opening the background context menu. Instead of relying on this assumption, make the background context menu use the view.current-directory-properties action which is used by the current location menu in the pathbar.
* Revert "files-view: Streamline properties actions paths"António Fernandes2018-07-302-8/+20
| | | | | | | | | | | | This reverts commit ee75ea771763b4a7fcef5fd61d3c790e688d88e5. It was pushed too early, caused criticals, and broke keyboard shortcuts. There is value in keeping a generic "view.properties" action which deals with both selection and no selection, because we want the <Ctrl><i> and <Alt><Return> accelerators to do the right thing in both cases.
* flatpak: add space after (Development) prefixWill Thompson2018-07-292-2/+2
| | | | | Without this, the app name comes out as "(Development)Files". No functional issue, just ugly.
* flatpak: Update GTK+ 4 manifestErnestas Kulik2018-07-281-26/+6
| | | | | | | This commit builds master Tracker with Meson and removes a redundant finish argument. (cherry picked from commit f42bca38528a64d92e4e7f47865bb0a0133580cd)
* pathbar: Change border-radius to 3px for AdwaitaAlexander Mikhaylenko2018-07-271-1/+1
| | | | | Be consistent with buttons and entries and make transition from or to search entry more seamless.
* Revert "files-view: close menu when new folder prompt appears"António Fernandes2018-07-273-15/+0
| | | | | | | This reverts commit 0453216b8a6731d92cfcd6405c323d76c0c1182c. Nowadays, the view menu doesn't have a new folder action so this is not needed anymore.
* files-view: Streamline properties actions pathsAntónio Fernandes2018-07-272-20/+8
| | | | | | | | | | | The view.properties action opens the current directory properties when the selection is NULL, which we assume to be the case when opening the background context menu. Instead of relying on this assumption, make the background context menu use the view.current-directory-properties action which is used by the current location menu in the pathbar. Also, rename view.properties to view.selection-properties and specialize it.
* ui-utilities: Move menu pop up code to files-viewAntónio Fernandes2018-07-273-44/+10
| | | | | | | | | | | | | | | In the past, nautilus_pop_up_context_menu_at_pointer() was the common path for popping up context menus from the view and pathbar. However, different paths were introduced in commit 29cf64bd7632b25dd56a275078da6130b201edeb and commit 489d4d091e7006f0ec68849e836a52119af88959, which share some code but couldn't use this API. Now that the pathbar context menus are gone, this is actually causing more code duplication while making it harder to read. Instead, handle everything in files-view.c.
* Update German translationTim Sabsch2018-07-271-530/+556
|
* Updated Spanish translationDaniel Mustieles2018-07-271-485/+514
|
* toolbar-switcher: Don't expandAntónio Fernandes2018-07-261-2/+2
| | | | | | It breaks proper centering in the header bar. Fixes https://gitlab.gnome.org/GNOME/nautilus/issues/554
* meson: Bump version3.29.90.1Carlos Soriano2018-07-262-2/+2
|
* rename-file-popover: Fix Glade overriding marginsCarlos Soriano2018-07-261-1/+5
| | | | And setting can_focus false by default...
* release: Prepare for 3.29.903.29.90Carlos Soriano2018-07-261-0/+38
|
* pathbar: Add translator comments for new stringsAntónio Fernandes2018-07-261-0/+5
|
* new-folder-dialog-controller: Stop translating a dotPiotr Drąg2018-07-261-1/+1
|
* toolbar: Add missing mnemonicsPiotr Drąg2018-07-261-5/+5
|
* preferences-window: Add missing mnemonicPiotr Drąg2018-07-261-1/+1
|
* preferences-window: Remove unneeded context and commentPiotr Drąg2018-07-261-1/+1
|
* Update POTFILES.inPiotr Drąg2018-07-261-1/+0
|
* pathbar: Show label for administrator rootAntónio Fernandes2018-07-261-8/+14
| | | | | | | | | | Similar problem to the previous commit. Ideally, we should simply call it "Computer", since it is the same location. But we currently lack an effective visual clue that the admin: backend is in use. For that reason, label it "Administrator root" istead.
* pathbar: Show label for filesystem rootAntónio Fernandes2018-07-261-14/+5
| | | | | | | | | | | | When current location is "/", the pathbar is (icon)(slash)(arrow), which looks bad because that's 3 symbols in sequence. Also, the slash ("/") label duplicates the pathbar separator if current location is a child. Instead, call it "Computer", which is the label used in Other Locations Fixes https://gitlab.gnome.org/GNOME/nautilus/issues/414
* general: Remove trash shortcut changed handlingCarlos Soriano2018-07-265-79/+1
| | | | | | | It was introduced in 3.14, most probably everyone is in a newer version already... Time to clean up!
* folder-is-empty: Use GladeCarlos Soriano2018-07-261-10/+14
|
* trash-is-empty: Use GladeCarlos Soriano2018-07-261-11/+15
|
* starred-is-empty: Use GladeCarlos Soriano2018-07-261-10/+14
|
* rename-file-popover: Use GladeCarlos Soriano2018-07-261-12/+23
|
* progress-info-widget: Use Glade and update to gtk 3.20Carlos Soriano2018-07-261-29/+35
|
* no-search-result: Use GladeCarlos Soriano2018-07-261-10/+15
| | | | And update to gtk 3.20
* preferences: Update to gtk 3.20 Glade generated fileCarlos Soriano2018-07-261-31/+21
| | | | So we get rid of deprecated properties
* preferences: Fix General label context for translatorsCarlos Soriano2018-07-261-1/+1
| | | | Not so obvious in Glade.
* preferences: Remove experimental view settingsCarlos Soriano2018-07-262-55/+0
| | | | | | | It went worse than I expected, it's a "break me please" setting, which we are generally against. It can still be enabled through dconf.
* search-engine-recent: use #pragma once for guardingMarco Trevisan (Treviño)2018-07-261-4/+1
|
* search-engine: move simple engine inclusion to .c fileMarco Trevisan (Treviño)2018-07-262-1/+1
| | | | No need to keep this in the header anymore
* search-engine: add a recent-search-engine listing GtkRecentManager entriesMarco Trevisan (Treviño)2018-07-264-0/+476
| | | | | | | | | | | Using GtkRecent items as search engine source in nautilus. The main reason for this, is being able to get fast results on recently-used files from the shell search provider. This is disabled when recursive searches are disabled, as there's no need to go through for recent files if no recursive (or indexed) search is enabled as the simple engine will be already fast enough, while running this engine could be just a waste.
* flatpak: Tweak GTK+ 4 manifestErnestas Kulik2018-07-261-88/+90
| | | | | | | | | This pins versions of most dependencies, uses quotes for strings and removes header cleanup from GTK+ module, because CI pipelines choke on them being absent when ninja decides to rebuild everything when running tests. (cherry picked from commit a9f13fc91f7319b318e75a95a89918e9cadf94cf)
* file-operations: Fix undo-duplicate criticalAlexandru Fazakas2018-07-261-13/+13
|
* flatpak: Use meson for gexvi2Carlos Soriano2018-07-264-4/+16
| | | | Life's much better now.
* toolbar: Adjust width requirementsCarlos Soriano2018-07-262-2/+2
| | | | | | | | So we allow half sized windows in 1360px screens. This is delicatily adjusted with the default GNOME set up: Adwaita theme, only close button as window controls and Cantarell as font. Closes https://gitlab.gnome.org/GNOME/nautilus/issues/425
* preferences-window: Expose show sidebar settingCarlos Soriano2018-07-262-88/+100
| | | | Since we want to replicate inside Nautilus what's in the app menu.
* toolbar: Fix window slot handlingErnestas Kulik2018-07-261-58/+77
| | | | | | | | | | | | | | Calling _set_window_slot() in the window slot weak ref notification callback isn’t a good idea, given that most of the stuff being cleaned up there is done automagically, and results in runtime warnings or potentially a segfault when removing a property binding. This commit split nautilus_toolbar_set_window_slot(), so that property bindings aren’t removed if called from the weak reference notification function. Additionally, the same notification functions nulls out the icon property binding, fixing the same thing happening in dispose(). Fixes https://gitlab.gnome.org/GNOME/nautilus/issues/441
* toolbar: Remove unused fieldErnestas Kulik2018-07-261-3/+0
| | | | The view widget binding is no longer created.
* file-view: Always unset pending_selection after freeing itMarco Trevisan (Treviño)2018-07-261-9/+5
| | | | | | | | | | | | | | | | | When a file view was loaded with a pending selection, and not all the files were seen yet, the private pending_selection list was properly free'd, but the pointer was not cleared, causing a crash when `nautilus_files_view_set_selection` was called again, as it was trying to deeply copy a list pointed by this invalid reference. So, removing the unneeded `pending_selection` temporary pointer from the main function scope, as it only confuses, while use it (with an autolist) when we need to pass the previous `priv->pending_selection` (stealing its ownership) to set_selection again. Eventually use a g_clear_pointer to free the list and nullify its priv reference Fixes #295
* file-utilities: Use proper switch/case code styleCarlos Soriano2018-07-261-1/+12
|