I think the date might actually have a meaning. E.g. if you split files by year you might have one marker in one file and another in the other and based on the date of the transaction it should go to the right one.
On March 31, 2018 5:59:40 AM GMT+02:00, Martin Blais <[email protected]> wrote: >On Fri, Mar 30, 2018 at 8:22 AM, Dominik Aumayr <[email protected]> >wrote: > >> I think that could be very useful. I think there needs to be some >> discussion about the syntax before you start implementing. >> >> Would it look like this? >> >> ```beancount >> >> 2018-03-30 * "Hooli Shop" "Buy hoodie" >> Expenses:Fashion 10.00 USD >> Assets:Cash >> >> marker Assets:US:* >> >> 2018-03-31 * "Walgreens" "Groceries" >> Expenses:Groceries 45.00 USD >> Assets:US:BoA:Checking >> >> ``` > > >Hmm, the few non-directive keywords I have at the moment don't have >proper >metadata (e.g. line number). >I was thinking of making it a directive instead. >e.g. > >2018-03-30 marker "...any string..." > >The date has no meaning (but it you can think of a useful meaning I can >add >one.) > >Also, the account name that's there, how is it used? Would it not be >more >general to make it a general string? > > > > >> >> > Am 28.03.2018 um 04:22 schrieb Martin Blais <[email protected]>: >> > >> > I could promote the custom entry as a native one. >> > Let's call it "marker". >> > Would that be useful? >> > >> > >> > On Tue, Mar 27, 2018 at 2:04 AM, ><[email protected]> >> wrote: >> > Fava has such a feature (and code), see the "insert-entry"-option >here: >> https://fava.pythonanywhere.com/example-with-budgets/help/options/ >> > >> > Basically it works like this: You can add custom "insert-entry" >entries >> with a RegEx, and when adding a transaction, the position where it >should >> go in the file is determined by those custom entries. >> > >> > Am Montag, 26. März 2018 22:39:48 UTC+2 schrieb Martin Blais: >> > New issue 257: Create a section classifier for new transactions >> > https://bitbucket.org/blais/beancount/issues/257/create-a- >> section-classifier-for-new >> > >> > Martin Blais: >> > >> > There's nothing like that in the Beancount codebase. I've thought >about >> building something to automatically insert imported transactions in >the >> right "section" (I personally use org-mode, where each section >corresponds >> to an institution and its related group of accounts) but it's unclear >> whether that would generalize. >> > >> > I think you could turn this into a simple classification problem. >Given >> some syntax for splitting up an input file into sections (e.g., some >> regular expression matching on a title or separator), you now have >groups >> of transactions and inputs. Somehow reduce this to a simple model for >> classifying which section an incoming transaction matches with >highest >> probability and insert it there. Or more appropriately - since >transactions >> are imported in groups - find the section that best matches all the >> transactions in the imported files and insert at the end there. >> > >> > >> > On Sun, Mar 11, 2018 at 12:28 PM, Michael Droogleever ><[email protected]> >> wrote: >> > I believe it is against the design of beancount, but is there any >> existing code which attempts to add transactions to an existing >beancount >> file. Assuming the entries in the file are grouped by asset account, >it >> would need to append the entry to the subsection of entries all from >the >> same account. >> > >> > Responsible: blais >> > >> > -- >> > 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 post to this group, send email to [email protected]. >> > To view this discussion on the web visit >https://groups.google.com/d/ >> >msgid/beancount/4694718a-6afc-4346-80de-c7c78bd87de6%40googlegroups.com. >> > >> > For more options, visit https://groups.google.com/d/optout. >> > >> > >> > -- >> > 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 post to this group, send email to [email protected]. >> > To view this discussion on the web visit >https://groups.google.com/d/ >> >msgid/beancount/CAK21%2BhMKca%3DWb8Jv45k9tHWHZ%2Bv2vbsG14yXtq4RyC6M9tB1mg% >> 40mail.gmail.com. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> 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 post to this group, send email to [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/beancount/B436BAF8-B56D-4FED-B9A1-F1B408AE6BD1%40aumayr.name. >> For more options, visit https://groups.google.com/d/optout. >> > >-- >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 post to this group, send email to [email protected]. >To view this discussion on the web visit >https://groups.google.com/d/msgid/beancount/CAK21%2BhM-bVNW8N7hdC1qv9GBFui_wDuV8viUOzYZKuBJXxRiKA%40mail.gmail.com. >For more options, visit https://groups.google.com/d/optout. -- 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 post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beancount/08A37AFC-EB5F-4344-AE12-43F32BE6435A%40ch.tario.org. For more options, visit https://groups.google.com/d/optout.
