What would the semantics of
tessel select be across multiple terminals or shell scripts? How would this be implemented?
If it writes the selected device to a config file, that will be shared across all the user's sessions and lead to a terrible mess of race conditions and unexpected changes.
Ideally, it would be local to the shell running the command and descendants, like an environment variable, but that doesn't work with the proposed interface without major hackery. (Making the user
source a setup script, and making
tessel actually a shell function, not a binary on
Or, what's wrong with the logical extension of the current interface:
tessel run ...
Can't blink it automatically, but it's at least very clear what the semantics will be.