Not a big fan of cron, I think something textual might be better.
Plus minutes don't matter and you can't do everything with cron ("second
tuesday of every month").You might also want to have a look at Wes McKinney's Pandas periodicity spec as well: http://pandas.pydata.org/pandas-docs/dev/timeseries.html#dateoffset-objects Also, look at how Google Calendar allows you to repeat events. More important than this is the problem of defining what it means to generate new transactions for forecasting. My take on this is that forecasting transactions should only get generated past the existing history. In other words, the system should be smart enough to only insert transactions that live "in the future", for some definition of what "the future" is. For me, "the last balance assertion of all the accounts from its postings" should be a good-enough definition. Also, one has to recognize that auto-generated forecast transactions are an approximate tool to estimate the future. They need to be treated as such, and not as a way to avoid data entry. I personally have not a single use case of a repeated transaction that is exactly as planned for all of its occurrences. The most regular is my apt. rent, perhaps, and even then, there are some exceptions here and there, some fees or corrections that make it irregular. I can't imagine people have many exactly regular transactions either, the real world just isn't that square. On Tue, Jul 8, 2014 at 7:38 PM, Eric Abrahamsen <e...@ericabrahamsen.net> wrote: > Craig Earls <ender...@gmail.com> writes: > > > I have been very slowly working on exactly that for a long time. I > > keep dithering on how to represent that kind of recurrence. So, since > > you are the first to ask, what would you like it to look like? > > Cron has been around for ages and is just about as expressive as you can > get -- maybe something based on that? > > > I was think of something like: > > <anchor date>+ perodicity > > For example every o > > Third Monday starting on 2014-07-14 would be: > > 2014-07-14+3w > > > > I have thought of other ways and all have merits. What would you > > like. Keep in mind the requirement for specifying a starting point > > > > On Tuesday, July 8, 2014, Richard Cobbe < > > rco...@gmail.com> wrote: > > > > (Please forgive me if this is a duplicate post -- I'm fairly new > > to Google groups, and my first attempt apparently went off into > > the ether rather than showing up on this list.) > > > > I'm trying to transition from GnuCash to ledger, and I'm looking > > for an equivalent to GnuCash's scheduled transactions. I see > > from the ledger-mode manual that there's some support for this > > feature in Emacs, and I've played around with it and figured out > > how to do simple things, like scheduling a transaction to run > > every month on the 13th, say, by supplying a date in the form [*/ > > */13]. > > > > Is there a way to schedule a transaction to run every other > > Monday? I don't see how to fit that into the date syntax that's > > described in the manual. I took a quick look at > > ledger-schedule.el, and ledger-schedule-descriptor-regex appears > > to support more expressive date specifications than just [*/*/ > > 13], but it's going to take me a while to figure out what's going > > on here. In particular, ledger-schedule-constrain-day appears > > not to support all of the possible options that the regex appears > > to allow. > > > > Ledger 3.0.3-20140608 on MacOS 10.9.4, for what it's worth. Oh, > > and Emacs 24.3.1. > > > > Thanks! > > > > Richard > > > > -- > > > > --- > > You received this message because you are subscribed to the > > Google Groups "Ledger" group. > > To unsubscribe from this group and stop receiving emails from it, > > send an email to ledger-cli+unsubscr...@googlegroups.com. > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > Craig, Corona De Tucson, AZ > > enderw88.wordpress.com > > > > -- > > > > --- > > You received this message because you are subscribed to the Google > > Groups "Ledger" group. > > To unsubscribe from this group and stop receiving emails from it, > > send an email to ledger-cli+unsubscribe-/ > > jypxa39uh5tlh3mboc...@public.gmane.org. > > For more options, visit https://groups.google.com/d/optout. > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Ledger" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ledger-cli+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Ledger" group. To unsubscribe from this group and stop receiving emails from it, send an email to ledger-cli+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
