| Age | Commit message (Collapse) | Author |
|---|
|
|
|
if a handle is the same color as the background it becomes invisible
counting ansi string lengths is not supported, so that would be work
|
|
tweets are now recorded with the date they are recieved at
dated id lookup is now supported
tweet ids, where displayed, are displayed in a convenient form:
if the tweet was recieved today, show the today id
if the tweet was recieved on a different day, show the bare id
many instances where display_info was passed for logging information,
the parameter has become unnecessary, so it's gone now
|
|
update todo
|
|
|
|
what a mess... threading this through to any point where printing happens is upsetting. probably should be a global mutable behind accessors.
|
|
add connection state tracked per-stream, add explicit TwitterProfile
mapped to names that can be used for accounts. default names are the
handle of the corresponding twitter account.
partition out user Credential to be per TwitterProfile, so fav, reply,
etc, all come from the selected account. Multiplex twitter connections
and message streams across chan (instead of earlier plan, which was to
have one chan per thread)
|
|
also disable rendering of delete events
|
|
this is, hopefully, the start of support for correctly wrapping lines
with ANSI control codes included. additionally, hopefully the start of
supporting coloring @'s in tweets.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
also fix bug where cached user info takes precedence over (possibly
updated) api json user info
|
|
|
|
move DisplayInfo into ... display
flush output, duh
|
|
|
|
|
|
kind of.
add DisplayInfo struct that eventually can be used for rendering to any
particular interface. I care primarily about rendering to a CLI, so.
to support this: many instances of rendering with println!() are moved
to at least be orchestrated by display::paint, which will eventually
become smart enough to handle a reserved area for state notifications
from the client, and buffer input nicely, ....
more code moved over to use TweetId instead of bare strings
because DisplayInfo is currently a member on TwitterCache, any cases of
writing to DisplayInfo also involve writing to TwitterCache, which means
TwitterCache is mut like... everywhere.
Also, invalid TweetId in IdConversions ends up logging, meaning anything
calling that conversion requires a mut TwitterCache, by the above
paragraph.
|
|
|
|
escape more stuff
avoid possible breakage if we dont have the fav of a retweet
|
|
|
|
double-post bug if you are the author of the quoting tweet because you see the event AND your tweet in your feed
|
|
|
|
|
