Conversation
Owner
Author
|
cc @peterhellberg, this should help your bot too :) (Also we miss you on ssh-chat!) |
tyrelsouza
approved these changes
Apr 15, 2020
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is the beginning of the bot and api modes for ssh-chat.
Primarily, it disables our custom re-rendering pipeline (which emits a slew of control characters that are increasingly hard to parse for bots), it also disables the message echo'ing and defaults to the mono theme. Should be a very clean output that is easy to parse.
This should also make testing easier.
Comparing outputs, default: (using
cat -A)TERM=bot: