From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: block-headings variable seems to be ignored
Date: Tue, 18 Oct 2022 12:25:10 -0700 [thread overview]
Message-ID: <B9A8B9A4-4DF3-4CC6-912D-2176396AD629@gmail.com> (raw)
In-Reply-To: <CADAJKhAGBFXH9jhkuebbhsBWCKtZaYUKPJ-Z4P_tpJz0HEhxmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
> On Oct 18, 2022, at 3:13 AM, BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
>
>
> Den tis 18 okt. 2022 00:34John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> skrev:
> If you use `-t latex -s`, or if you use `—verbose` while producing a PDF, you’ll see the LaTeX intermediate file.
> Check to see that it includes these lines in the preamble:
>
> % Make \paragraph and \subparagraph free-standing
> \ifx\paragraph\undefined\else
> \let\oldparagraph\paragraph
> \renewcommand{\paragraph}[1]{\oldparagraph{#1}\mbox{}}
> \fi
> \ifx\subparagraph\undefined\else
> \let\oldsubparagraph\subparagraph
> \renewcommand{\subparagraph}[1]{\oldsubparagraph{#1}\mbox{}}
> \fi
>
> How come `\mbox{}` has the desired effect? I would have expected `\hfill` which you must use to make an `\item` appear on its own line.
>
I'm not sure, I didn't come up with this.
--
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/B9A8B9A4-4DF3-4CC6-912D-2176396AD629%40gmail.com.
prev parent reply other threads:[~2022-10-18 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-17 19:59 Claudio Di Vita
[not found] ` <ef6821e6-6de5-4f8c-b3c9-5692df472e27n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-17 22:06 ` John MacFarlane
[not found] ` <E53EB13B-6757-4117-B86D-D2A847FEAB10-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-17 22:19 ` Claudio Di Vita
[not found] ` <CAMBF16uxC=CzeL0+bdYGnQHkBgHC5PoBqkR+sHUmddXNf6tnHw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-17 22:24 ` John MacFarlane
[not found] ` <FF4194CA-FA19-4713-9C95-6A73B56E4D5C-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-17 22:26 ` Claudio Di Vita
[not found] ` <CAMBF16uzMHBaD6q7M7DJ1Oyqt=1WCcKTTh4HhsQBpNd2qfzw+Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-17 22:33 ` John MacFarlane
[not found] ` <0B3B83E5-1716-4F88-BD91-E560515C0AC0-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-18 9:26 ` Claudio Di Vita
2022-10-18 10:13 ` BPJ
[not found] ` <CADAJKhAGBFXH9jhkuebbhsBWCKtZaYUKPJ-Z4P_tpJz0HEhxmQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-10-18 19:25 ` John MacFarlane [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=B9A8B9A4-4DF3-4CC6-912D-2176396AD629@gmail.com \
--to=fiddlosopher-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).