Faster search navigation

[oleasteo]

Is your feature request related to a problem? Please describe.
I frequently want to navigate several directories deeper by typing parts of the directory names and entering. Currently, I have to type /<search><ENTER><ENTER>/<search><ENTER><ENTER>... This is cumbersome.

Describe the solution you'd like
The / key has no special meaning in the search, cannot be used in file names, and is commonly used to separate directories.
Thus, it could be used to enter the first directory in the view, clear the search, and keep the search focus.

Alternatives
The <TAB> key could also be used instead.

[github-actions]

👋 Hi there, and welcome to superfile!

Thanks for opening your first issue. We really appreciate your interest and involvement.

A maintainer might ask you for more details or clarification to better understand the issue.
That’s totally normal and helps us solve the problem more effectively.

If you plan to submit a PR, make sure to check our Contribution Guide

[cschanhniem]

The / key as a directory separator during search navigation is elegant — it exploits the fact that POSIX filenames cannot contain /, so there's no ambiguity. A few details to lock down for implementation:

1. String splitting on /: Use filepath.SplitList or a manual split on / with the last segment as the incremental search term. When the user types /foo/bar, you want to enter foo/ first (clearing the search input), then start matching bar within foo/. The intermediate navigation moves can use Bubble Tea's filepicker.Model if superfile uses that, or a direct tea.Cmd to change the directory of the file panel.

2. Tab cycling ambiguity: If <TAB> is proposed as an alternative, note that <TAB> already cycles between panels in superfile (left panel ↔ right panel). Reusing <TAB> for search completion would conflict with panel navigation unless it's scoped to search-input focus only. / avoids this because / has no existing binding in search mode.

3. No-match handling: When a segment doesn't match any directory, the behavior should probably fall back to the current fuzzy-search behavior (stay in the current directory, show the segment as part of the search string). This prevents the navigation from trapping the user in a broken path. The worst UX would be silently navigating to a wrong directory because dir2 in /dir1/dir2/dir3 matched something unexpected on partial input.

4. History integration: If superfile keeps a navigation history stack, each /-delimited directory entry should push to the history. This way [backspace] or an explicit back-navigation binding can undo the /foo/bar → enter bar/ step, returning to foo/.