Thanks folks, sounds like preprocessing is the way to go. Easy enough, I just didn't want to reinvent the wheel. Carl
On Wed, May 25, 2022 at 2:43 PM John Wiegley <[email protected]> wrote: > >>>>> "CT" == Carl Tappan <[email protected]> writes: > > CT> 1.) Is it possible to enter time in "HH:MM" format? Converting to > decimal > CT> hours is clunky, and the various timeclock options don't fit my > workflow > CT> well. I know that I can add a timelog entry with "time in" and "time > out", > CT> but ideally I'd be able to post directly to the account. > > You won't be able to use such a syntax to express durations of time, but > what > you COULD do is use the format you'd like and then write a processing > script > to convert those HH:MM entries into seconds. > > CT> 2.) Is it possible to define an hourly rate in a price history file, or > CT> some other persistent way that doesn't require recording each entry as > CT> xx.yyh @ $<rate> ? The documentation implies under 3.4.2 that time is > just > CT> a commodity, but setting a price as P h $<rate> doesn't seem to work. > If I > CT> log in units of 'hours' instead of 'h' then defining P hour $<rate> > works > CT> as expected, but I think that breaks the predefined equivalencies > between > CT> different time units. > > Price histories work differently from associating a conversion value with a > posting. I don't think the "P" directive will ever fully do what you'd wish > here. > > John > -- --- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ledger-cli/CAFNQEv66XWrvyiePvpVVnEbRRwRevH%3DRLpz8X3GOAxFj0DEtsQ%40mail.gmail.com.
