summaryrefslogtreecommitdiff
path: root/src (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-11-28handle unknown times at stationsstuebinm1-3/+11
(travelynx sends these as the literal epoch value, which led to really confusing results, printing exactly the time zone offset as arrival time)
2022-04-21add import from hafas to travelynxstuebinm1-10/+134
(using yuka's hafas-rs)
2022-02-26from / to commands for travelynxstuebinm3-10/+50
2022-02-26fix the Trip type (and make it Display)stuebinm4-34/+36
it's not as nice as i'd like, but whatever
2022-02-26iceportal: cancelled stops have state nullstuebinm1-1/+2
which … fine, i guess
2022-02-09existential types in rust are weirdstuebinm8-202/+312
… lots and lots of traits …
2022-02-08S-Bahns are weirdstuebinm3-1/+123
(added a simple zugportal.de api client, but can't do auto-checkin yet)
2022-02-02we'll be there in -1000 minutes isn't helpfulstuebinm3-4/+14
2022-02-01pretty print pretty printing codestuebinm6-457/+485
2022-02-01are we there yet?stuebinm2-1/+24
(also why do people get up from their seats a solid nine minutes before the train is even scheduled to arrive at all?)
2022-02-01handle (esp. iceportal) timestamps correctlystuebinm4-61/+68
why use unix time if you can use unix time * 1000 while your margin of error will never be lower than a full minute?
2022-02-01display iceportal itinery & stopsstuebinm6-28/+80
I'm pretty sure something in parsing the times is broken, since this train is currently /also/ broken I have absolutely no idea what the correct ones would be and don't have the energy to dig further into this.
2022-02-01better output if there are no intermediate stopsstuebinm1-10/+8
2022-02-01add `traveltext destination`stuebinm2-0/+19
I have no intention of going to Hamburg today, so I need to check out earlier
2022-01-26sadly i'm not on a ICE right nowstuebinm1-4/+10
2022-01-26add a config file because why notstuebinm1-24/+65
2022-01-25some code deduplicationsstuebinm1-69/+88