We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Frequently people don't know to press enter after flterm connects, so they sit there waiting for something to happen.
If we could send an enter after connecting, people would see the prompt.
An expect script would be even better. That would allow us to issue a reboot command.
The text was updated successfully, but these errors were encountered:
Example;
while True: send('\n') If recv('>'): Break Sleep() Send('reboot') || Send('serialboot')
Sorry, something went wrong.
Any chance of this being addressed in the firmware?
Installing a patched term program or addon config/script seems like it will cause more confusion than forgetting to press enter.
There is no way this can be addressed in firmware, the firmware gets no notification that a user has connected / disconnected from the console.
This flterm program is installed as part of our environment and is used for make load-firmware and similar commands.
make load-firmware
No branches or pull requests
Frequently people don't know to press enter after flterm connects, so they sit there waiting for something to happen.
If we could send an enter after connecting, people would see the prompt.
An expect script would be even better. That would allow us to issue a reboot command.
The text was updated successfully, but these errors were encountered: