public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Norman Ramsey <fellswalker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Can pandoc be prevented from renumbering ordered lists?
Date: Wed, 1 Feb 2023 11:47:57 -0800 (PST)	[thread overview]
Message-ID: <9c5112a4-b699-4f82-b962-c4f5e8cd55can@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1624 bytes --]

At the moment I'm sending feedback to students with numbering like the 
following:

```markdown
3. I'm not sure this is an issue with literals, as our VM doesn't support 
pointers or dereferencing in any obvious way.  But I grant you the point.

4. This answer says both that `loadfun` would have to change and that "the 
loader shouldn't have to change.  These statements aren't internally 
consistent (only one can be true).  As for functions returning, no change 
is needed to `VMFunction`.  All that's needed is a `Return` instruction.

5. Nice thinking about cache effects.

<!--comment-->

7. Good thinking.  Later on we'll see that it is sufficient to be sure that 
every execution path in a function ends with a `Return` instruction.

8. I didn't make the Booleans static because I wanted a `mkBooleanValue` 
with a dynamic argument.  Adding static values has no payoff.  (A `Value` 
fits in two hardware registers.)


<!--comment-->

10. Nice work.
```

If I ever forget to include `<!--comment-->`, the feedback goes to the 
student with the wrong number.  

I know that the Markdown specification says that items in ordered lists 
will be renumbered.  But is there a way to tell pandoc not to do that?

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/9c5112a4-b699-4f82-b962-c4f5e8cd55can%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2107 bytes --]

                 reply	other threads:[~2023-02-01 19:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9c5112a4-b699-4f82-b962-c4f5e8cd55can@googlegroups.com \
    --to=fellswalker-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).