From: Gianluca Carbone <gianlucarbone96-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Use custom template for markdown
Date: Thu, 13 Oct 2022 03:26:35 -0700 (PDT) [thread overview]
Message-ID: <8c51680f-f2e8-452d-8a2e-2fd3a8657b16n@googlegroups.com> (raw)
In-Reply-To: <Y0aoMY1fhYewq6pw@localhost>
[-- Attachment #1.1: Type: text/plain, Size: 2341 bytes --]
Thank you! I made this mistake because I'm new with the tool! Thank you for
the help!
Il giorno mercoledì 12 ottobre 2022 alle 13:42:47 UTC+2 Bastien Dumont ha
scritto:
> -D stands for --print-default-template, not “print the template specified
> in your command”! Specifying your template file via --template when
> converting a file to markdown should work (but I don't know if you can
> strip the extension as you did).
>
> Le Wednesday 12 October 2022 à 03:16:49AM, Gianluca Carbone a écrit :
> > Hello guys,
> >
> > I tried to use a custom template written by me coping the content of the
> > command:
> > pandoc -D markdown
> >
> > Next I add some markdown lines as static text that I want in the output
> of my
> > markdown file.
> >
> > I put this file in the folder /home/ubuntu/.pandoc/templates/
> > nameproject.markdown, and I check the path of pandoc with the command:
> > pandoc --version
> >
> > When i want to see if pandoc use the correct template, I use:
> > pandoc -D markdown --template nameproject
> >
> > But it prints always the same default.markdown file
> >
> > How can I use a custom markdown file?
> >
> > Thanks in advance!
> >
> > --
> > 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 [1]pandoc-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To view this discussion on the web visit [2]
> https://groups.google.com/d/msgid/
> > pandoc-discuss/83207291-1220-4357-9ce3-6bfe591322b1n%40googlegroups.com.
> >
> > References:
> >
> > [1] mailto:pandoc-discus...-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
> > [2]
> https://groups.google.com/d/msgid/pandoc-discuss/83207291-1220-4357-9ce3-6bfe591322b1n%40googlegroups.com?utm_medium=email&utm_source=footer
>
>
--
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/8c51680f-f2e8-452d-8a2e-2fd3a8657b16n%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4031 bytes --]
prev parent reply other threads:[~2022-10-13 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 10:16 Gianluca Carbone
[not found] ` <83207291-1220-4357-9ce3-6bfe591322b1n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-10-12 11:42 ` Bastien DUMONT
2022-10-13 10:26 ` Gianluca Carbone [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=8c51680f-f2e8-452d-8a2e-2fd3a8657b16n@googlegroups.com \
--to=gianlucarbone96-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).