Comment 150 for bug 1164016

This is an upstream GNOME bug (though you might want to make the case that Ubuntu should deviate from the default GNOME behaviour for this issue, in which case please open a new bug since I don't think standard practice is to re-open old bugs like this when it has been fixed in an Ubuntu release? I think you could reasonably tag the new bug as a regression. If you do make a new bug for this issue in newer Ubuntu releases then please link to it from here), please +1 (use the thumbs up button on the original Issue and comments that you agree with, don't comment a +1) the following issues to indicate your support for a restoration of type-ahead. On unlocked Issues you can also comment specific use-cases which a lack of type-ahead breaks and which the optimizations mentioned in https://gitlab.gnome.org/GNOME/nautilus/issues/246 and https://gitlab.gnome.org/GNOME/nautilus/issues/247 don't fix (if you think those optimizations would help your use-case then please +1 them). Specific use-cases where you absolutely NEED type-ahead search may change the developers' minds, if you don't have specific use-cases then just +1 comments on GNOME GitLab that you agree with, but we're unlikely to see much change in that case, we NEED specific use-cases:
https://gitlab.gnome.org/GNOME/nautilus/issues/8 (unlocked)
https://gitlab.gnome.org/GNOME/nautilus/issues/244 (locked)
https://gitlab.gnome.org/GNOME/nautilus/issues/466 (unlocked)
https://gitlab.gnome.org/GNOME/nautilus/issues/590 (unlocked)