From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: preserve-tabs and line_blocks
Date: Wed, 12 Oct 2022 09:11:45 -0700 [thread overview]
Message-ID: <00528E94-4F91-40DC-89A2-F7D25C42B83A@gmail.com> (raw)
In-Reply-To: <ea4af10c-e784-4194-b1f0-b8135c76355an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
First, note that only initial indentation of lines is significant in line blocks; internal consecutive spaces will be collapsed anyway.
Second, --preserve-tabs does apparently have an effect, but it's not what you'd expect;
% printf "|\thi" | pandoc -t native
[ LineBlock [ [ Str "\160\160hi" ] ] ]
% printf "|\thi" | pandoc -t native --preserve-tabs
[ Para [ Str "|" , Space , Str "hi" ] ]
% printf "| \thi" | pandoc -t native --preserve-tabs
[ LineBlock [ [ Str "\160hi" ] ] ]
You should go ahead and put something about this on the bug tracker.
> On Oct 12, 2022, at 2:47 AM, Alcuin York <alcuin434-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
>
> From my own understanding of the pandoc manual, it seems that the --preserve-tabs option does not apply to line_blocks. And from my own attempts this also appears to be the case. So, 2 questions:
>
> 1. Is this correct (--preserve-tabs does not apply to line_blocks).
>
> 2. If yes to 1, would it be possible to incorporate it into pandoc?
>
>
>
> --
> 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/ea4af10c-e784-4194-b1f0-b8135c76355an%40googlegroups.com.
next prev parent reply other threads:[~2022-10-12 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 9:47 Alcuin York
[not found] ` <ea4af10c-e784-4194-b1f0-b8135c76355an-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-12 16:11 ` John MacFarlane [this message]
[not found] ` <00528E94-4F91-40DC-89A2-F7D25C42B83A-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-10-13 7:56 ` Alcuin York
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=00528E94-4F91-40DC-89A2-F7D25C42B83A@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).