| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | we'll be there in -1000 minutes isn't helpful | stuebinm | 2022-02-02 | 3 | -4/+14 |
| | | |||||
| * | pretty print pretty printing code | stuebinm | 2022-02-01 | 7 | -457/+488 |
| | | |||||
| * | are we there yet? | stuebinm | 2022-02-01 | 2 | -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?) | ||||
| * | handle (esp. iceportal) timestamps correctly | stuebinm | 2022-02-01 | 4 | -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? | ||||
| * | display iceportal itinery & stops | stuebinm | 2022-02-01 | 6 | -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. | ||||
| * | better output if there are no intermediate stops | stuebinm | 2022-02-01 | 1 | -10/+8 |
| | | |||||
| * | add `traveltext destination` | stuebinm | 2022-02-01 | 2 | -0/+19 |
| | | | | | I have no intention of going to Hamburg today, so I need to check out earlier | ||||
| * | sadly i'm not on a ICE right now | stuebinm | 2022-01-26 | 1 | -4/+10 |
| | | |||||
| * | add a config file because why not | stuebinm | 2022-01-26 | 3 | -24/+128 |
| | | |||||
| * | some code deduplications | stuebinm | 2022-01-25 | 1 | -69/+88 |
| | | |||||
| * | hacky proof of concept | stuebinm | 2022-01-25 | 8 | -0/+1271 |
 |
index : traveltext | |
| travelynx terminal client |
| summaryrefslogtreecommitdiff |