From: Asher Harvey-Smith <asherharveysmith-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Leading \qquad not rendering in PDF output
Date: Sun, 16 Oct 2022 04:08:38 -0700 (PDT) [thread overview]
Message-ID: <98e1c77d-62e4-4f19-be83-18dff35a1469n@googlegroups.com> (raw)
In-Reply-To: <fnd3e6uPZu85K0ZeHvLrn6IgLoyruI0x6L65CzoLVf-SzdBOF6hWy6AVz8n62SK00X-WB5lH7OEWtUBOkrSua-MhLkSp2PwiUCgP6hymAuw=@protonmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 825 bytes --]
Thank you! \hspace* works great.
On Sunday, October 16, 2022 at 10:24:24 AM UTC+1 Nick Bart wrote:
> In fact, this has nothing to do with pandoc, but is a known behavior of
> LaTeX:
>
> See
> https://tex.stackexchange.com/questions/318454/quad-not-working-after-using-newline
> .
>
> Suggested solution: Use `\hspace*{2em}` instead of `\qquad`. (Do use the
> starred version, otherwise this will not work.)
>
--
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/98e1c77d-62e4-4f19-be83-18dff35a1469n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1685 bytes --]
prev parent reply other threads:[~2022-10-16 11:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 17:07 Asher Harvey-Smith
[not found] ` <87599708-491c-42c5-b448-798644e592d6n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-15 17:09 ` Asher Harvey-Smith
[not found] ` <5e3eaf24-bb25-4515-9300-0776d28cd544n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-15 20:09 ` John MacFarlane
[not found] ` <EEC5A828-F9B2-4EF9-9C25-09812C74F34B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-16 9:24 ` 'Nick Bart' via pandoc-discuss
2022-10-16 11:08 ` Asher Harvey-Smith [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=98e1c77d-62e4-4f19-be83-18dff35a1469n@googlegroups.com \
--to=asherharveysmith-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).