rules lookup should be extended to look for rules in additional paths about hledger-flow HOT 5 CLOSED

The preprocess script could be a simple shell script that just runs the one you maintain elsewhere

Sure, that works too

from hledger-flow.

Interesting use case, I'll have to think about it some more.

Very nice idea though to have a place where people can share scripts and rules files!
Similar to the example rules files in hledger, but also supporting scripts.
https://github.com/simonmichael/hledger/tree/master/examples/csv

I'm using symlinks to point some of my preprocess and construct scripts to scripts maintained elsewhere. Haven't considered environments that doesn't have symlinks.

A very hacky workaround for now could be to make your preprocess a simple script wrapper that copies the rules file, and then runs the real preprocess in the external repo.

from hledger-flow.

Another option, instead copying the rules file with a script, could be to have an include line in a rules file used by hledger-flow which just points to the path of the external rules file.

https://hledger.org/manual.html#csv-format

from hledger-flow.

I prefer sticking to the hledger feature set rather than complicate your codebase.
include (in the sense of what is described at https://hledger.org/manual.html#include) would work, what about preprocess scripts though?

(mind you, I only have one preprocess script so far, and I could probably get rid of it)

from hledger-flow.

I prefer sticking to the hledger feature set rather than complicate your codebase.
include (in the sense of what is described at https://hledger.org/manual.html#include) would work, what about preprocess scripts though?

(mind you, I only have one preprocess script so far, and I could probably get rid of it)

The preprocess script could be a simple shell script that just runs the one you maintain elsewhere

from hledger-flow.