Hi all, I have a question about beangulp. I've noticed that compared to beancount.ingest, beangulp now produces more logging when doing an extract so I wanted to question why it's there.
In my specific case, I use beangulp directly within vim to import transactions directly into my beancount file. Using beancount.ingest the resulting text required no alteration as it only contained the header containing the filename and the transactions. But using beangulp, now I have to clean up the text because it has some logging to indicate the progress of the overall extraction which results in something like below (highlighted yellow). (gulp) [picasso@xps-13 beancount.dm-crypt]$ python gulp.py extract downloads/account-2021-04.ofx * /run/media/picasso/beancount.dm-crypt/downloads/account-2021-04.ofx ... OK ;; -*- mode: beancount -*- **** /run/media/picasso/beancount.dm-crypt/downloads/flexaccount-2021-04.ofx 2021-04-01 * "Transfer" Assets:Account 20.0 GBP I see that the information logging is output on stderr so I can redirect it to /dev/null however I would like to know how everyone else is using beangulp and whether this change of behaviour is only affecting me or other too. Actually even the beancount mode header also is superfluous in almost all of my cases but that is also being produced beancount.ingest. On Saturday, 20 February 2021 at 03:21:00 UTC bl...@furius.ca wrote: > Thank you for doing this! > > > On Fri, Feb 19, 2021 at 7:20 PM Daniele Nicolodi <dan...@grinta.net> > wrote: > >> On 02/02/2021 07:20, Martin Blais wrote: >> > Hi, >> > >> > Part of v3 plans is thinning out the repository. >> > I've just moved the beancount.ingest directory from beancount to a new >> > repository. >> > Announcing: >> > https://github.com/beancount/beangulp >> >> When beangulp was split off from the beancount repository, the git >> history was not preserved. Among other things, this made it not easy to >> identify contributors to the code. To address this, I used >> git-filter-repo to carve beangulp out of beancount preserving history. I >> just foce pushed the result to the beangulp master branch. >> >> The contents of the repository are identical, but the most recent git >> commits have been rebased and thus have different commit IDs. If anyone >> has open pull request or local commits, these will need to be rebased on >> top of the new repository head. "git rebase --help" has instructions on >> how to do it in the "RECOVERING FROM UPSTREAM REBASE" section. Let me >> know if you need help with it. >> >> I think I started this work when most likely I was the only one beangulp >> changes pending merge (Github reported that there were only an handful >> of forks of the beangulp repo and none had any commit to it). >> Unfortunately, by the time I pushed the new history a PR for beangulp >> popped up. I hope it is not too much trouble to rebase it. >> >> Sorry for the disruption, but I feel that preserving the history was >> worth the inconvenience. >> >> Cheers, >> Dan >> >> -- >> 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 beancount+...@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/beancount/7ee5273f-9857-6d83-9f0a-f667ac34c16d%40grinta.net >> . >> > -- 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 beancount+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/95abb52e-eedb-4053-b517-5ba73775e7ccn%40googlegroups.com.
