| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | we'll be there in -1000 minutes isn't helpful | stuebinm | 2022-02-02 | 1 | -1/+1 |
| | | |||||
| * | pretty print pretty printing code | stuebinm | 2022-02-01 | 1 | -55/+54 |
| | | |||||
| * | handle (esp. iceportal) timestamps correctly | stuebinm | 2022-02-01 | 1 | -8/+8 |
| | | | | | | why use unix time if you can use unix time * 1000 while your margin of error will never be lower than a full minute? | ||||
| * | display iceportal itinery & stops | stuebinm | 2022-02-01 | 1 | -3/+36 |
| | | | | | | | | 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. | ||||
| * | hacky proof of concept | stuebinm | 2022-01-25 | 1 | -0/+67 |
 |
index : traveltext | |
| travelynx terminal client |
| summaryrefslogtreecommitdiff |