[squeak-dev] Running Squeak fro ma unix shell script file with #! squeak...

David T. Lewis lewis at mail.msen.com
Mon May 6 13:05:00 UTC 2019


On Mon, May 06, 2019 at 08:14:44AM -0400, David T. Lewis wrote:
> On Sun, May 05, 2019 at 11:03:34PM -0400, David T. Lewis wrote:
> > On Sun, May 05, 2019 at 05:32:19PM -0400, David T. Lewis wrote:
> > > On Sun, May 05, 2019 at 02:06:14PM -0700, tim Rowledge wrote:
> > > > 
> > > > 
> > > > > On 2019-05-05, at 1:51 PM, David T. Lewis <lewis at mail.msen.com> wrote:
> > > > > 
> > > > > On Sun, May 05, 2019 at 12:48:13PM -0700, tim Rowledge wrote:
> > > > >> 
> > > > >> 
> > > > >>> On 2019-05-05, at 7:38 AM, Fabio Niephaus <lists at fniephaus.com> wrote:
> > > > >>> 
> > > > >>> Otherwise, `#!/path/to/vm/squeak /path/to/my.image` should work, right?
> > > > >> 
> > > > >> That's what I thought but it doesn't appear to actually do that. I've been looking at https://en.wikipedia.org/wiki/Shebang_(Unix) to try to understand but so far nothing is doing quite what I anticipated.
> > > > >> Most annoyingly I can't get any sort of debugging output using the usual -x flag. 
> > > > >> 
> > > > > 
> > > > > One part of the current problem is that we have somehow broken the script loader:
> > > 
> > > And the next issue after that is the code loader, which probably used to be smart
> > > enough to skip over the shebang line in the hello.sq script, but apparently no
> > > longer does so.
> > 
> > Fixed in trunk now (System-dtl.1062).
> > 
> > Turn off deprecation warnings to work around the other issue, I don't know
> > the story on that one. But otherwise things should be back to normal.
> >
> 
> The deprecation warning is raised by URI class>>basicNew, called by String>>asURI.
> The deprecation was added recently in Network-tpr.231, but I don't know what
> the replacement class should be.
> 
> Presumably String>>asURI needs to be updated, and that should fix the remaining
> problem with shebang script loading.
>

Changing to use String>>asUrl instead of String>>asURI seems like the right thing
to do, but additional changes will be needed in ProjectLauncher>>startUpAfterLogin
to make it work.

Dave
 


More information about the Squeak-dev mailing list