Groups > linux.debian.user > #201885

Re: An appropriate directory search tool?

From	David Wright <deblis@lionunicorn.co.uk>
Newsgroups	linux.debian.user
Subject	Re: An appropriate directory search tool?
Date	2018-10-30 16:00 +0100
Message-ID	<wODES-8pe-5@gated-at.bofh.it> (permalink)
References	<wKEzv-4gD-5@gated-at.bofh.it> <wKFce-4tV-11@gated-at.bofh.it> <wKFvz-4Ph-1@gated-at.bofh.it>
Organization	linux.* mail to news gateway

Show all headers | View raw

On Fri 19 Oct 2018 at 12:03:42 (-0400), Greg Wooledge wrote:
> On Fri, Oct 19, 2018 at 10:48:42AM -0500, David Wright wrote:
> > find . -type f -exec chmod a-wx {} \;
> 
> For this one, you probably want to replace \; with + to get the efficiency
> boost, which would be pretty significant here.  You probably wrote this
> one a long time ago.

You're dead right. It could even have been copied straight from Unix
Power Tools 1st ed. And, of course, with the other example
find . -type f -exec file {} \; | less
it can make a huge difference to the number of "find: ‘file’
terminated by signal 13" messages if you lose interest and quit
out of less.

> > find . -type f | while read file ; do bash-function "$file"; done # avoid using exec
> 
> This one has a few minor bugs.  It will fail on filenames that contain
> newlines, or backslashes, or trailing whitespace, or leading whitespace.
> It can be corrected, although sadly the corrected version is a bit uglier.
> 
> find . -type f -print0 | while IFS= read -rd '' file; do bash-function "$file"; done

Updated. I'm more careful in writing my bash functions than this
commandline¹ stuff where the filename population tends to be
more restricted (ie I generated them).

> > find . -type f -name \*ly -printf '%TY-%Tm-%Td %TT %f\n' | cut --complement -b 20-30 | sort
> 
> This one looks like a variant of my "rlart" function:
> 
> rlart() {
>   find "${1:-.}" -type f -printf '%T@,%TY-%Tm-%Td,%TT,%p\0' |
>   sort -zn |
>   while IFS=, read -rd '' _ day time path; do
>     printf '%s %s %s\n' "$day" "${time%.*}" "$path"
>   done
> }
> 
> I give a detailed explanation of an earlier iteration of that one on
> <https://mywiki.wooledge.org/BashProgramming/03> for those who are
> interested in that sort of thing.  The explicit comma delimiters were
> added more recently, to avoid losing trailing whitespace.

Again, as you can see from -name, they're intended for particular sets
of files. Your considered version is better, so updated. However, I've
added back name so that just a set of source files are considered
(-name \*py might be a more obvious example for others) and I throw
away the leading directories.

Thanks once again for preening my bash constructs; much appreciated.

¹ I'm probably unusual in having a readonly .bash_history which
contains a handcrafted set of command paradigms. That's why some of
my commandlines might seem inordinately long, like hundreds of chars.

Cheers,
David.

Thread

An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-19 17:10 +0200
  Re: An appropriate directory search tool? Roberto C. Sánchez <roberto@debian.org> - 2018-10-19 17:20 +0200
  Re: An appropriate directory search tool? Roberto C. Sánchez <roberto@debian.org> - 2018-10-19 17:20 +0200
  Re: An appropriate directory search tool? <tomas@tuxteam.de> - 2018-10-19 17:30 +0200
    Re: An appropriate directory search tool? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-19 17:40 +0200
      Re: An appropriate directory search tool? <tomas@tuxteam.de> - 2018-10-19 17:50 +0200
      Re: An appropriate directory search tool? rhkramer@gmail.com - 2018-10-20 15:30 +0200
  Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-19 17:50 +0200
    Re: An appropriate directory search tool? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-19 18:10 +0200
      Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-30 16:00 +0100
        Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-12-01 18:20 +0100
  Re: An appropriate directory search tool? songbird <songbird@anthive.com> - 2018-10-20 00:40 +0200
  Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-20 11:40 +0200
    Re: An appropriate directory search tool? <tomas@tuxteam.de> - 2018-10-20 11:50 +0200
      Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-20 12:30 +0200
        Re: An appropriate directory search tool? Joe <joe@jretrading.com> - 2018-10-20 13:40 +0200
          Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-20 14:30 +0200
            Re: An appropriate directory search tool? Brian <ad44@cityscape.co.uk> - 2018-10-20 21:10 +0200
              Re: An appropriate directory search tool? Håkon Alstadheim <hakon@alstadheim.priv.no> - 2018-10-21 00:00 +0200
                Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-21 12:10 +0200
              Re: An appropriate directory search tool? Andrew McGlashan <andrew.mcglashan@affinityvision.com.au> - 2018-10-21 11:00 +0200
                Re: An appropriate directory search tool? <tomas@tuxteam.de> - 2018-10-21 11:20 +0200
        Re: An appropriate directory search tool? Roberto C. Sánchez <roberto@debian.org> - 2018-10-20 14:10 +0200
        Re: An appropriate directory search tool? John Crawley <john@bunsenlabs.org> - 2018-10-21 03:20 +0200
          Re: An appropriate directory search tool? mick crane <mick.crane@gmail.com> - 2018-10-21 07:30 +0200
          Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-21 12:30 +0200
            Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-21 15:50 +0200
              Re: An appropriate directory search tool? rhkramer@gmail.com - 2018-10-21 16:40 +0200
                Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-21 17:30 +0200
                Re: An appropriate directory search tool? rhkramer@gmail.com - 2018-10-21 17:50 +0200
                Re: An appropriate directory search tool? Curt <curty@free.fr> - 2018-10-21 18:40 +0200
                Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-21 18:40 +0200
                Re: An appropriate directory search tool? rhkramer@gmail.com - 2018-10-21 19:20 +0200
                Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-21 21:00 +0200
                Re: An appropriate directory search tool? rhkramer@gmail.com - 2018-10-21 23:50 +0200
              Re: An appropriate directory search tool? John Crawley <john@bunsenlabs.org> - 2018-10-22 03:20 +0200
                Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-22 17:30 +0200
              Re: An appropriate directory search tool? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-22 15:20 +0200
                Re: An appropriate directory search tool? David Wright <deblis@lionunicorn.co.uk> - 2018-10-22 17:30 +0200
                Re: An appropriate directory search tool? Greg Wooledge <wooledg@eeg.ccf.org> - 2018-10-22 17:50 +0200
        Re: An appropriate directory search tool? Curt <curty@free.fr> - 2018-10-21 12:00 +0200
      Re: An appropriate directory search tool? Joe <joe@jretrading.com> - 2018-10-20 13:30 +0200
        Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-20 14:30 +0200
    Re: An appropriate directory search tool? Étienne Mollier <etienne.mollier@mailoo.org> - 2018-10-20 12:30 +0200
      Re: An appropriate directory search tool? Richard Owlett <rowlett@cloud85.net> - 2018-10-20 14:40 +0200
        Re: An appropriate directory search tool? Dan Purgert <dan@djph.net> - 2018-10-20 15:20 +0200
        Re: An appropriate directory search tool? rhkramer@gmail.com - 2018-10-20 15:30 +0200

csiph-web