all 22 comments

sorted by: hot top controversial new old
[–] 18 points 2 years ago* (4 children)

Also if you are looking for a replacement for find that is not a full tui then take a look at fd which works more like what the author expected from the find commad - fd <pattern>.

  • source
  • hideshow 4 child comments
  • [–] 1 point 2 years ago* (last edited 2 years ago) (3 children)

    Plus, IIRC fd does breadth-first search, which leads to faster finds in the most common cases.

    I've been corrected. fd doesn't do this; other find replacements exist that do, though.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 2 points 2 years ago (2 children)

    I don't think so, where did you get that? Last I checked, they weren't interested in adding it. That's why tools like bfs exist.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 13 points 2 years ago (2 children)

    find can be a bit slow because it enumerates every directory recursively from the root you specified, but it let's you do a lot more than just search by name. locate is available on most distros and give fast results, albiet from when the index was last rebuilt (usually nightly). They both have the vital property that they output a list of files to stdout for further processing.

  • source
  • hideshow 2 child comments
  • [–] 8 points 2 years ago

    Sounds fantastic, but unfortunately none of the instructions for Debian-based, or the pre-compiled binary, or the building from source worked.

  • source
  • [–] 7 points 2 years ago

    So many linux posts seem to be new people getting frustrated at their lack of knowledge and trying to reinvent something that already exists. I'm looking at this thinking, why didn't they just use locate and fzf?

  • source
  • this looks beautiful. find has always driven me a bit batty.

    https://github.com/alexpasmantier/television?tab=readme-ov-file

  • source
  • [–] 3 points 2 years ago

    Love reading about the author's struggle with find, it really resonates. I have the same terrible experience every time I try to use it.

  • source
  • [–] 3 points 2 years ago

    It literally looks like a clone of fzf or sk complete with prompt and file previews. The fact that ithe article doesn't event reference the prior art is deeply concerning.

  • source
  • [–] 2 points 2 years ago

    I'm with the others: fd default syntax is easier to remember.

    And for the interactive search I'm using skim. With it I cd to the dir I want and Alt t to trigger fuzzy finding. There are also bindings to search for dir or in the history. The neat part is that results are inserted as is in the command line, no need to xargs or copy them. It also make the history look like I always know where the files I want are when in reality they are just fuzzy-found

  • source
  • [–] 2 points 2 years ago

    Eh, tried it. Doesn't seem to support regex or even wildcard matching, which is... suboptimal. The preview window also often fails to show the content of the current file correctly.

  • source
  • [–] 2 points 2 years ago (4 children)

    I always just use

    find | grep -i <partial file name>
    
  • source
  • hideshow 4 child comments
  • [–] 2 points 2 years ago

    Why can’t I remember the find parameters?

    I don't know. Perhaps write a couple of aliases?

  • source
  • [–] 2 points 2 years ago

    Looks like I'm gonna give it a whirl

  • source