aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authoriximeow <me@iximeow.net>2017-12-01 01:49:28 -0800
committeriximeow <me@iximeow.net>2017-12-01 01:49:28 -0800
commit1e18587e5b6aabecd4200cfc3281567d3b7bf57a (patch)
tree9c5d6d3059a342eb8aa1a5d77797e8ed6a330fbe
parent50654583a0c8f51c58f4138a3d2564036e3f2855 (diff)
show json for DM, since fleshing that out is nextish on the to-do
-rw-r--r--src/tw/mod.rs2
-rw-r--r--todo13
2 files changed, 12 insertions, 3 deletions
diff --git a/src/tw/mod.rs b/src/tw/mod.rs
index 737286d..6dbc259 100644
--- a/src/tw/mod.rs
+++ b/src/tw/mod.rs
@@ -881,6 +881,7 @@ fn handle_twitter_twete(
tweeter: &mut TwitterCache,
display_info: &mut DisplayInfo,
_queryer: &mut ::Queryer) {
+ //display_info.recv(display::Infos::Text(vec![format!("{:?}", structure)]));
let twete_id = structure["id_str"].as_str().unwrap().to_string();
tweeter.cache_api_tweet(serde_json::Value::Object(structure));
display_info.recv(display::Infos::Tweet(TweetId::Twitter(twete_id)));
@@ -894,6 +895,7 @@ fn handle_twitter_dm(
display_info: &mut DisplayInfo,
_queryer: &mut ::Queryer) {
// show DM
+ display_info.recv(display::Infos::Text(vec![format!("{:?}", structure)]));
display_info.recv(display::Infos::DM(structure["direct_message"]["text"].as_str().unwrap().to_string()));
}
diff --git a/todo b/todo
index 98f8c56..6e4789a 100644
--- a/todo
+++ b/todo
@@ -3,12 +3,13 @@ hm.* -> thinking emoji
emoji -> :description:
:description: -> emoji
+tearing on media url
+
granular thread view (pageup shouldn't skip the whole thread through...)
follow/new follower notifications display the wrong person
-up/down scroll
-
+# vetoed for now
name/handle colored by user id instead of handle
recursively display quoted tweets?
@@ -19,6 +20,12 @@ history
per-account activity info
-show scrollback if any
+when scrolled back don't advance forward on new events
quick tweet interaction (goto :1234, f<ret> to fav, rep<ret> to reply, ...)
+
+fix client qt bug
+
+look into line wrapping issue with ansi-aware lengths and overflow for long usernames? might be unicode/not-really-monospace-font issues?
+
+updating information already stored to cache (this might be kind of tricky, maybe time to move to a decent storage format?)