Closed burggraf closed 10 years ago
yeah i had the same problem but when i updated from master it went away. maybe it's some sort of race condition.
@burggraf I can't reproduce this, so I'm going to need more details. How do you have triple installed? Is it from npm? Is it from source? If its from source, what commit hash? Be sure you have the latest from master as we've been adding features and fixes really fast the last few days.
I’m using npm. I even uninstalled and reinstalled via npm and got the same results.
On Jul 27, 2014, at 1:11 PM, Tony Lukasavage notifications@github.com wrote:
I can't reproduce this, so I'm going to need more details. How do you have triple installed? Is it from npm? Is it from source? If its from source, what commit hash? Be sure you have the latest from master as we've been adding features and fixes really fast the last few days.
— Reply to this email directly or view it on GitHub.
.exit
was resolved in #21 which is part of 0.2.0 development. It's not in the 0.1.x branch and therefore not on npm. triple dot commands are only available in the master branch at this time. You'll need to install from the repo directly if you want the commands, but bare in mind we are developing fast in master and that stability is not guaranteed.
Typing .exit from the prompt does not exit triple. Instead it just gives a triple-dot prompt and accepts commands until you press control+C to break out. Pressing control+C again exits the app as .exit should.
Example:
$ triple [launching app] > .exit ... <-- press control+c here to exit out of the ... prompt set (^C again to quit) <-- press control+c here again to exit triple