From: Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Comments within a list
Date: Mon, 23 Aug 2021 10:03:27 -0400 [thread overview]
Message-ID: <867e0b56-f5fe-2351-5e58-59265529eec2@reagle.org> (raw)
In-Reply-To: <yh480kmtpbvku5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
Done: https://github.com/jgm/pandoc/issues/7521
On 21-08-20 17:59, John MacFarlane wrote:
>
> --strip-comments shouldn't affect this.
> Why don't you submit a bug report with a minimal example
> showing that it does, and we can look into it.
>
> Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:
>
>> It's the `--strip-comments` option that is causing sibling items around the commented one to be stuck in <p>. I learned of the `--strip-comments` recently and added it as a default to all of my builds -- might as well as keep sleuths from seeing comments to myself. And I just now stubbed my toe on it. Was I mistaken to think this option shouldn't have other side-effects?
>>
>>
>> On 21-08-20 15:52, John MacFarlane wrote:
>>> This works:
>>>
>>> - this is top 1
>>> - this is sub 1.1
>>> - this is sub 1.2
>>> <!-- - going to think about 1.3 for a bit -->
>>> - this is sub 1.4
>>> - this is top 2
>>> - this is sub 2.1
>>> - this is sub 2.2
>>> - this is sub 2.3
>
--
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/867e0b56-f5fe-2351-5e58-59265529eec2%40reagle.org.
prev parent reply other threads:[~2021-08-23 14:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 18:11 Joseph Reagle
[not found] ` <f554871e-a51e-5c58-502d-611a97ca95fd-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-08-20 18:40 ` Daniel Staal
[not found] ` <69e1034f-6462-61d9-45f9-3af2c9fd2a97-Jdbf3xiKgS8@public.gmane.org>
2021-08-20 18:55 ` Joseph Reagle
[not found] ` <decd3c8a-41f7-bcf2-addf-3e226cfc0896-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-08-20 19:03 ` William Lupton
[not found] ` <CAEe_xxg0N37nDD4kD5UfKcJOQM6xfRPVx69cTho=11mhYxWKCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-08-20 19:38 ` Joseph Reagle
2021-08-20 19:52 ` John MacFarlane
[not found] ` <yh480k35r3x5a1.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-08-20 21:03 ` Joseph Reagle
[not found] ` <e48f774d-2904-7c9f-1d8f-b21fca3977e8-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-08-20 21:59 ` John MacFarlane
[not found] ` <yh480kmtpbvku5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-08-23 14:03 ` Joseph Reagle [this message]
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=867e0b56-f5fe-2351-5e58-59265529eec2@reagle.org \
--to=joseph.2011-t1oy19wchswdnm+yrofe0a@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).