Robert O Butts
Robert O Butts
Right now there's no code to handle the disconnect. It'll just panic, or stop receiving messages. We should handle it, try to reconnect, give the user a message, etc.
There are a ton of RTM messages we just ignore right now. Basically all of them but new messages. We should do something intelligent for all of them.
Currently, there's a bug that messages are fetched and displayed, for whatever channel happens to be focussed, as soon as the managers finish initialising. Either it needs fixed to not...
Right now, the channel manager queries 'channels' from the Slack API, which only gets regular channels. We probably want to get personal and group channels too, and treat them like...
Right now, sent messages are flagged as user ID 'me" user name 'me.' The user manager should be fixed to fetch the current user from the API.
Currently, the message window is unselectable, and unscrollable. It simply shows the last messages which fit in the terminal height. The messages window should also be fixed to correctly display...
The input box should handle commands like C-a, C-e, C-k, C-v, Home, End, M-→, M-←, etc. We probably _don't_ want to make C-c copy. I'd like to preserve C-c killing...
Changes the logger to not call Printf when the logger is io.Discard. Also changes the logger constructor to use `io.Discard` instead of `io.MultiWriter(io.Discard, io.Discard)`, which is necessary to detect all...