You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love twidge for "vanilla" usage on the terminal, but there are a few things I'd like to try that involve piping twidge output. However, the newest-tweets-print-first system breaks a lot of these ideas unless I write some sort of wrapper code to reverse tweet output.
eg., if I simply want to archive my feed, I'd like to be able to run a cron job for "twidge lsrecent -asu >> ~/Docs/MyFeedArchive"
With the current setup, tweet order will get totally borked: tweets get appended to the file in subblocks, with the newer tweets in each sub-block being at the top of the block.
If there were a flag to simply reverse the order of tweet output, a pipe like this would work flawlessly.
Thanks for twidge! :)
The text was updated successfully, but these errors were encountered:
You're right - it wouldn't be too terribly hard to do. The API from twitter does not lend itself to this exactly, but a memory buffer could do it. But if you got the entire tweet on a single line, wouldn't tac(1) solve your issue?
You're right - it wouldn't be too terribly hard to do. The API from twitter does not lend itself to this exactly, but a memory buffer could do it. But if you got the entire tweet on a single line, wouldn't tac(1) solve your issue?
I'm using tac to pipe tweets into a file myself, but it is only useful when using -las well (or setting -whigh enough to guarantee only one line per tweet).
I love twidge for "vanilla" usage on the terminal, but there are a few things I'd like to try that involve piping twidge output. However, the newest-tweets-print-first system breaks a lot of these ideas unless I write some sort of wrapper code to reverse tweet output.
eg., if I simply want to archive my feed, I'd like to be able to run a cron job for "twidge lsrecent -asu >> ~/Docs/MyFeedArchive"
With the current setup, tweet order will get totally borked: tweets get appended to the file in subblocks, with the newer tweets in each sub-block being at the top of the block.
If there were a flag to simply reverse the order of tweet output, a pipe like this would work flawlessly.
Thanks for twidge! :)
The text was updated successfully, but these errors were encountered: