Re: An appropriate directory search tool?

On Tue 30 Oct 2018 at 09:52:52 (-0500), David Wright wrote: > 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 g

Re: An appropriate directory search tool?

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. Yo

Re: An appropriate directory search tool?

On Mon, Oct 22, 2018 at 10:24:35AM -0500, David Wright wrote: > > > On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > > > > I wish a list of files with a specific extension in a directory which > > > > contain keywordA but not keywordB. Recursing down the directory tree > > > > was th

Re: An appropriate directory search tool?

On Mon 22 Oct 2018 at 09:09:12 (-0400), Greg Wooledge wrote: > On Sun, Oct 21, 2018 at 08:48:28AM -0500, David Wright wrote: > > On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > > > I wish a list of files with a specific extension in a directory which > > > contain keywordA but not k

Re: An appropriate directory search tool?

On Mon 22 Oct 2018 at 10:12:57 (+0900), John Crawley wrote: > On 21/10/2018 22.48, David Wright wrote: > > On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > > > On 10/20/2018 08:16 PM, John Crawley wrote: > > > > On 20/10/2018 19.28, Richard Owlett wrote: > > > > > ...I would have exp

Re: An appropriate directory search tool?

On Sun, Oct 21, 2018 at 08:48:28AM -0500, David Wright wrote: > On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > > I wish a list of files with a specific extension in a directory which > > contain keywordA but not keywordB. Recursing down the directory tree > > was the primary object

Re: An appropriate directory search tool?

On 21/10/2018 22.48, David Wright wrote: On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: On 10/20/2018 08:16 PM, John Crawley wrote: On 20/10/2018 19.28, Richard Owlett wrote: ...I would have expected to use an explicit pipe command between 'find' and 'grep'. In fact, depending

Re: An appropriate directory search tool?

On Sunday, October 21, 2018 02:52:15 PM David Wright wrote: > On Sun 21 Oct 2018 at 13:11:16 (-0400), rhkra...@gmail.com wrote: > > > > rhk@s19:/rhk/ked1$ grep test - >| /tmp/a ; echo "and the output is" ; cat > > /tmp/a one > > two > > test > > one > > two > > test > > ^C > > rhk@s19:/rhk/ked1$ l

Re: An appropriate directory search tool?

On Sun 21 Oct 2018 at 13:11:16 (-0400), rhkra...@gmail.com wrote: > On Sunday, October 21, 2018 12:35:04 PM David Wright wrote: > > On Sun 21 Oct 2018 at 11:45:49 (-0400), rhkra...@gmail.com wrote: > > > Any further clarification / clues would be appreciated. > > > > Use neither option to see the

Re: An appropriate directory search tool?

On Sunday, October 21, 2018 12:35:04 PM David Wright wrote: > On Sun 21 Oct 2018 at 11:45:49 (-0400), rhkra...@gmail.com wrote: > > Any further clarification / clues would be appreciated. > > Use neither option to see the difference with using either -l or -L. > So that standard output doesn't clu

Re: An appropriate directory search tool?

