FYI, I've just pushed some changes that rework the punch logic to avoid this and other issues.
On Mon, Apr 7, 2014 at 2:48 PM, John Rigg <[email protected]> wrote: > On Mon, Apr 07, 2014 at 01:53:29PM -0700, J. Liles wrote: > > Yeah, I think I know what this is. I have some changes that completely > > rework the way punch in/out is handled to avoid this and some other > related > > bugs, but I haven't been able to test it adequately for publication. > > > > You should be fine editing the history file (but keep a backup!). No > matter > > how messed up it is, you can always go back to a point where it wasn't. > > > > Until I get the fix published, punch in/out will not be 100% reliable. > > I've restored the session to a fully working state. Good to know about the > likely cause and that it wasn't just a random occurrence. At least the > history > file is easy to read and edit :-) > > John > > >
