From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: weird: tab is replaced with spaces locally but not on pandoc.org/try
Date: Thu, 6 Apr 2023 10:15:46 -0700 [thread overview]
Message-ID: <AAE60CE7-FA54-4189-B663-F7880EC114C1@gmail.com> (raw)
In-Reply-To: <u0mlbg$6sh$1@ciao.gmane.io>
You can use `—preserve-tabs` on the command line if you want to preserve them. That’s just the default on the web app.
> On Apr 6, 2023, at 7:35 AM, jiewuza <jiewuza-9Onoh4P/yGk@public.gmane.org> wrote:
>
> I am using pandoc 3.1.2 locally.
> I convert some code block using tab as indentation from html to latex, and find the result is indented by spaces. While with the same input and cmdline on pandoc.org/try, tabs are reserved.
>
> I have no idea why.
> --
>
>
>
>
> ----Android NewsGroup Reader----
> http://www.piaohong.tk/newsgroup
>
> --
> 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/u0mlbg%246sh%241%40ciao.gmane.io.
--
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/AAE60CE7-FA54-4189-B663-F7880EC114C1%40gmail.com.
prev parent reply other threads:[~2023-04-06 17:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-06 14:35 jiewuza
2023-04-06 17:15 ` 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=AAE60CE7-FA54-4189-B663-F7880EC114C1@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).