On Sun 21 Oct 2018 at 11:45:49 (-0400), rhkra...@gmail.com wrote: > On Sunday, October 21, 2018 11:21:35 AM David Wright wrote: > > On Sun 21 Oct 2018 at 10:33:41 (-0400), rhkra...@gmail.com wrote: > > > On Sunday, October 21, 2018 09:48:28 AM David Wright wrote: > > > > $ grep -L keywordB $(grep -

Re: An appropriate directory search tool?

On 2018-10-21, rhkra...@gmail.com wrote: > > Thanks for the reply, and I like that ability to use standard input! > > I tried the following, and the output from -L and -l seems almost the same, > except for that extra line that says "(standard input)" when I use the -l > option. For -l, I gue

Re: An appropriate directory search tool?

On Sunday, October 21, 2018 11:21:35 AM David Wright wrote: > On Sun 21 Oct 2018 at 10:33:41 (-0400), rhkra...@gmail.com wrote: > > On Sunday, October 21, 2018 09:48:28 AM David Wright wrote: > > > $ grep -L keywordB $(grep -l keywordA a-directory/*extension) > > > > I am not the OP, and I haven't

Re: An appropriate directory search tool?

On Sun 21 Oct 2018 at 10:33:41 (-0400), rhkra...@gmail.com wrote: > On Sunday, October 21, 2018 09:48:28 AM David Wright wrote: > > On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > > > I wish a list of files with a specific extension in a directory which > > > contain keywordA but no

Re: An appropriate directory search tool?

On Sunday, October 21, 2018 09:48:28 AM David Wright wrote: > On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > > I wish a list of files with a specific extension in a directory which > > contain keywordA but not keywordB. Recursing down the directory tree > > was the primary objectio

Re: An appropriate directory search tool?

On Sun 21 Oct 2018 at 05:25:05 (-0500), Richard Owlett wrote: > On 10/20/2018 08:16 PM, John Crawley wrote: > > On 20/10/2018 19.28, Richard Owlett wrote: > > > ...I would have expected to use an explicit pipe command > > > between 'find' and 'grep'. > > > > In fact, depending on the exact conditi

Re: An appropriate directory search tool?

On 10/20/2018 08:16 PM, John Crawley wrote: On 20/10/2018 19.28, Richard Owlett wrote: ...I would have expected to use an explicit pipe command between 'find' and 'grep'. In fact, depending on the exact conditions of your search, you might not need to use find at all. 'grep -r' will do a recu

Re: An appropriate directory search tool?

On 10/20/2018 04:57 PM, Håkon Alstadheim wrote: Den 20. okt. 2018 21:05, skrev Brian: On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote: On 10/20/2018 06:37 AM, Joe wrote: On Sat, 20 Oct 2018 05:28:52 -0500 Richard Owlett wrote: On 10/20/2018 04:44 AM, to...@tuxteam.de wrote: O

Re: An appropriate directory search tool?

On 2018-10-20, Richard Owlett wrote: > > But they did. > That's why I wrote 'My take away from answers so far is "A script will > be required." ' > Perhaps we have different ideas of the definition of "script". > I saw the examples which worked as scripts (even if written as one > liners). If I

Re: An appropriate directory search tool?

On Sun, Oct 21, 2018 at 07:51:55PM +1100, Andrew McGlashan wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, > > On 21/10/18 06:05, Brian wrote: > > On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote: > >> Had never heard of 'zenity'. I browsed the text of the page. To >

Re: An appropriate directory search tool?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, On 21/10/18 06:05, Brian wrote: > On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote: >> Had never heard of 'zenity'. I browsed the text of the page. To >> read it as intended I'll have to use an alternate profile -- it >> expects "featu

Re: An appropriate directory search tool?

On 2018-10-21 02:16, John Crawley wrote: On 20/10/2018 19.28, Richard Owlett wrote: ...I would have expected to use an explicit pipe command between 'find' and 'grep'. In fact, depending on the exact conditions of your search, you might not need to use find at all. 'grep -r' will do a recursiv

Re: An appropriate directory search tool?

On 20/10/2018 19.28, Richard Owlett wrote: ...I would have expected to use an explicit pipe command between 'find' and 'grep'. In fact, depending on the exact conditions of your search, you might not need to use find at all. 'grep -r' will do a recursive search, starting at whatever directory

Re: An appropriate directory search tool?

Den 20. okt. 2018 21:05, skrev Brian: > On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote: > >> On 10/20/2018 06:37 AM, Joe wrote: >>> On Sat, 20 Oct 2018 05:28:52 -0500 >>> Richard Owlett wrote: >>> On 10/20/2018 04:44 AM, to...@tuxteam.de wrote: > On Sat, Oct 20, 2018 at 04:

Re: An appropriate directory search tool?

On Sat 20 Oct 2018 at 07:19:50 -0500, Richard Owlett wrote: > On 10/20/2018 06:37 AM, Joe wrote: > > On Sat, 20 Oct 2018 05:28:52 -0500 > > Richard Owlett wrote: > > > > > On 10/20/2018 04:44 AM, to...@tuxteam.de wrote: > > > > On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: > >

Re: An appropriate directory search tool?

On Saturday, October 20, 2018 08:35:51 AM Richard Owlett wrote: > I don't think "find" itself is the problem. > Debian seems to do some 'black magic' to conflate "standard output" and > "standard input". Otherwise a pipe command would be required between > "find" and "grep". I didn't go back all t

Re: An appropriate directory search tool?

On Friday, October 19, 2018 11:29:13 AM Greg Wooledge wrote: > There's also . I'm not the OP, but I wanted to say that I find the pages on your wiki (at least the ones I've looked at) to be helpful and well-written.

Re: An appropriate directory search tool?

Richard Owlett wrote: > On 10/20/2018 05:23 AM, Étienne Mollier wrote: >> [snip] >>> My take away from answers so far is "A script will be required." >> >> Not necessarily, the trouble is: "find" is so vast, you can >> spend hours in the manual to search for adequate option for >> your specific ne

Re: An appropriate directory search tool?

On 10/20/2018 05:23 AM, Étienne Mollier wrote: [snip] My take away from answers so far is "A script will be required." Not necessarily, the trouble is: "find" is so vast, you can spend hours in the manual to search for adequate option for your specific need, and end up writing a script, instea

Re: An appropriate directory search tool?

On 10/20/2018 06:24 AM, Joe wrote: On Sat, 20 Oct 2018 11:44:37 +0200 wrote: On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: I think my original post needs a rewrite ;/ I'm looking for a directory search tool with specific capabilities which would fit comfortably with my work

Re: An appropriate directory search tool?

On 10/20/2018 06:37 AM, Joe wrote: On Sat, 20 Oct 2018 05:28:52 -0500 Richard Owlett wrote: On 10/20/2018 04:44 AM, to...@tuxteam.de wrote: On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: I think my original post needs a rewrite ;/ I'm looking for a directory search tool wit

Re: An appropriate directory search tool?

On Sat, Oct 20, 2018 at 05:28:52AM -0500, Richard Owlett wrote: > > But they did. > That's why I wrote 'My take away from answers so far is "A script will be > required." ' > Perhaps we have different ideas of the definition of "script". > I saw the examples which worked as scripts (even if writte

Re: An appropriate directory search tool?

On Sat, 20 Oct 2018 05:28:52 -0500 Richard Owlett wrote: > On 10/20/2018 04:44 AM, to...@tuxteam.de wrote: > > On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: > >> I think my original post needs a rewrite ;/ > >> > >> I'm looking for a directory search tool with specific capabil

Re: An appropriate directory search tool?

On Sat, 20 Oct 2018 11:44:37 +0200 wrote: > On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: > > I think my original post needs a rewrite ;/ > > > > I'm looking for a directory search tool with specific capabilities > > which would fit comfortably with my work environment. > >

Re: An appropriate directory search tool?

On 10/20/2018 04:44 AM, to...@tuxteam.de wrote: On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: I think my original post needs a rewrite ;/ I'm looking for a directory search tool with specific capabilities which would fit comfortably with my work environment. [...] I suspec

Re: An appropriate directory search tool?

Good Day, On 10/20/18 11:32 AM, Richard Owlett wrote: > I think my original post needs a rewrite ;/ Well, let's stick to the text then... > I'm looking for a directory search tool with specific capabilities which > would fit comfortably with my work environment. > > The "MATE Search Tool" come

Re: An appropriate directory search tool?

On Sat, Oct 20, 2018 at 04:32:43AM -0500, Richard Owlett wrote: > I think my original post needs a rewrite ;/ > > I'm looking for a directory search tool with specific capabilities > which would fit comfortably with my work environment. [...] > I suspect that what I want would most likely be a c

Re: An appropriate directory search tool?

I think my original post needs a rewrite ;/ I'm looking for a directory search tool with specific capabilities which would fit comfortably with my work environment. The "MATE Search Tool" comes close. It can: Select a starting directory. Search for a specific extension. Search for a keyw

Re: An appropriate directory search tool?

Richard Owlett wrote: ... > I suspect what I want would most likely be what I'm looking for. > "ls" can search by extension and stay in specified directory. > It cannot include/exclude keywords. > > My immediate problem involves only a couple dozen files so manual search > is feasible. > > Suggest

Re: An appropriate directory search tool?

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. > find . -type f | while re

Re: An appropriate directory search tool?

On Fri 19 Oct 2018 at 10:00:25 (-0500), Richard Owlett wrote: > The "MATE Search Tool" comes close. > > It can: > Select a starting directory. > Search for a specific extension. > Search for a keyword in file content. > > It cannot: >Search ONLY the specified directory. >Return file

Re: An appropriate directory search tool?

On Fri, Oct 19, 2018 at 11:29:13AM -0400, Greg Wooledge wrote: > On Fri, Oct 19, 2018 at 05:21:30PM +0200, to...@tuxteam.de wrote: > > This would be 'find' (ok, with some little help from 'grep'). Hands down. > > > > The man page can be a bit... intimidating [...] > There's also

Re: An appropriate directory search tool?

On Fri, Oct 19, 2018 at 05:21:30PM +0200, to...@tuxteam.de wrote: > This would be 'find' (ok, with some little help from 'grep'). Hands down. > > The man page can be a bit... intimidating, so I'd suggest to begin with > little examples and return to the man page from time to time until you > got t

Re: An appropriate directory search tool?

On Fri, Oct 19, 2018 at 10:00:25AM -0500, Richard Owlett wrote: > The "MATE Search Tool" comes close. > > It can: > Select a starting directory. > Search for a specific extension. > Search for a keyword in file content. > > It cannot: >Search ONLY the specified directory. >Return fi

Re: An appropriate directory search tool?

On Fri, Oct 19, 2018 at 11:12:30AM -0400, Roberto C. Sánchez wrote: > On Fri, Oct 19, 2018 at 10:00:25AM -0500, Richard Owlett wrote: > > The "MATE Search Tool" comes close. > > > > It can: > > Select a starting directory. > > Search for a specific extension. > > Search for a keyword in file

Re: An appropriate directory search tool?

On Fri, Oct 19, 2018 at 10:00:25AM -0500, Richard Owlett wrote: > The "MATE Search Tool" comes close. > > It can: > Select a starting directory. > Search for a specific extension. > Search for a keyword in file content. > > It cannot: >Search ONLY the specified directory. >Return fi

Re: An appropriate directory search tool?

Hello, On Fri, Oct 19, 2018 at 10:00:25AM -0500, Richard Owlett wrote: > The "MATE Search Tool" comes close. > > It can: > Select a starting directory. > Search for a specific extension. > Search for a keyword in file content. > > It cannot: >Search ONLY the specified directory. >R

An appropriate directory search tool?

The "MATE Search Tool" comes close. It can: Select a starting directory. Search for a specific extension. Search for a keyword in file content. It cannot: Search ONLY the specified directory. Return files that DO NOT contain a keyword. I suspect what I want would most likely be what