zsh-users
 help / color / mirror / code / Atom feed
From: Yuya Amemiya <ghostrevery@gmail.com>
To: brent.briggs@gmail.com
Cc: zsh-users@zsh.org
Subject: Re: Glob problem
Date: Wed, 23 Oct 2013 23:29:56 +0900 (JST)	[thread overview]
Message-ID: <20131023.232956.18388131.ghostrevery@gmail.com> (raw)
In-Reply-To: <91F9ED9F-B198-403B-9FE1-FF40DE960C1C@gmail.com>

Hi,

> This did the job. I still have one question. I can't find any documentation for the "--" option. What does it do exactly?
"--" is not a option.
This separates options and normal arguments to give arguments starting with "-".

The more important point is ${^path}.
This turns on RC_EXPAND_PARAM option for evaluation of path.

${^path}/${~pattern} is substituted with /opt/local/bin/git*(N) /opt/local/sbin/git*(N) ...
and result of substitution is interpreted as pattern for filename generation.

regards,

From: Brent Briggs <brent.briggs@gmail.com>
Subject: Re: Glob problem
Date: Wed, 23 Oct 2013 08:27:22 -0400

> This did the job. I still have one question. I can't find any documentation for the "--" option. What does it do exactly?
> 
> 
> On Oct 22, 2013, at 4:11 PM, Yuya Amemiya <ghostrevery@gmail.com> wrote:
> 
>> Hi,
>> 
>>> print -l $path/$~pattern
>> 
>> Try this:
>>  print -l -- ${^path}/${~pattern}
>> 
>> regards
>> 
>> From: Brent Briggs <brent.briggs@gmail.com>
>> Subject: Re: Glob problem
>> Date: Tue, 22 Oct 2013 14:49:13 -0400
>> 
>>> Adding the (N) Glob Qualifier made a difference but is I'm still not quite there yet. 
>>> 
>>> pattern=git*(N)
>>> print -l $path/$~pattern
>>> 
>>> Output:
>>> ----------
>>> /opt/local/bin
>>> /opt/local/sbin
>>> /usr/bin
>>> /bin
>>> /usr/sbin
>>> /sbin
>>> /usr/local/bin
>>> /usr/local/MacGPG2/bin
>>> 
>>> This is my full path listing minus the final entry /Users/brent/bin. I know this is a bit of an incidental question but why is the final path entry missing from this output? 
>>> 
>>> Trying this gets me a little closer.
>>> 
>>> pattern=git*(N)
>>> for entry in $path      
>>> do
>>> 	print -l $entry/$~pattern
>>> done
>>> 
>>> Output:
>>> ----------
>>> /opt/local/bin/git
>>> /opt/local/bin/git-credential-osxkeychain
>>> /opt/local/bin/git-cvsserver
>>> /opt/local/bin/git-receive-pack
>>> /opt/local/bin/git-shell
>>> /opt/local/bin/git-upload-archive
>>> /opt/local/bin/git-upload-pack
>>> /opt/local/bin/gitk
>>> -- blank --
>>> /usr/bin/git
>>> /usr/bin/git-cvsserver
>>> /usr/bin/git-receive-pack
>>> /usr/bin/git-shell
>>> /usr/bin/git-upload-archive
>>> /usr/bin/git-upload-pack
>>> -- blank --
>>> -- blank --
>>> -- blank --
>>> -- blank --
>>> -- blank --
>>> 
>>> Blank lines are printed for the directories that contain no pattern matches. Any quick way to get rid of these?
>>> 
>>> On Oct 22, 2013, at 2:12 PM, Peter Miller <peter.d.miller@oracle.com> wrote:
>>> 
>>>> On 10/22/13 14:02, Brent Briggs wrote:
>>>>> Thanks for all the responses. The glob is now being generated properly. However, I am still having a problem getting my loop to run completely through.
>>>>> 
>>>>> pattern=git*
>>>>> for entry in $path
>>>>> do
>>>>>    print -l $entry/$~pattern
>>>>> done
>>>>> 
>>>>> Output:
>>>>> ----------
>>>>> /opt/local/bin/git
>>>>> /opt/local/bin/git-credential-osxkeychain
>>>>> /opt/local/bin/git-cvsserver
>>>>> /opt/local/bin/git-receive-pack
>>>>> /opt/local/bin/git-shell
>>>>> /opt/local/bin/git-upload-archive
>>>>> /opt/local/bin/git-upload-pack
>>>>> /opt/local/bin/gitk
>>>>> zsh: no matches found: /opt/local/sbin/git*
>>>>> 
>>>>> /opt/local/sbin/ being the second entry in my path.
>>>>> 
>>>>> 
>>>>> Also tried:
>>>>> 
>>>>> print -l $path/$~pattern
>>>> 
>>>> try
>>>> 
>>>> pattern=git*(N)
>>>> print -l $path/$~pattern
>>>> 
>>>> that will tell zsh to ignore globs that don't have any matches.
>>>> 
>>>>> 
>>>>> Output:
>>>>> ----------
>>>>> zsh: no matches found: /Users/brent/bin/git*
>>>>> 
>>>>> /Users/brent/bin/ being the last entry in my path.
>>>>> 
>>>>> Looks like I need to use a conditional to test if any pattern matches exist, per directory, before trying to print them. I wasn't able to find a solution in the manual that facilitates testing for the existence of pattern matches. I would like to solve this problem using only globbing if possible. I am probably missing something simple.
>>>>> 
>>>>> 
>>>>> 
>>>>> On Oct 22, 2013, at 1:05 PM, Philippe Troin<phil@fifi.org>  wrote:
>>>>> 
>>>>>> On Tue, 2013-10-22 at 12:45 -0400, Brent Briggs wrote:
>>>>>> 
>>>>>>> I am simply trying to list all matches for a specified pattern in an
>>>>>>> array of directory paths, the $path array for example. Here is my
>>>>>>> attempt. Where am I going wrong?
>>>>>> Globs are not ran after variable substitution by default.
>>>>>> To run filename generation (aka globs) after variable substitution, use
>>>>>> $~var.
>>>>>> 
>>>>>> Your example:
>>>>>> 
>>>>>>> pattern=git*
>>>>>>> for entry in $path
>>>>>>> do
>>>>>>>   # Print all files in the path that match the pattern.
>>>>>>>   print $entry/$pattern
>>>>>>> done
>>>>>> Can be rewritten as:
>>>>>> 
>>>>>>       pattern=git*
>>>>>>       for entry in $path
>>>>>>       do
>>>>>>           # Print all files in the path that match the pattern.
>>>>>>           print $entry/$~pattern
>>>>>>       done
>>>>>> 
>>>>>> It can be simplified further as:
>>>>>> 
>>>>>>       pattern=git*
>>>>>>       print $path/$~pattern
>>>>>> 
>>>>>> Phil.
>>>>>> 
>>>> 
>>> 
> 


  parent reply	other threads:[~2013-10-23 14:30 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-22 16:45 Brent Briggs
2013-10-22 16:58 ` Jérémie Roquet
2013-10-22 16:59 ` Peter Stephenson
2013-10-22 17:05 ` Philippe Troin
2013-10-22 18:02   ` Brent Briggs
2013-10-22 18:12     ` Peter Miller
2013-10-22 18:49       ` Brent Briggs
2013-10-22 19:30         ` Peter Miller
2013-10-22 20:11         ` Yuya Amemiya
2013-10-23 12:27           ` Brent Briggs
2013-10-23 12:37             ` Jérémie Roquet
2013-10-23 13:47             ` Peter Stephenson
2013-10-23 14:29             ` Yuya Amemiya [this message]
2013-10-22 17:11 ` Matt Garriott

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20131023.232956.18388131.ghostrevery@gmail.com \
    --to=ghostrevery@gmail.com \
    --cc=brent.briggs@gmail.com \
    --cc=zsh-users@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).