From: Carsten Dominik <dominik@science.uva.nl>
To: Scott Otterson <scotto@u.washington.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: local variables for html export
Date: Thu, 25 May 2006 23:28:49 +0200 [thread overview]
Message-ID: <d275eafe2524a9edacc077f517ff1cb7@science.uva.nl> (raw)
In-Reply-To: <4475FEF6.10600@u.washington.edu>
You are right, this is a recent change in emacs 22 (emacs 21 was more
forgiving.
In fact, suffixes are not needed, they are allowed, in order to use
this in fils where comments need a special end delimiter. But now
indeed prefixes are needed in each line, also in the middle of an
extended string value of a variable. Thanks. I have fixed this for
the next version.
- Carsten
On May 25, 2006, at 21:01, Scott Otterson wrote:
> I think there's an error in the org-mode manual. The snippet at the
> end of section 9.2:
>
> * COMMENT HTML style specifications
> # Local Variables:
> # org-export-html-style: " <style type=\"text/css\">
> p {font-weight: normal; color: gray; }
> h1 {color: black; }
> </style>"
> # End: ***
>
> needs to have prefixes and suffixes, like this:
>
> * COMMENT HTML style specifications
>
> # Local Variables: ***
> # org-export-html-style: " <style type=\"text/css\"> ***
> # p {font-weight: normal; color: gray; } ***
> # h1 {color: black; } ***
> # </style>" ***
> # End: ***
>
> At least this is the case with emacs 22.0.50.2
>
> Scott
>
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
prev parent reply other threads:[~2006-05-25 21:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 19:01 local variables for html export Scott Otterson
2006-05-25 21:28 ` Carsten Dominik [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
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=d275eafe2524a9edacc077f517ff1cb7@science.uva.nl \
--to=dominik@science.uva.nl \
--cc=emacs-orgmode@gnu.org \
--cc=scotto@u.washington.edu \
/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).