commit | 010844f8d64ea5b35e425597b09f59e37a427c6a | [log] [tgz] |
---|---|---|
author | rginda <rginda@chromium.org> | Mon Jun 07 17:48:49 2010 -0700 |
committer | rginda <rginda@chromium.org> | Mon Jun 07 17:48:49 2010 -0700 |
tree | 4b825dc642cb6eb9a060e54bf8d69288fbee4904 |
initial add of chromeos shell and cros-term BUG=chromium-os:3884 TEST=None yet. cros-term takes care of launching the appropriate xterm stand-in, with a suitable environment. crosh is a read-eval-print loop with a whitelisted set of commands. It is intended to be started by our xterm, instead of bash, so that we don't have to give a full bash prompt. I don't believe platform/window-manager is really the correct place to stash these scripts in the long term. Short term, we'd like to land this in time to cherry-pick into R7, and window-manager seems like the best of the wrong places. If this ends up being something we keep around, it probably deserves its own repo. Review URL: http://codereview.chromium.org/2733001
This tree is empty.