public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "Pablo Rodríguez" <oinos-S0/GAf8tV78@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: is there a better way to solve this?
Date: Thu, 22 Jan 2015 21:25:38 +0100	[thread overview]
Message-ID: <54C15CC2.1020903@web.de> (raw)

John,

I have the following title:

    # `git` {}{.part}

Are the empty braces the best way to make the class refer to <h1> and
not to <code>?

BTW, how about the url try.pandoc.org?

Many thanks for your help,


Pablo
-- 
http://www.ousia.tk


             reply	other threads:[~2015-01-22 20:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22 20:25 Pablo Rodríguez [this message]
     [not found] ` <54C15CC2.1020903-S0/GAf8tV78@public.gmane.org>
2015-01-22 21:01   ` BP Jonsson
     [not found]     ` <54C1652E.7000401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2015-01-23 17:28       ` Pablo Rodríguez
     [not found]         ` <54C284BF.2070205-S0/GAf8tV78@public.gmane.org>
2015-01-23 21:21           ` BPJ
2015-01-22 22:09   ` Raniere Silva

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=54C15CC2.1020903@web.de \
    --to=oinos-s0/gaf8tv78@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).