Hi Frank,<br><br><div class="gmail_quote">On Tue, Mar 26, 2013 at 3:36 PM, Frank Shearar <span dir="ltr"><<a href="mailto:frank.shearar@gmail.com" target="_blank">frank.shearar@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Thanks very much Chris, I'll give this a whirl.<br>
<br>
Indeed, my _primary_ goal is to run things headless, which requires<br>
decent error reporting to stdout/stderr.<br>
<br>
However, I do really like REPLs (I use Clojure's, Python's and Ruby's<br>
just about every day), and having such a thing for Smalltalk would<br>
make me very happy. It would aid my ambassadorship greatly as well.<br></blockquote><div><br></div><div>Have you taken a look at Camillo's work for Pharo? The curses integration is particularly nice with colour in output stack traces (e.g. red on Exception methods).</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
frank<br>
<br>
On 26 March 2013 21:40, Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>> wrote:<br>
> Forwarding to your personal email as I have a feeling squeak-dev is<br>
> going to bounce my message due to being a whopping 130K attachment.<br>
><br>
><br>
> ---------- Forwarded message ----------<br>
> From: Chris Muller <<a href="mailto:asqueaker@gmail.com">asqueaker@gmail.com</a>><br>
> Date: Tue, Mar 26, 2013 at 4:38 PM<br>
> Subject: Re: [squeak-dev] The Trunk: Graphics-tpr.205.mcz<br>
> To: The general-purpose Squeak developers list<br>
> <<a href="mailto:squeak-dev@lists.squeakfoundation.org">squeak-dev@lists.squeakfoundation.org</a>><br>
><br>
><br>
> Here is my little wrapper for handling running .st scripts from the<br>
> command-line and outputting Notifications and SyntaxErrors to stdOut<br>
> and Errors to stdErr. I use this every day, at one time I had wanted<br>
> to integrate this into the trunk.<br>
><br>
> I've never found interacting back-and-forth with an image via<br>
> command-line in the style of Camillo's tool useful. I don't know when<br>
> one would want to do that. However certainly I do need to kick off<br>
> Smalltalk jobs from the command-line, headless or not, by passing in<br>
> .st scripts and that sounds like what you're wanting to do with a<br>
> build server.<br>
><br>
> MaCommandLineProcessor in the attached package is 11 methods total --<br>
> it thinly wraps Squeaks existing capability so that some of the<br>
> "gotcha's" are taken care of -- for example like the fact that if you<br>
> try to print an Error's signalerContext's longStack, it's full of CR's<br>
> rather than the platform line-ending making it unreadable in the host<br>
> OS. MaCommandLineProcessor in the attached package fixes that.<br>
><br>
> Comments welcome -- maybe you'll see some tips at least..<br>
><br>
><br>
><br>
> On Tue, Mar 26, 2013 at 1:49 AM, Frank Shearar <<a href="mailto:frank.shearar@gmail.com">frank.shearar@gmail.com</a>> wrote:<br>
>> On 26 March 2013 00:27, tim Rowledge <<a href="mailto:tim@rowledge.org">tim@rowledge.org</a>> wrote:<br>
>>> Starting from a fresh image from the Jenkins server that claimed to be completely clean and up to date<br>
>><br>
>> That's going to be the best we have, for the moment. Mainly because<br>
>> * we never have a green build,<br>
>> * Squeak has very limited command line support<br>
>> ** you need to feed it a chunk-formatted startup script, or a script<br>
>> with no !s in it<br>
>> ** exceptions mean debuggers pop up, rather than dumping stack traces to stdout<br>
>><br>
>> But otherwise, if the resulting image is _not_ completely clean & up<br>
>> to date, it's my fault, and please yell at me. Preferably in the form<br>
>> of a nice bug report :)<br>
>><br>
>> frank<br>
>><br>
>>>, making the changes to get rid of the obsolete 'BitBlt current' idiom for everything visible, I have now committed about half-a-dozen packages that seem to be correct.<br>
>>><br>
>>> I also committed a VMMaker change to<br>
>>> a) move BitBltSImulation under SmartSyntaxPlugin<br>
>>> b) move the pixel-peeker primitive into BitBltSimulation<br>
>>> c) update the comment a bit to include some combination rules added about ten years ago<br>
>>><br>
>>> A VM built from this passes the BitBltTests in TestRunner and appears to run everything normally.<br>
<div class="im">>>><br>
>>> tim<br>
>>> --<br>
>>> tim Rowledge; <a href="mailto:tim@rowledge.org">tim@rowledge.org</a>; <a href="http://www.rowledge.org/tim" target="_blank">http://www.rowledge.org/tim</a><br>
</div>>>> Strange OpCodes: SD: Self Destruct<br>
>>><br>
>>><br>
>>><br>
>><br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div>