Jump to content




New CC features!


  • You cannot reply to this topic
7 replies to this topic

#1 ElvishJerricco

  • Members
  • 803 posts

Posted 30 March 2015 - 08:01 PM

Auto completion coming to CC!

Couple of things to note:
  • We have the grays on black and white computers!
  • Showing this by example in the Lua REPL program means that either it's hard coded into the REPL, or it's now API in the read function, which would be awesome.


#2 ItsRodrick

  • Members
  • 72 posts
  • Location= gps.locate() or "unknown"

Posted 30 March 2015 - 08:24 PM

It also works at the Edit program! :D

Also, the Edit program now has RUN

#3 Geforce Fan

  • Members
  • 846 posts
  • LocationMissouri, United States, America, Earth, Solar System, Milky Way, Universe 42B, Life Street, Multiverse, 4th Dimension

Posted 30 March 2015 - 08:32 PM

I'm not sure how I feel about this. It could easily be done as a user-made program

#4 ElvishJerricco

  • Members
  • 803 posts

Posted 30 March 2015 - 08:44 PM

View PostGeforce Fan, on 30 March 2015 - 08:32 PM, said:

I'm not sure how I feel about this. It could easily be done as a user-made program

I've never liked that this is kind of the go to response when new features are suggested. Sometimes the suggested features are so obvious that there's no reason not to have it in. I think auto-complete is one of those.

Anyway, being in edit raises some questions about how this works. Edit doesn't use read(), so how exactly is it using the same API as the Lua REPL?

#5 Bomb Bloke

    Hobbyist Coder

  • Moderators
  • 7,099 posts
  • LocationTasmania (AU)

Posted 30 March 2015 - 09:21 PM

Methinks it's less likely the feature is built into the "lua" script, and more likely it's built into an API function that both read() and the "edit" script are able to call.

It strikes me that there may be a behaviour switch to make it work in the shell with folders/files. We haven't seen it functioning that way yet, but I imagine Dan'd go for a uniform experience and have it available there too. I guess we'll see.

Quite frankly I more interested in the grey background, but being able to tab in commands'll indeed be handy. :)


#6 SquidDev

    Frickin' laser beams | Resident Necromancer

  • Members
  • 1,427 posts
  • LocationDoes anyone put something serious here?

Posted 31 March 2015 - 07:36 AM

I love the way I watched both clips before reading this and didn't even notice the grey background! I'm pretty excited, but it would be even better if this was implemented inside the shell as that is where I spend most of my time. All we need now is that read()'s history ignores duplicates and empty strings!

#7 ElvishJerricco

  • Members
  • 803 posts

Posted 31 March 2015 - 08:19 AM

View PostSquidDev, on 31 March 2015 - 07:36 AM, said:

I love the way I watched both clips before reading this and didn't even notice the grey background! I'm pretty excited, but it would be even better if this was implemented inside the shell as that is where I spend most of my time. All we need now is that read()'s history ignores duplicates and empty strings!

We also need UNIX-like piping but one step at a time I guess =P

#8 Wojbie

  • Members
  • 631 posts
  • LocationKinda lost

Posted 31 March 2015 - 08:19 AM

Gray background is one big change for basic computers. If it adds gray font color too it would mean we now have 6 instead of 2 readable combinations of colors. (7 instead of 3 if you can read black on not so black combo - i can't)

As for tab-completion. Well depending on how its implemented (and if its implemented into shell) that could mean death to my extended shell. And i can't be more happy about that :D . If not that will make it a lot smaller.

Edited by wojbie, 31 March 2015 - 08:20 AM.






1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users