Explorer Plugin: Results after 'Tab'-ing into a folder

[luopa]

Is your feature request related to a problem? Please describe.

After listing a folder with explorer plugin, I often wish to further browse into the folder, hence I hit 'Tab'. I'm then presented with the following entry-lines:

• "Open in default file manager. Use '>' to search in [...]"
• [Folder Contents]
• [Folder Contents]
• [...]

When I provide further input, the folder contents are being filtered. However, the "Open in default file manager [...]"-line remains. This forces me to use arrow down in any case to select my target object.

But: If my target was to open the current folder, I would have hit enter already at the beginning. After I start to type further input, I don't need the first line anymore, because I'm targeting another folder or file.

Describe the solution you'd like After browsing into a folder, only display the "Open in default file manager [...]"-line as long as there is no additional text input. As soon es there is, hide the "Open in default file manager [...]"-line.

This allows to "Tab" into a folder, text-input to filter the results towards a target, "Tab" again into folder, etc. (or eventually hit "Enter" or "Ctrl+Enter" (depending on your settings) on the target object).

[github-actions[bot]]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions[bot]]

This issue is stale because it has been open 45 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[taooceros]

Makes sense. Maybe we can get it a fix.

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

[f34r1335]

New Flow Launcher user here, and this was one of the first things I noticed that seemed a bit unintuitive. It's exactly as OP says:

If my target was to open the current folder, I would have hit enter already at the beginning. After I start to type further input, I don't need the first line anymore, because I'm targeting another folder or file.

Ideally it would be even better if I could substitute spaces for tabs. For example in another file launcher I use, for a path like very/long/path/to/folder I could find this folder in many ways (depending on how many matches) such as:

ve lo (or any two letters)
ve pa
ve to fo
pa to
fo
etc, etc.

Thanks.

Edit: Glad to know I just overlooked the setting, found it at: Plugins -> Explorer -> Everything Setting -> Search Full Path

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

[github-actions[bot]]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 60 days.\n\nAlternatively this issue can be kept open by adding one of the following labels:\nkeep-fresh

[github-actions[bot]]

This issue was closed because it has been stale for 7 days with no activity. If you feel this issue still needs attention please feel free to reopen.

[jjw24]

FYI I implemented the result "Open in default file manager. Use '>' to search in [...]" in the early days to let users know these are some further operations you can do. Perhaps we can move this tip somewhere else instead.