On 3/2/2012 3:28 AM, Eliot Moss wrote:
.
Generally, getting " quotes around it will do the trick.
Over the years I have managed to make many of my scripts
safe for file and directory names that have spaces. It's
a pain, but generally possible ... Eliot Moss
Eliot:
Thanks. I am usually very
[sent to wrong email address, apologies]
On 3/2/2012 12:43 PM, Paul Allen Newell wrote:
On 3/1/2012 11:19 PM, Dave Korn wrote:
On 02/03/2012 07:06, Paul Allen Newell wrote:
I'll go and figure out some way to filter $(PWD) to be acceptable to
basename.
It just needs quotes around it to prev
On 3/2/2012 2:06 AM, Paul Allen Newell wrote:
On 3/1/2012 10:50 PM, Dave Korn wrote:
I'll go and figure out some way to filter $(PWD) to be acceptable to basename.
Generally, getting " quotes around it will do the trick.
Over the years I have managed to make many of my scripts
safe for file
On 02/03/2012 07:06, Paul Allen Newell wrote:
> I'll go and figure out some way to filter $(PWD) to be acceptable to
> basename.
It just needs quotes around it to prevent the space being taken as a
separator.
cheers,
DaveK
--
Problem reports: http://cygwin.com/problems.html
F
On 3/1/2012 10:50 PM, Dave Korn wrote:
I think it's because aliases are just simple text substitutions. So if you
have 'make' being transformed to 'settitle Making $(basename $PWD)&& make
"$@"' then you would get 'make>& make.out' becoming 'settitle Making
$(basename $PWD)&& make "$@">&
On 02/03/2012 06:25, Paul Allen Newell wrote:
> +++
> type make; which -a make
> make is aliased to `settitle Making $(basename $PWD) && make "$@"'
> /usr/bin/make
> /usr/bin/make
> +++
>
> I groaned when I saw this as it is obvious the $(PWD) is feeding
> basename and that's the "make" error. Th
On 3/1/2012 10:07 PM, Dave Korn wrote:
On 02/03/2012 02:52, Paul Allen Newell wrote:
[ weird problem symptoms ]
You probably have a script or shell alias getting in between you and the
real make. Please run "type make ; which -a make" in a bash shell and show us
the results.
cheers,
7 matches
Mail list logo
