reply

NAML documentation   Watch a video
   Usages of this macro
The source code below doesn't have navigation links because no usage has been compiled yet. Navigation links depend on how and where the macro is used, so first you may try finding all usages of "reply".
... in reply.naml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
<override_macro name="reply" requires="servlet">
    <n.new_post>
        <page_name>
            <t>Reply</t>
        </page_name>
        <focus>
            <n.message_field.focus/>
        </focus>
        <mailing_list_etiquette>
            <li><t>Quote what you reply to and trim it to only the relevant parts. This provides context for those who will read your message by email.</t></li>
            <li><t>Avoid small talk such as "Thank you", "Great"... You can <n.page_node.reply_to_author_link.>send a private email</n.page_node.reply_to_author_link.> if you want.</t></li>
        </mailing_list_etiquette>
        <bottom>
            <n.in_reply_to/>
        </bottom>
    </n.new_post>
    
    <script type="text/x-mathjax-config">MathJax.Hub.Config({tex2jax:{inlineMath:[['$','$']]}});</script>
    <script src="https://cdnjs.cloudflare.com/ajax/libs/mathjax/2.7.5/MathJax.js?config=TeX-AMS-MML_HTMLorMML"></script>
    
</override_macro>
Overrides default macro
... in reply.naml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
<macro name="reply" requires="servlet">
    <n.new_post>
        <page_name>
            <t>Reply</t>
        </page_name>
        <focus>
            <n.message_field.focus/>
        </focus>
        <mailing_list_etiquette>
            <li><t>Quote what you reply to and trim it to only the relevant parts. This provides context for those who will read your message by email.</t></li>
            <li><t>Avoid small talk such as "Thank you", "Great"... You can <n.page_node.reply_to_author_link.>send a private email</n.page_node.reply_to_author_link.> if you want.</t></li>
        </mailing_list_etiquette>
        <bottom>
            <n.in_reply_to/>
        </bottom>
    </n.new_post>
</macro>