I think the use of defthing here is not really correct; I would argue that if
you’re going to use a defthing, you should go ahead and provide the definition
of the thing. Otherwise, just put in a reference to the name, so that the user
can click through to see the definition. I think that this “in-between” use
where you have the header but not the textual definition is violating user
expectations in a confusing way…
John
> On Jan 14, 2019, at 11:46 AM, Matthew Butterick <m...@mbtype.com> wrote:
>
> I believe the `defthing` tags need an empty {} after them.
>
>
>> On Jan 13, 2019, at 11:51 PM, Sorawee Porncharoenwase
>> <sorawee.pw...@gmail.com> wrote:
>>
>> This seems to be a known and expected output, however. According to
>> https://docs.racket-lang.org/demo-manual-m2/Definition_Blocks.html:
>>
>> Since no explanation flow is attached to the above defform use, there’s no
>> SIntrapara block around the table (just a <p>).
>>
>> The question is, when is this ever a desired output? It seems objectively
>> ugly and confusing in all use cases.
>
>
> --
> You received this message because you are subscribed to the Google Groups
> "Racket Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to racket-users+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
"Racket Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
