From: Craig Parker <craigp-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Conditional Formatting
Date: Thu, 19 Sep 2019 07:14:27 -0400 [thread overview]
Message-ID: <1250a102-4bc2-d9ae-1f46-bc7e4d3ab286@linuxacademy.com> (raw)
In-Reply-To: <c18b9c78-2262-4f63-b995-0698dc795132-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 3408 bytes --]
I already took it and ran with it. A designer called for all top level
list items to be bold. That's fine, unless the whole list is just top
level items, then it looks funny. :::nobold takes care of that. And
:::nonum addresses the next level being actual numerals. When we don't
need numbered steps, we don't need numbers.
I'm sure there are a plethora of other uses I can find for it, but then
I just need to make sure that it doesn't start getting confusing for folks.
On 9/19/19 1:15 AM, brainchild wrote:
> Specific to Pandoc, it seems.
>
> It is a behavior in Pandoc that is not specified in MarkDown dialects
> generally, or supported in other software currently.
>
> It is implemented in Pandoc as an extension, meaning that the behavior
> can be toggled. Actually, I am confused about which extensions are
> enabled or disabled by default, but this one appears to work on a
> basic invocation of Pandoc.
>
> While it seems ideally suited to your requirements as long as you are
> using Pandoc, you do ask the right question, and should be aware that
> results might be unpredictable with editors, readers, or other
> MarkDown converters.
>
> Yet, it seems to be one of the more useful features not part of common
> MarkDown dialects.
>
> In a pinch you can use Pandoc to convert from a document using these
> extensions into a common dialect of MarkDown, suitable for ingestion
> by another converter.
>
>
> On Wednesday, September 18, 2019 at 10:46:51 AM UTC-4, Craig Parker
> wrote:
>
>
> Is this something specific to pandoc, github markdown, or what?
>
>
> --
> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> <mailto:pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/c18b9c78-2262-4f63-b995-0698dc795132%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/c18b9c78-2262-4f63-b995-0698dc795132%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
Learn by Doing with Linux Academy Multicloud Training
<https://linuxacademy.com>
*#1 Learn-by-Doing Multicloud Training Platform*
*Craig Parker*
Technical Writer
Schedule a Meeting or Call <http://www.fossfolks.com>
125 Bear Creek Parkway. Keller. Texas 76248
LinuxAcademy.com <https://linuxacademy.com>
Learn faster and deeper with REAL Hands-On Labs.
<https://linuxacademy.sigstr.net/uc/5d5b0bc61a99af20f77b0db4>
© Linux Academy, 2019. All Rights Reserved.
Pinehead® and the Linux Academy Logo® are registered trademarks of Linux
Academy in the U.S. and other countries. Linux® is a registered
trademark of Linus Torvalds in the U.S. and other countries.
--
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/1250a102-4bc2-d9ae-1f46-bc7e4d3ab286%40linuxacademy.com.
[-- Attachment #2: Type: text/html, Size: 8220 bytes --]
prev parent reply other threads:[~2019-09-19 11:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 18:51 Craig Parker
[not found] ` <34b81ee8-2405-5b3a-bbc9-23600a2802c5-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-09-17 19:11 ` John MacFarlane
[not found] ` <yh480ktv9ahh68.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-17 19:21 ` Craig Parker
[not found] ` <214b77f6-5739-eba4-ff5d-ea5d1fa553b9-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-09-17 23:38 ` John MacFarlane
[not found] ` <yh480kr24eh4s5.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-09-18 14:12 ` BP Jonsson
[not found] ` <CAFC_yuQ3GEoYovUB+tg6iSs_hL9bDGq7RCoDT93GemZXz+CSYw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2019-09-18 14:46 ` Craig Parker
[not found] ` <99b9af3a-c206-d664-3b58-d671eabd9116-UzRat0APdLvLPIzirxu/xA@public.gmane.org>
2019-09-18 15:32 ` John Gabriele
2019-09-19 5:15 ` brainchild
[not found] ` <c18b9c78-2262-4f63-b995-0698dc795132-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-09-19 11:14 ` Craig Parker [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=1250a102-4bc2-d9ae-1f46-bc7e4d3ab286@linuxacademy.com \
--to=craigp-uzrat0apdlvlpizirxu/xa@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).