On Thu, May 04, 2017 at 02:22:38PM +0200, Nicolas George wrote:
> For interactive use, the other other behaviour is obviously the best
> one:
>
> ~ $ ls *.c
> zsh: no matches found: *.c
> zsh: exit 1 ls --color=tty -FT0 *.c
>
> Notice how zsh is reporting the error, not ls?
Oh, bash calls th
Le quintidi 15 floréal, an CCXXV, Greg Wooledge a écrit :
> Bash has an option for this behavior (nullglob). It's off by default
> because it produces extremely surprising results in interactive use.
For interactive use, the other other behaviour is obviously the best
one:
~ $ ls *.c
zsh: no mat
On Thu, May 04, 2017 at 09:36:11AM +0200, Nicolas George wrote:
> Note that it is a severe misfeature of the shell to have a very
> different behaviour when a glob matches than when a glob does not match.
>
> I have seen make commands fail because they contained unquoted "[a]"
> arguments and some
On Thursday, May 04, 2017 01:45:30 AM Bob McGowan wrote:
> On 05/03/2017 07:44 PM, rhkra...@gmail.com wrote:
...
> >> On my (Wheezy) system, I tried that, i.e.:
> >>
> >>
> >> echo find /home/ -type d -name .*
> >>
> >> and
> >>
> >> echo find /home/ -type d -name '.*'
> >>
> >> and, in both
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, May 04, 2017 at 09:36:11AM +0200, Nicolas George wrote:
> Le quintidi 15 floréal, an CCXXV, to...@tuxteam.de a écrit :
> > Exactly. Try again in a directory with something in it, and you'll
> > appreciate the whole power/curse of the thing :-)
Le quintidi 15 floréal, an CCXXV, to...@tuxteam.de a écrit :
> Exactly. Try again in a directory with something in it, and you'll
> appreciate the whole power/curse of the thing :-)
>
> The shell takes a lot from the "ambient" (current directory, shell
> variables inherited through the dynamic pat
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 03, 2017 at 10:45:30PM -0700, Bob McGowan wrote:
[...]
> >>> before all that:
> >>> echo find /home/richard -type d -name .*
> >> That seems like a helpful trick, but I'm not sure what I should see.
> >>
> >> On my (Wheezy) system, I tr
On 05/03/2017 07:44 PM, rhkra...@gmail.com wrote:
> Hmm, maybe I don't need a response to this--I think if I read Greg Wooledge's
> post (next in the thread) and experiment (tomorrow or later ;-) with his
> script, I'll get the idea...
>
> On Wednesday, May 03, 2017 10:29:08 PM rhkra...@gmail.com
Hmm, maybe I don't need a response to this--I think if I read Greg Wooledge's
post (next in the thread) and experiment (tomorrow or later ;-) with his
script, I'll get the idea...
On Wednesday, May 03, 2017 10:29:08 PM rhkra...@gmail.com wrote:
> On Wednesday, May 03, 2017 04:22:57 PM to...@tuxt
On Wednesday, May 03, 2017 04:22:57 PM to...@tuxteam.de wrote:
> FWIW, a trick to see what's really going on is to prepend an echo
> before all that:
>
> echo find /home/richard -type d -name .*
That seems like a helpful trick, but I'm not sure what I should see.
On my (Wheezy) system, I tried
On Wednesday, May 03, 2017 01:34:02 PM Richard Owlett wrote:
> *GRIN*
> Been using that basic procedure since mid 1950's [when volume of single
> flip-flop could be measured in cubic inches ;]
Good! (I didn't start that with much rigor until the mid 60s.)
> I had spent more than an hour:
> 1.
On 4 May 2017 at 09:54, David wrote:
>
> You might also get helpful information by running:
> info find
> to read the full GNU documenation.
>
> If you don't like the user interface of the 'info' program, you can
> dump all its output into a text file by running:
> info -f find --subnodes >out
On 4 May 2017 at 01:13, wrote:
> On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
>> The man page for find confuses me.
>> Looking for explanatory material I found and tried to follow examples in
>> http://mywiki.wooledge.org/UsingFind#A-prune .
Richard,
Relevant examples are on tha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 03, 2017 at 04:38:15PM -0400, Greg Wooledge wrote:
> On Wed, May 03, 2017 at 10:22:57PM +0200, to...@tuxteam.de wrote:
> > FWIW, a trick to see what's really going on is to prepend an echo
> > before all that:
> >
> > echo find /home/ric
On Wed, May 03, 2017 at 10:22:57PM +0200, to...@tuxteam.de wrote:
> FWIW, a trick to see what's really going on is to prepend an echo
> before all that:
>
> echo find /home/richard -type d -name .*
>
> (for the example above). Of course you won't think of that if you
> are't suspecting shell ex
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Wed, May 03, 2017 at 11:44:31AM -0400, Greg Wooledge wrote:
> On Wed, May 03, 2017 at 11:13:46AM -0400, rhkra...@gmail.com wrote:
> > On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
> > >find /home/richard \( -type d -name .* -prune
On 05/03/2017 12:34 PM, Richard Owlett wrote:
On 05/03/2017 10:13 AM, rhkra...@gmail.com wrote:
On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
The man page for find confuses me.
Looking for explanatory material I found and tried to follow examples in
http://mywiki.wooledge.org/Usi
On 05/03/2017 10:13 AM, rhkra...@gmail.com wrote:
On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
The man page for find confuses me.
Looking for explanatory material I found and tried to follow examples in
http://mywiki.wooledge.org/UsingFind#A-prune .
I tried
find /home/richard
On Wed, May 03, 2017 at 12:23:26PM -0400, rhkra...@gmail.com wrote:
> On Wednesday, May 03, 2017 12:09:59 PM Greg Wooledge wrote:
> > Unfortunately, "remove random parts of the syntax and see what happens"
> > tends to be a poor approach, especially with find(1). There may be
> > some other kinds
On Wednesday, May 03, 2017 12:09:59 PM Greg Wooledge wrote:
> On Wed, May 03, 2017 at 12:01:21PM -0400, rhkra...@gmail.com wrote:
> > Oh, but in case it wasn't very clear, my intension wasn't so much a
> > specific recommendation of what might work, but instead, a
> > recommendation on a methodolog
On Wed, May 03, 2017 at 12:01:21PM -0400, rhkra...@gmail.com wrote:
> Oh, but in case it wasn't very clear, my intension wasn't so much a specific
> recommendation of what might work, but instead, a recommendation on a
> methodology to find the problem one's self.
Unfortunately, "remove random p
On Wednesday, May 03, 2017 11:44:31 AM Greg Wooledge wrote:
> On Wed, May 03, 2017 at 11:13:46AM -0400, rhkra...@gmail.com wrote:
> > On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
> > >find /home/richard \( -type d -name .* -prune \) -o -atime -42
> > >-print
> >
> > Maybe n
Richard Owlett writes:
> The man page for find confuses me.
> Looking for explanatory material I found and tried to follow examples
> in http://mywiki.wooledge.org/UsingFind#A-prune .
>
> I tried
> find /home/richard \( -type d -name .* -prune \) -o -atime -42 -print
> and
> find /home/richar
On Wed, May 03, 2017 at 11:13:46AM -0400, rhkra...@gmail.com wrote:
> On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
> >find /home/richard \( -type d -name .* -prune \) -o -atime -42 -print
> Maybe next I'd try:
>
> find /home/richard -type d -name .* (without the escaped parens
Hi,
Richard Owlett wrote:
> I tried
> find /home/richard \( -type d -name .* -prune \) -o -atime -42 -print
> and
> find /home/richard \( -type d -name .* -prune \) -atime -42 -print
> ...
> Each got an "find: paths must precede expression: .." error
You need to hide the .* word from the shel
On Wednesday, May 03, 2017 10:57:09 AM Richard Owlett wrote:
> The man page for find confuses me.
> Looking for explanatory material I found and tried to follow examples in
> http://mywiki.wooledge.org/UsingFind#A-prune .
>
> I tried
>find /home/richard \( -type d -name .* -prune \) -o -atime
The man page for find confuses me.
Looking for explanatory material I found and tried to follow examples in
http://mywiki.wooledge.org/UsingFind#A-prune .
I tried
find /home/richard \( -type d -name .* -prune \) -o -atime -42 -print
and
find /home/richard \( -type d -name .* -prune \) -atim
27 matches
Mail list logo
