Checkbox state

[sweenzor]

Continuing our conversation from ydkhatri/mac_apt/issues/13:

I've gotten it up and running. Super exciting! Thanks for the hard work!

When I'm using either the -m or -h args, I get checklist items decorated with the following html:
<div style="103">

Regardless of whether or not the checkbox is checked.

[bshannon]

Ya, there's a bunch of stuff I haven't tried to handle yet. (Mostly haven't had time to get back to this.)

How do you think a checklist item should be formatted in html or markdown?

[sweenzor]

I would think markdown. I find this notation pretty reasonable: https://github.github.com/gfm/#task-list-items-extension-

…

On Sun, Apr 14, 2019 at 2:35 PM Bill Shannon ***@***.***> wrote: Ya, there's a bunch of stuff I haven't tried to handle yet. (Mostly haven't had time to get back to this.) How do you think a checklist item should be formatted in html or markdown? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAM9cpq3N7wGPVFnqWtGDiUmMIJ9SSIWks5vg58DgaJpZM4cuaZP> .

[sweenzor]

(But I can deal with any way of indicating checkbox state)

[sweenzor]

I just noticed something. When you copy and paste a checklist out of notes, the resulting text follows the GFM convention:

- [ ] Unchecked item
- [x] Checked item

[bshannon]

Just to let you know I haven't forgotten about this...

I started working on this, but it's not as straightforward as I was hoping.
I'm having to do more significant work than expected to get all but the
most trivial cases to work correctly.

[sweenzor]

Ah, bummer. I appreciate the effort!

…

On Fri, May 31, 2019 at 12:18 PM Bill Shannon ***@***.***> wrote: Just to let you know I haven't forgotten about this... I started working on this, but it's not as straightforward as I was hoping. I'm having to do more significant work than expected to get all but the most trivial cases to work correctly. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AABT24SRLTNJE7Z5SYWNZBDPYCKHBA5CNFSM4HFZUZH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUCXCQ#issuecomment-497560458>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABT24VQJR3HMI7MGDYJHR3PYCKHBANCNFSM4HFZUZHQ> .

[bshannon]

I think I've got it working now. Try the 1.1 release.

[sweenzor]

Oh awesome! I’ll give it a try!

…

On Fri, Jun 7, 2019 at 9:09 PM Bill Shannon ***@***.***> wrote: I think I've got it working now. Try the 1.1 release. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#1?email_source=notifications&email_token=AABT24WFAVYX4QPAICK7AB3PZMWG3A5CNFSM4HFZUZH2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXHMZIY#issuecomment-500092067>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AABT24UWFUTKLSFJFZORU2TPZMWG3ANCNFSM4HFZUZHQ> .

[sweenzor]

Working! Thank you!!