Simon Michael

Followup: later, I found the lace UI by left clicking on the lace button which I had added to the browser toolbar. I think I tried that before, but possibly...

Hello @mchappell, I installed it from https://www.lace.io (did not build locally). I opened it yesterday after 2 weeks away and again struggled to get it working at first. I think...

I updated my comment: I'm currently seeing a 1s delay before the popup appears. And I see that if I click again before the popup appears, it cancels the popup....

From memory - Brave has three permission options for an extension: click (the toolbar button) to enable it each time, enable always on this site, and enable always on all...

I'll break out a smaller first step of this. phase 1: embed paypal/mint/wells fargo conversion rules, eg using a here quasiquoter or including the examples/* file similar to DocFiles.hs, and...

More notes: https://hledger.org/dev/hledger.html#timeclock The original timeclock.el has 0-1 fields after the time: `[COMMENT]` Ledger's timeclock format has 1-2: `ACCOUNT[ PAYEE]` hledger's timeclock format has 1-3: `ACCOUNT[ DESCRIPTION[;COMMENT]]` Before I hurt...

I think we can unambiguously say that semicolon always ends the account or description and starts a comment ?

In journal format (and timeclock reuses parsers from there) we don't allow escaping ; in any way, and it can't appear inside an account name or a description/payee/note.

To be clear, I agree with you, I think it's ok to enforce that a semicolon always begins the comment field, even though this will be a change in how...

I thought an account name was required on clockin entries. But I see it's not, as long as there's no trailing space: ``` i 2025-04-02 18:00:00 o 2025-04-02 18:01:00 ```...