On Tue, 06 Nov 2007 17:20:14 +0100 "Julian H. Stacey" <[EMAIL PROTECTED]> wrote:
> It seems to me that all except csh (including bourne shell !) are
> broken !! Amazing ! None of them cope properly actually following
> symbolic links, they all make false premise the /some_path/.. ==
> /some_path !
On Tue, Nov 06, 2007 at 05:20:14PM +0100, Julian H. Stacey wrote:
> It seems to me that all except csh (including bourne shell !) are
> broken !! Amazing ! None of them cope properly actually following
> symbolic links, they all make false premise the /some_path/.. ==
> /some_path !
This may be a
> broken !! Amazing ! None of them cope properly actually following
> symbolic links, they all make false premise the /some_path/.. ==
> /some_path !
Sorry, typo, should have been:
they all make false premise that /some_path/something/.. == /some_path
--
Julian Stacey. Munich Computer Consultan
Hi Harti cc Hackers,
Thanks for answer.
> Are you sure that this is not a problem with /bin/sh?
Good question ! I think you'r right. I tested several shells with
[ Effectively: ln -s /usra/jhs/xtra/pics /usra/home/jhs/pics ] +
source `which unsetenv.csh`
[ sh, bash, csh,
On Mon, 5 Nov 2007, Julian Stacey wrote:
JS>I found some unexpected behaviour within make on 6.2-RELEASE,
JS>Not sure if it's a bug, or proper behaviour. Comment please ?
JS>
JS>Make seems to be being too clever, evaluating where it
JS>think the CWD (current working directory) is, whereas I think
I found some unexpected behaviour within make on 6.2-RELEASE,
Not sure if it's a bug, or proper behaviour. Comment please ?
Make seems to be being too clever, evaluating where it
think the CWD (current working directory) is, whereas I think
it should better let the external per line shell discover
6 matches
Mail list logo
