Hello, When I run my beangulp importers `extract` step, the include the path of the file that generated the entries:
``` **** /home/john/Finances/downloads/statementA.CSV 2025-10-24 * "foo" Liabilities:Bar -14.87 USD Expenses:Baz **** /home/john/Finances/downloads/statementB.CSV 2025-10-14 * "foo" Liabilities:Bar -20.25 USD Expenses:Baz ``` However, those filepaths becoming meaningless once I run the importer `archive` step, which renames the files and moves them to my documents folder, e.g. `/home/john/Finances/documents/Liabilities/Bar/2025-10-14.bar.csv`. I think it would be more useful if the filepaths output by `extract` matched the path that results from `archive`. Currently I'm updating them manually. I am curious, how do others handle this? Would the maintainers of beangulp be open to a PR to implement this, perhaps as an option CLI flag on `extract`? Thanks, John -- You received this message because you are subscribed to the Google Groups "Beancount" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/beancount/ce6d6a31-bc18-4258-8e6c-924778d6bfban%40googlegroups.com.
