Yes - my mistake (there was a bug in my code) - the defaultfolder does indeed change the effective place the shell command is called from.
2011/1/16 Björnke von Gierke <[email protected]> > answer folder "" > set the defaultfolder to it > put shell(ls) > > The result changes depending on what folder i specify. so it works fine for > me. Therefore I assume a scripting error on your part :P > > On 16 Jan 2011, at 17:06, David Bovill wrote: > > > I'm wandering if there is any relationship between "the defaultfolder" > and > > where the "shell" function effectively operates from? I thought there was > > but it seems not... to get the same result as I would get from the > command > > line I have to: > > > > shell_BashParamEscape pExecuteWhere > > > > *put* "cd" && pExecuteWhere && "&&" & space before someShell > > > > *put* someShell > > > > *put* shell (someShell) into shellResult > > > > > > > > /* > > > > -- this does not seem to work > > > > put the defaultfolder into oFolder > > > > set the defaultfolder to pExecuteWhere > > > > put shell (someShell) into shellResult > > > > set the defaultfolder to oFolder > > > > */ > > > > > > > > Is there a more elegant way? > > _______________________________________________ > > use-livecode mailing list > > [email protected] > > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > > http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > [email protected] > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
