Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • What is the difference between expression (only one allowed?), cmd (dito?), options and args? Commented May 20, 2011 at 15:35
  • @user unknown -- the find command implements it's own expression syntax. The expression, when given, is the last argument on the command line. When absent, expression resolves to -print. Commented May 20, 2011 at 16:03
  • Ah - now I see, [cmd] isn't following [expression], but it's a description of the line before. Commented May 21, 2011 at 3:04
  • 7
    OP asserts that find "expects parameters in a painfully different way from most other utils". You state that OP is "confusing expression primaries with options". Do most other utils even have a concept of "expression primaries"? If not, doesn't that demonstrate OP's point? And that's really not the strangest part of using find. What other CLI involves {} (which of course must be escaped somehow)? Commented Aug 24, 2017 at 16:39
  • I hope someone makes a modern tool, like the way mc makes ls seem outdated, and ncdu makes du seem outdated, and zsh / fish makes bash seem outdated. I want an nclocate . which makes locate operate on a path with autocomplete in realtime, like google does for websites, or Ctrl-F does in nautilus GUI Commented Sep 29, 2017 at 17:50