This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

RE: basename(1) defect

Thanks.  The echo works. I haven't verified whether the latest basename(1)
behaves in the same way because I've run across a bigger problem.

Has anyone seem severe performance degradation running Cygwin on
WinME systems?  I've seen my system just get slower and slower over
the past several months. Cygwin ops that took a few seconds to run
now are running into the minutes.  Are there tools I can run to see what's
taking so long?  I've looked at the WinME side and I don't see anything
obviously wrong (SYSMON says resources okay, no viruses, defragged etc).
Any thoughts?  Help!


From: "Buchbinder, Barry (NIH/NIAID)" <>
To: <>
CC: "Stan Tsu" <>
Subject: RE: basename(1) defect
Date: Fri, 25 Nov 2005 08:33:50 -0500 wrote:
>>> This is a bug with basename 5.3.0 found in the latest Cygwin
> Not a bug.
>> 1.5.15 was three releases ago, it's most certainly not the latest.
>> But that's not really relevant to your question, I don't think.
>>> $ basename NA A
>>> N
>>> $ basename N/A A
>>> A                           <====== should return 'N/'
> POSIX requires that basename return everything beyond the final slash
> onwards, minus a partial suffix. The output you got is REQUIRED by
> basename (beyond the final suffix is "A", and "A" is a complete match
> rather than a partial suffix of "A", so the result must be "A"), and
> any other behavior from an older version of basename would be the
> bug, not the current behavior of either basename-5.3.0 or
> basename-5.93.
>>> Even with quoting:
>>> $ basename 'NA' A
>>> N
>>> $ basename 'N/A' A
>>> A                           <====== should return 'N/'
> Quoting makes no difference - the shell strips quotes before passing
> the arguments to /bin/basename.
>> If you just want to remove a trailing string I suggest you just use
>> bash's built in parameter expansion:
>> $ FCF="N/A"; Z=${FCF:(-1)}; echo ${FCF%$Z}
> This could also be done by /bin/expr (if you like coreutils), or even
> with awk, sed, or perl.  But Brian is correct, shell parameter
> expansion is the most efficient way to do string parsing, as it does
> not spawn any external processes.
> --
> Eric Blake
> volunteer cygwin bash/coreutils maintainer

Maybe you really want dirname.

/c> dirname N/A
/c> echo $(dirname N/A)/

Express yourself instantly with MSN Messenger! Download today - it's FREE!

-- Unsubscribe info: Problem reports: Documentation: FAQ:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]