| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
+ ? do {push @feeds, path("$feeds_dir/$_") foreach @ARGV}
Fixes custom feed loading.
The data structure is hash of
date mapped to a list of
entries which is a list of
$feed_name, $message
This also fixes omitting of entries as we store a list of entries so
we get multiple entries in same date map.
|
| | |
|
| |
|
|
| |
Send it to STDERR. Send everything to STDERR. I'm tired.
|
| |
|
|
|
|
| |
Now the program won't misbehave if user enters invalid feeds & it's
more flexible. Like the user can enter an invalid field, the program
will skip it & goto next.
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Now user can run `pyxis timeline <feed>' & it'll only load that feed.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
After this I'll make it possible to call single user timeline, like
`pyxis timeline <user>'. We will check in early in code & read only
this file.
Also, need to append user information in `%twtxt' along with support
for multiple entries in single date. Currently only one entry will
show up if there is a date clash.
I'll fix these by changing the data structure to hash table of a list
of hash table. So the list will contain 2 hashes - user & entry & the
list of this will be store in hash table so as to not over write
multiple entries of same time.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
That's basically giving my IP address to people because I don't think
anyone else will be using this. So feed owners could just link the IP
to me directly which is not good.
|
| | |
|
| | |
|
| |
|