From: Robert Klein <roklein@roklein.de>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode@gnu.org
Subject: Re: PATCH: programming language indicators in HTML export
Date: Tue, 10 May 2016 21:07:04 +0200 [thread overview]
Message-ID: <20160510210704.7a54bec7@lt70.fritz.box> (raw)
In-Reply-To: <87inymdyp2.fsf@gmx.us>
Hi,
Rasmus <rasmus@gmx.us> wrote:
> Robert Klein <roklein@roklein.de> writes:
>
> > Hi,
> >
> > Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> >
> >> Hello,
> >>
> >> Robert Klein <roklein@roklein.de> writes:
> >>
> >> > anyone willing to commit this patch I sent back in march?
> >>
> >> This patch actually felt through the cracks. Sorry about that.
> >> Would you mind sending it again, using git format-patch so I can
> >> apply it?
> >>
> >
> > Please find the patch attached.
>
> I wonder if it would be possible (or even desirable) to build this
> part of the css header automatically? It may be too prone to
> unexpected bugs.
>
basically same answer I gave last time; when you want JS to create the
CSS you still have to map the source block identifier to ``readable''
text elsewhere. You'd just move the static from org-modes basic CSS
into org-mode.
I think the patch is a bonus for those, that don't roll their own CSS
(e.g. Tianxian Xiong, who first gave me the idea).
Any automated solution would be error-prone, too, and depend on:
- what's the Emacs mode for editing (or is there one at all)?
- is there an ob-<language> module for running the code?
- for LaTeX export: is the language supported by
- the LaTeX listings package (and what is its name there?)?
- or the pygments library (for those using the LaTeX minted package)?
One example I use for documentation is `conf' source blocks for
`generic' configuration files. For LaTeX export I have to add
(add-to-list 'org-latex-listings-langs '(conf " "))
to my .emacs, as the listings package doesn't support a `configuration'
language.
It's a hack, but it works. I don't see a general solution (even if
restricted to the CSS header).
I see my patch as a `best effort' for getting things working out of the
box. Anyone rolling his own CSS will probably pick his 2 to 5
languages and be happy with them.
Best regards
Robert
next prev parent reply other threads:[~2016-05-10 19:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-14 14:16 PATCH: programming language indicators in HTML export Robert Klein
2016-03-14 15:59 ` Rasmus
2016-03-14 19:25 ` Robert Klein
2016-03-15 14:24 ` Rasmus
2016-03-15 14:35 ` Robert Klein
2016-05-09 11:01 ` Robert Klein
2016-05-09 20:05 ` Nicolas Goaziou
2016-05-10 5:19 ` Robert Klein
2016-05-10 9:55 ` Rasmus
2016-05-10 19:07 ` Robert Klein [this message]
2016-05-10 20:22 ` Nicolas Goaziou
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160510210704.7a54bec7@lt70.fritz.box \
--to=roklein@roklein.de \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).