public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Tristan Lazard <trislaz.tl-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: CSS style sheet for markdown conversion
Date: Thu, 23 Apr 2020 06:18:38 -0700 (PDT)	[thread overview]
Message-ID: <fb096b99-0d8a-4b71-8d76-de764e207d80@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1251 bytes --]

Hello,

I've been through the messages and did not see anyone with the same 
problem...
I am afraid that it may be very simple but I can't find a way to solve it.
I used to have a small webpage that i write in markdown and convert to html 
with pandoc and I did that using the --css option.
It worked fine until I changed my computer and I began having troubles on 
OSX, the css option is not taken into account when generation the html file

[image: Capture d’écran 2020-04-23 à 15.14.20.png] 
<about:invalid#zClosurez>


The css does not appear and no error is raised... I verified if 
css/retro.css is here etc... but even if i put a wrong path it stil raises 
no error and process the .md into a non-styled html.

I am using pandoc 2.9.2.1

Any clue of what i am doing wrong ?

Thank you !

Tristan


-- 
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/fb096b99-0d8a-4b71-8d76-de764e207d80%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2089 bytes --]

[-- Attachment #2: Capture d’écran 2020-04-23 à 15.14.20.png --]
[-- Type: image/png, Size: 109754 bytes --]

             reply	other threads:[~2020-04-23 13:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-23 13:18 Tristan Lazard [this message]
     [not found] ` <fb096b99-0d8a-4b71-8d76-de764e207d80-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-23 15:46   ` K4zuki
     [not found]     ` <1636f74f-d643-4c30-b9a5-da7b8fac3e2c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-23 15:54       ` John MacFarlane
     [not found]         ` <m2h7xadwpb.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2020-04-23 15:58           ` Tristan Lazard

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=fb096b99-0d8a-4b71-8d76-de764e207d80@googlegroups.com \
    --to=trislaz.tl-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).