From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
pandoc-discuss
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: LaTeX end document / endinput compliance
Date: Sun, 20 Oct 2019 22:44:35 -0700 [thread overview]
Message-ID: <m2h842tzy4.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <881d31da-683e-456f-aa3d-b46ef5809ef1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Yes, you can submit a feature request.
A workaround could be using sed to remove everything from the
input document after \end{document} before passing it to pandoc.
Luis Rivera <jlrn77-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> So, there is no know workaround about this issue? May I submit a feature
> request to the repo?
>
> Confused,
>
> On Saturday, 5 October 2019 12:37:43 UTC-5, Luis Rivera wrote:
>>
>>
>>
>> On Friday, 4 October 2019 23:39:22 UTC-5, John MacFarlane wrote:
>>>
>>>
>>> Out of curiosity, what do you have in your LaTeX document
>>> after \end{document}?
>>>
>>>
>> From the earliest days I put back there (as well as after \endinput) bits
>> and pieces I don't want to discard, but don't make it to the final draft of
>> the paper either. This way I don't clutter my directories with zettel, and
>> I can find the discarded material for other purposes later. Then some
>> people want opendoc/openxml copies for whatever reason, and then I found
>> that the supposedly ignored materials pop up in the converted files.
>>
>> BTW I also miss the ability to comment out material with the {comment}
>> environment: but then regular %s do the job.
>>
>> Besides, the inability to handle materials this way with MarkDown is what
>> keeps me from moving to that format altogether.
>>
>> Cheers,
>>
>>
>
> --
> 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/881d31da-683e-456f-aa3d-b46ef5809ef1%40googlegroups.com.
next prev parent reply other threads:[~2019-10-21 5:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-05 1:26 Luis Rivera
[not found] ` <44a69616-a689-4fe8-9486-6beb8ae08f2d-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-05 4:39 ` John MacFarlane
[not found] ` <m2r23rg61j.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-05 17:37 ` Luis Rivera
[not found] ` <6bcd828b-6f90-45d4-a59f-f10b86dfb6f5-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-18 1:57 ` Luis Rivera
[not found] ` <881d31da-683e-456f-aa3d-b46ef5809ef1-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-10-21 5:44 ` John MacFarlane [this message]
[not found] ` <m2h842tzy4.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2019-10-22 20:41 ` Luis Rivera
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=m2h842tzy4.fsf@johnmacfarlane.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=jlrn77-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).