[Bug 1164016] Re: restore type-ahead find
I don't know how long it will take, but in the meantime Ubuntu could ship the patch maintained by the Arch community: https://aur.archlinux.org/cgit/aur.git/tree/nautilus-restore- typeahead.patch?h=nautilus-typeahead It looks like this patch is kept up to date pretty well. There is a similar patch for gtk3 to make the file chooser dialog have type-ahead. It's the best of both worlds, since you can still tap ctrl-f to search. Whilst it would be nice for the Nautilus devs to upstream the patch or for there to be a dialog about what kind of patch they might accept (if any), in the meantime distros can include the patch, there is little downside since the patch is maintained and not bit rotting. Canonical would not be committing themselves to maintaining it by including it. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1164016] Re: restore type-ahead find
I don't think it's true that an option is always good. I think software should endeavour to have decent default options, and if multiple use cases can be accommodated without an option, then that is preferable. But you're right, a recursive search with ctrl-f vs typeahaed with simple typing would accomplish what everyone wants without an option. I'm using the 'search in current folder only' setting in order to make the search more like typeahead, but this has the downside that I have to go into the settings to do an actual recursive search. In reality, recursive search is useful, and I want to use it, but it's different to typeahead and it's a shame I have to pick one or the other. Ideally for me would be typing is just going to select things similarly to the old typeahead behaviour, and ctrl-f would do a search, either in the current folder or recursively depending on a checkbox that would ideally be in the main interface next to the search box rather than in the settings menu - since one often wants one or the other, it's not really an all-time preference. I do think things will eventually go back this way. There is currently wasted effort trying to make search meet the requirements of type-ahead, whereas this would be unnecessary if typeahead existed too. Search is becoming a bit of a frankenstein trying to be both, with returning items from the current folder first, and having the search-in-current-folder- only setting being global. It should just be search - features should do one thing each instead of trying to please everyone. I understand that search has been improved a lot in response to complaints about type-ahead being removed, and this shows that the devs are trying to meet people's use cases. But ultimately I think it is misguided and making the search implementation more complex than it otherwise would need to be. They are really are different features. So I know there has been a lot of vitriol over this issue, but I would encourage the nautilus devs to consider that they should become different features once again. Ctrl-f to search will not confuse anybody, type-ahead will not confuse anybody, whereas the current search is trying to be both and so can behave unexpectedly in terms of the order of search results and whether the search is recursive. Presumably this means code complexity too. I also understand that the old type-ahead code was holding back the codebase and so it was desirable to excise it. I imagine new typeahead functionality, working as much as possible within the current codebase and its future directions, would be more amenable to nautilus dev approval than just restoring the old code. For example, we probably don't need the popup box in the bottom right as you type. It should just be type a few characters and have a few-second timeout before forgetting them, just like it is on other platforms such as windows and macos (I think). It seems similar to me to the case or removing nautilus handling the desktop. The code was holding back the codebase, but now we see that a desktop extension for gnome-shell is in development by the main nautilus dev. I do think Nautilus can satisfy everyone's preferences here, and I do think typeahead will eventually be re implemented once tensions die down, especially if the nautilus devs can do it on their terms instead of rejecting a patch that just re-adds code that they don't want to maintain. A good typeahead implementation would even allow Nautilus to remove code that customises how the search works to make it more useful as typeahead - there would no longer be a need for that if typeahead were present in its own right. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1164016 Title: restore type-ahead find To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1164016/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 326582] Re: sort order of files listings in nautilus is not alphabetical
On major problem with this search order is that it conflicts with the order of files in Nautilius in the non-search view. In my home folder I have 'thesis' and 'tmp' subfolders, and they are shown in that order. I type 't' expecting 'thesis' to be the first result so that I can hit enter and navigate to the 'thesis' folder. However 'tmp' comes up first because Nautilus's search view is sorting by length before aphabetically, or something (not sure what the exact algorithm is). This is one of the behaviours preventing the new search interface from being used for keyboard navigation as a replacement for the removed typeahead functionality. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/326582 Title: sort order of files listings in nautilus is not alphabetical To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/326582/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767027] Re: Search current folder only in nautilus doesn't work (Ubuntu 18.04)
I tested with nautilus 1:3.26.4-0~ubuntu18.04.1 and the issue is fixed for me. Thank you! :) ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
Lubomir, what changes were required on top of the arch patch to work with 3.26.3? I'm using the Arch patch as-is on Ubuntu 18.04 and there don't appear to be any problems that I've noticed so far. But assuming your changes are necessary, could you publish them somewhere? It would be great to maybe have a public git repo that people could contribute to to maintain patches for the latest few versions of Nautilus that are in common use. Ubuntu devs - now that there is a working patch again (and seemingly the will to maintain it by the arch community and others), might Ubuntu be able to ship a patched nautilus once more restoring this behaviour? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/181 Title: Restore interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
That example was my home directory, and all the files were either in my home directory or a subfolder. Attached is another example from within the root directory a python project 'zprocess', searching for 'py'. Here is the result of the find command (excluding hidden files and folders): zprocess $ find . -not -path '*/\.*' -name '*py*' | sort ./doc/conf.py ./run_tests.py ./setup.py ./tests/output_redirection.py ./tests/tests.py ./zprocess/clientserver.py ./zprocess/examples/example_client.py ./zprocess/examples/example_server.py ./zprocess/examples/processclass_example.py ./zprocess/__init__.py ./zprocess/locking/__init__.py ./zprocess/locking/__main__.py ./zprocess/process_class_wrapper.py ./zprocess/process_tree.py ./zprocess/remote/__main__.py ./zprocess/security.py ./zprocess/utils.py ./zprocess/zlog/__init__.py ./zprocess/zlog/__main__.py As far as I can tell, it is performing search as if 'search in subfolders' option was set to 'On this computer only', even though the preferences interface shows it set to 'never'. If I search a remote location it appears to correctly limit search to the current directory. ** Attachment added: "Screenshot" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138287/+files/nautilus_bug_2.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
Attached is a screenshot of the preferences dialog with my current settings. ** Attachment added: "Settings dialog" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138288/+files/nautilus_settings.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767027] Re: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
I'm using 1:3.26.3-0ubuntu4 Attached is a screenshot demonstrating the problem ** Attachment added: "screenshot of nautilus bug" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+attachment/5138067/+files/nautilus_search_bug.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 484043] Re: double click full screen plugin - undesired behaviour
No longer valid due to overlay scrollbars ** Changed in: eog (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/484043 Title: double click full screen plugin - undesired behaviour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/484043/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767030] [NEW] Nautilus does not focus search bar upon typing if search bar already is visible
Public bug reported: (Nautilus 3.26.3 on Ubuntu 18.04, but bug has been present as long as the new search box has existed to my knowledge) If you start typing in nautilus, so long as no text field anywhere is focused, the search box will appear and get focus, so you end up typing into it. However, if the search box is already visible but does not have focus (for example, by tapping ctrl-f and then clicking outside the search box), then typing does not re-focus the search box. This is jarring since you can be looking at a normal view of a folder (not at search results), and out of habit expect that you can start typing to search. Even if you tap ctrl-f, this makes an empty search box *vanish*, so you have to tap ctrl-f *twice* to get it focused (or click on it of course) Solutions include: * Make an empty search box always vanish upon losing focus * Make an empty search box, if still visible, gain focus again if the user starts typing. The first solution is probably cleanest since there is no use case I can think of for leaving an empty search box visible if the user is not about to type into it. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767030 Title: Nautilus does not focus search bar upon typing if search bar already is visible To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767030/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1767027] [NEW] Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04)
Public bug reported: I upgraded to Ubuntu 18.04 prerelease from Ubuntu 17.10 and am finding that Nautilus searches all subfolders when I start typing, not just the present folder, even though I have the "search only current folder" option selected in its preferences, and "Only searching the current folder" does appear in the GUI as I am searching. Nonetheless results appear from subfolders (which I wouldn't mind, but which I turn off due to its poor performance compared to current-folder-only). ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1767027 Title: Search current folder only in nautilus 3.26.3 doesn't work (Ubuntu 18.04) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1767027/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1682542] Re: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc
Agreed. Distinguishing between monitors serves no purpose. Like everyone else I have strong muscle memory to look to the top right of my screen when I want to see status indicators, or to look to the top to see the time, or to move my mouse to the top right to change the volume. This muscle memory has no concept of whether I am looking at my 'primary' monitor or not, and feels a half second of confusion each time I try to do one of these things on a second monitor, which is the hallmark of bad interface design. I think I'm subconsciously adapting to just not use the second monitor much, and that's a stupid outcome too. Of course indicators have nothing to do with the specific monitor they're on, but they have nothing to do with the primary monitor either, so why are they there? They're there to give quick visual and interactive access to certain frequently accessed information and functionality, quick enough that you apparently don't want to have to hit a few keypresses to get them. By the same logic you shouldn't have to drag your mouse over increasingly large screen real estate. Unity had it right in this regard. There should be just monitors, no primary or secondary. It's a pointless distinction, and whilst I accept it might be technically difficult to achieve given the current architecture of gnome-shell, to insist on it as a design decision is silly. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1682542 Title: Add support for top bars on all monitors to allow for multi-monitor support in primary extensions - apps-menu, places-menu, topbar, etc To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1682542/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1005729] Re: gnome-terminal resizes to max height when mousing over gnome panel
I'm experiencing this bug too. The deciding factor as to which windows move and which don't, when I mouse-over the launchers on gnome-panel, appears to be whether that window has at any point in the past had an overlap outside of the screen struts, ie it has been anywhere that a newly created or maximised window could not be. So if I drag a window halfway off the bottom of the screen, or a few pixels underneath a panel, even if I drag it back, it will then move around randomly whenever I mouse-over the launchers on gnome-panel. It's kinda weird. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-panel in Ubuntu. https://bugs.launchpad.net/bugs/1005729 Title: gnome-terminal resizes to max height when mousing over gnome panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1005729/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 550004] Re: Open with Other Application remember feature does not work
Still experiencing this bug in Nautilus 1:2.32.0-0ubuntu1.1 under ubuntu 10.10 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. https://bugs.launchpad.net/bugs/550004 Title: Open with Other Application remember feature does not work -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 484043] [NEW] double click full screen plugin - undesired behaviour
Public bug reported: Binary package hint: eog This bug/feature request regards eye of gnome 2.28.1, which I'm running on ubuntu 9.10. When the Fullscreen with double click plugin is enabled, and when viewing a large image full screen, there is is scroll bar on the right. Clicking the scroll arrows scrolls as desired, but if you click too rapidly, it counts as a double-click and the image reverts back to being displayed in a window. The same applies when viewing in a window and scrolling, double-clicking the scroll arrows triggers the image to be displayed fullscreen. Since clicking scroll buttons rapidly is pretty common, I think the desired behaviour for this should be that double clicks be ignored on the scrollbar and only trigger the fullscreen/window change when they are on the image itself. ProblemType: Bug Architecture: amd64 Date: Tue Nov 17 17:50:35 2009 DistroRelease: Ubuntu 9.10 ExecutablePath: /usr/bin/eog InstallationMedia: Ubuntu 9.10 Karmic Koala - Release amd64 (20091027) Package: eog 2.28.1-0ubuntu1 ProcEnviron: LANG=en_AU.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-14.48-generic SourcePackage: eog Uname: Linux 2.6.31-14-generic x86_64 ** Affects: eog (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- double click full screen plugin - undesired behaviour https://bugs.launchpad.net/bugs/484043 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 484043] Re: double click full screen plugin - undesired behaviour
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/35775567/Dependencies.txt ** Attachment added: ProcMaps.txt http://launchpadlibrarian.net/35775568/ProcMaps.txt ** Attachment added: ProcStatus.txt http://launchpadlibrarian.net/35775569/ProcStatus.txt ** Attachment added: XsessionErrors.txt http://launchpadlibrarian.net/35775570/XsessionErrors.txt -- double click full screen plugin - undesired behaviour https://bugs.launchpad.net/bugs/484043 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
