rabite0 / hunter

The fastest file manager in the galaxy!
Do What The F*ck You Want To Public License
1.32k stars 64 forks source link

TurboCd prepends '/' to the path #80

Open hasufell opened 4 years ago

hasufell commented 4 years ago

When I type / to switch to TurboCd, then start typing and then cycle through the options in the current dir, it prepends / to those directories. When I want to switch, it does nothing, because they don't exist top-level.

rabite0 commented 4 years ago

Ooops! Will fix that right now.

rabite0 commented 4 years ago

853cf53 fix prepended "/" when completing directory d18836d fix garbage completion with partial directory name and trailing /

Still a bit underwhelming, since it doesn't actually switch to the directory on a unique match (and no further completions without at least one letter). I guess it would be nice if it also filtered everything in the current directory that doesn't match the input.

In a branch I have an overhauled minibuffer with shell syntax highlighting, red/green highlighting for wrong/right filenames, filtered previews for all the executables in $PATH when entering a command and much better navigation (with filtering and automatic dir change)...

I should finish that up, but in the meantime I'll probably add the filter/dir change to it as it is, since that's really nice to have.

hasufell commented 4 years ago

I guess it would be nice if it also filtered everything in the current directory that doesn't match the input.

Exactly! This is a must-have feature imo for fast navigation. Pretty similar to auto-complete in shells. I would go so far to say there should be a mode where all ascii-keystrokes are just filter keystrokes, unless you hit a modifier.

rabite0 commented 4 years ago

Done! While in this mode you can move the selection up/down with history up/down (C/M-p/n by default). Cancelling with C-c resets the directory and the previous selection. "../" does what you would expect.

Open questions:

Nice to have:

hasufell commented 4 years ago

Hmm, it's better, but I was ultimately envisioning something a little more radical.

See, 80% of the time, when using a filemanager, I navigate. The other 20% of the time I interact with files (and want to do operations the filemanager doesn't support, like diffing, taring, ...).

So, IMO, the default mode of a filemanager should always be view only and keypresses should be by default filtering. This is actually the case for e.g. SpaceFM (gtk+). Normal keypresses start a search box and move the selector to the next best match.