Le Stephane

Thanks for re-opening. If I come up with a workaround worth sharing in the meantime, I'll share what I can.

I don't use autopostings much yet, but seeing the effects of my changes in journals would allow me to experiment much more with them.

This is not urgent

I have the following (working) workaround First, make it possible to override the hledger command in the scope of my root import directory ```bash (in the root import directory) $...

A possible workaround is to create an empty `.journal` in `1-in/YYYY+1` and `1-in/YYYY+2`. 

uh you're right, too much bookkeeping yesterday. I'll try to dig the exact command line that was generating an empty report and re-open with that.

FYI this is how i implement closing the year... ```bash #!/usr/bin/env bash source common.sh my_dir=$(readlink -e $(dirname "$0")) top_dir="$(dirname "${my_dir}")" usage() { cat &2 OPENING_FILE="${top_dir}/import/${OPENYEAR}-opening.journal" CLOSING_FILE="${top_dir}/import/${CLOSEYEAR}-closing.journal" ../hledger close \ --auto...

Here is more information: ```bash $ hledger bs -f includes.journal -f import/2017-include.journal Balance Sheet 2017/12/31 || 2017/12/31 =============++============ Assets || -------------++------------ -------------++------------ || 0 =============++============ Liabilities || -------------++------------ -------------++------------ ||...

The approach I now take is as follows - Have a `close-years.sh` script that, for each year, creates the `opening` and `closing` journal next to the hledger-flow `yyyy-include.journal` ```bash readonly...

> You need to either install hledger, or add it to your PATH, or **provide the path to an hledger executable.** I need more info on how to do that,...