On Sat, May 22, 2010 at 09:25:02PM -0700, Ben Tilly wrote:
> On Sat, May 22, 2010 at 9:21 PM, Greg London wrote:
> > I used '@' as my wildcard and then do a s/@/*/g at some point before using
> > it. It feels a bit klugey though. Is there a better way to do it?
>
> That is very kludgey. I would
Ben Tilly wrote:
> That is very kludgey. I would suggest just making people put single
> quotes around the wildcard. That will be less surprising for
> experienced people.
Oh, man, I don't know why I didn't think of that.
My only defense is I was frantically trying to finish
this at work, on Fri
On Sun, May 23, 2010 at 12:21 AM, Greg London wrote:
>
> First, I have a perl script that needs to pass in via command options a
> filename that might include wildcards. This filename will be used by the
> script at a later point, from a different directory, so I don't want Unix
> to do wildcard
> "GL" == Greg London writes:
GL> First, I have a perl script that needs to pass in via command
GL> options a filename that might include wildcards. This filename
GL> will be used by the script at a later point, from a different
GL> directory, so I don't want Unix to do wildcard repla
On Sat, May 22, 2010 at 9:21 PM, Greg London wrote:
> Two unrelated perl queries.
>
> First, I have a perl script that needs to pass in via command options a
> filename that might include wildcards. This filename will be used by the
> script at a later point, from a different directory, so I don't
Two unrelated perl queries.
First, I have a perl script that needs to pass in via command options a
filename that might include wildcards. This filename will be used by the
script at a later point, from a different directory, so I don't want Unix
to do wildcard replacement when I run the script. B
6 matches
Mail list logo
