Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reversed tweet display order for better piping #40

Open
ghost opened this issue Apr 30, 2012 · 3 comments
Open

Reversed tweet display order for better piping #40

ghost opened this issue Apr 30, 2012 · 3 comments

Comments

@ghost
Copy link

ghost commented Apr 30, 2012

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! :)

@jgoerzen
Copy link
Owner

jgoerzen commented May 1, 2012

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?

1 similar comment
@jgoerzen
Copy link
Owner

jgoerzen commented May 1, 2012

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?

@MentalFS
Copy link

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).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants