s0fasurfa

Nice idea, but the calendar format is a bit verbose for my taste. Week number is something I would have to look up constantly and surely get wrong more than once.

If you want to follow UNIX philosophy, why don't you write an augmenter/converter tool `caug` that adds "computed" information such as week number, weekday or even relative date?

  > cat calendar-src.txt

    2025
    ====
    03-01 9-12 project groups

  > cat calendar-src.txt | caug
    2025-03-01 w09 09:00-12:00 project groups +tomorrow 
    +thisweek

  > cat calendar-src.txt | caug | grep "thisweek"
    2025-03-01 w09 09:00-12:00 project groups +tomorrow 
    +thisweek

My major gripe with hledger and other plaintext accounting systems: setting up the correct rules (regex for your expenses) takes too much time as it involves:

a) defining the regexes/categories) for dozens to hundreds of expense descriptions (e.g. walmart, gas station xyz)

b) "recompiling" your hledger journals after every rule change

c) checking for negative and positive errors (expense description was not matched OR too many different expenses were matched)

This process is much faster in a spreadsheet application. IMHO the journal format of hledger and other plaintext accounts apps is too verbose.

it would be a great relief if someone started a Github repository with expense texts used when you e.g. pay at Carrefour in Italy or Walmart in the USA with your debit card. People could submit those descriptions from the CSV exports of their bank accounts.

Another annoyance in Europe is that there is no API connection for open source apps to bank account statements, you always rely on manual CSV exports.

Another red flag: this invoice was issued just days before the EURO was introduced in Germany (1st of January 2022). Invoices issued in these times would have surely shown the amount in EUR as well.