| Commit message (Collapse) | Author | Files | Lines | ||
|---|---|---|---|---|---|
| 7 days | do not require ds100 codes in API responsesHEADmain | stuebinm | 1 | -5/+5 | |
| these are not present when other hafas backends than the DB one were used for the trip's checkin. | |||||
| 2022-02-26 | from / to commands for travelynx | stuebinm | 1 | -7/+7 | |
| 2022-02-26 | fix the Trip type (and make it Display) | stuebinm | 1 | -21/+24 | |
| it's not as nice as i'd like, but whatever | |||||
| 2022-02-09 | existential types in rust are weird | stuebinm | 1 | -45/+19 | |
| … lots and lots of traits … | |||||
| 2022-02-02 | we'll be there in -1000 minutes isn't helpful | stuebinm | 1 | -2/+2 | |
| 2022-02-01 | pretty print pretty printing code | stuebinm | 1 | -128/+132 | |
| 2022-02-01 | are we there yet? | stuebinm | 1 | -1/+1 | |
| (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-01 | handle (esp. iceportal) timestamps correctly | stuebinm | 1 | -45/+41 | |
| 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-01 | display iceportal itinery & stops | stuebinm | 1 | -22/+8 | |
| 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-01 | better output if there are no intermediate stops | stuebinm | 1 | -10/+8 | |
 |
index : traveltext | |
| travelynx terminal client |
| summaryrefslogtreecommitdiff |