You wrote : > I just checked the code. It changes the working directory if you use type > in the path to mprime. Thus, "/bin/mprime -d" changes the working directory > to /bin and "mprime -d" leaves the working directory unchanged. I'll > leave this "feature" as is since people are relying on the current behavior
So we get both behaviour : when I have "/usr/primenet/prime3/mprime -B", the ini files are taken in the prime3 directory because mprime changes the path. when mprime is in the path, doing "for i in /usr/primenet/prime?; do (cd $i; mprime -B ); done", the ini files are taken in the prime? directory because mprime desn't change the path. ... -Jacques Charles On 7/5/07, Yves Bellefeuille <[EMAIL PROTECTED]> wrote: > > On Wednesday 04 July 2007, George Woltman wrote: > > > Then there is a bug in the Linux version. Hmmm, should I go fix it? > > Whatever your decision. I think that the documentation should reflect > the actual behaviour. > > Yves Bellefeuille > _______________________________________________ > Prime mailing list > [email protected] > http://hogranch.com/mailman/listinfo/prime > _______________________________________________ Prime mailing list [email protected] http://hogranch.com/mailman/listinfo/prime
