[chuck-users] chuck shell...
Andrew C. Smith
acsmith at willamette.edu
Wed Sep 9 14:05:30 EDT 2009
Um, I didn't actually expect it to be quite that easy. I just copied
the 188.8.131.52 CVS v2 source into the miniAudicle directory and
recompiled, then ran the "write.ck" example and it worked. Now, let me
ask, why isn't there a version of the mini with 184.108.40.206 available for
download? Or, at least on the wiki or something. This is great, like
Christmas when something like this works.
On Wed, Sep 9, 2009 at 1:34 PM, Andrew C. Smith<acsmith at willamette.edu> wrote:
> Hey, so how can I upgrade my Mini to the CVS version, with all the
> file IO capabilities? Or, even 220.127.116.11? I successfully compiled the
> CVS command line version, but I've never compiled the Mini. I just
> found myself liking the pretty colored text.
> On Wed, Sep 9, 2009 at 1:24 PM, Kassen<signal.automatique at gmail.com> wrote:
>> Hey, Kurt.
>> I think the shell has been close to abandoned, which is a shame as
>> there were some really good ideas planned for it. Right now the shell
>> offers little over a plain commandline; you can enter code but if you
>> make a single typo (and who doesn't?) you need to start all over again
>> as there is no buffer for commands. There were plans for a way to
>> navigate the scope of running code from the shell (to update it) but
>> those never materialised. I'm still a bit sad about that as those
>> plans were amongst the most exciting plans for ChucK ever, IMHO.
>> I think the Mini mostly replaced it; it does all that the shell does
>> and more though of course it does need to be used with a Gui; that
>> might be a downside to some.
>> Personally I tried to use the shell for a while but I found it a bit
>> clumsy so I'm curious why and how you use it.
>> 2009/9/9 kurt <sobrilliant at gmail.com>:
>>> Hello all-
>>> First of all, I love ChucK shell!!!
>>> But I wondered if there are any plans for ChucK shell improvements in the
>>> works? It would be nice to have some normal shell type stuff...
>>> Tab-completion, command line history (it would be sweet to 'up-arrow', then
>>> 'enter key' to keep adding the same shred), the ability to change
>>> directories (or at least the ../../ syntax would be nice, cause, as it
>>> stands, one has to use absolute path names for files not in the working
>>> directory), and to move the cursor with the arrow keys to edit commands.
>>> Also it might be cool if when querying active shreds (the '^' command) it
>>> would be cool if the child shreds were indented a level from the parent
>>> shreds. It would be nice if you could add and remove shreds by name (eg.
>>> all shreds named "foo.ck" could be removed by some command like '-! foo", i
>>> dunno?). I feel kinda lame asking about this stuff, but I figured if some
>>> awesome ChucK dev out there was thinking about spiffying up the shell for
>>> the next ChucK release they might be stoked to know someone out there was
>>> exited about potential improvements.
>>> chuck-users mailing list
>>> chuck-users at lists.cs.princeton.edu
>> chuck-users mailing list
>> chuck-users at lists.cs.princeton.edu
More information about the chuck-users