From: Robert Klein <roklein@roklein.de>
To: Nicolas Goaziou <n.goaziou@gmail.com>, Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: another blog exporter
Date: Tue, 04 Mar 2014 10:51:36 +0100 [thread overview]
Message-ID: <5315A228.1040105@roklein.de> (raw)
In-Reply-To: <87ha87mch5.fsf@gmail.com>
Hello,
thank you very much for your feedback.
On 02/10/2014 12:30 PM, Nicolas Goaziou wrote:
> Hello,
>
> Bastien <bzg@gnu.org> writes:
>
>> Somehow this calls for a way to let a backend use several affiliated
>> keywords. For example you would have:
>>
>> #+ATTR_HTML: :width 400px
>> #+ATTR_BLOG: :lineno t
>
> Org already provided a syntax to number lines in source blocks. Couldn't
> it be used instead?
>
> #+begin_src emacs-lisp -n
> ...
> #+end_src
>
Thanks a lot, I didn't know about this feature. Now I use the -n/+n
flags. When using -n flag the ATTR_BLOG attribute :firstline is used as
the first line number; the default is 1 as in the LaTeX exporter.
>> and the exporter would take both into account, letting you to simply
>> export to HTML without the need to add redundant information.
>>
>> Nicolas, did this cross your mind? Or maybe this is already feasible?
>
> This is already feasible. See `org-beamer-plain-list' for an example.
> Both #+attr_latex and #+attr_beamer are read but the latter has
> precedence over the former.
I already use this, but I felt a need to document those attributes that
get extra treatment: wordpress uses class="alignleft" instead of HTML
align="right" and I changed the style handling to support surrounding
double quotes ( :style "margin: 9pt; background: red;" )
Best regards
Robert
prev parent reply other threads:[~2014-03-04 9:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 17:10 another blog exporter Robert Klein
2014-02-07 17:35 ` Rasmus
2014-02-07 19:17 ` Robert Klein
2014-02-08 0:27 ` Ken Mankoff
2014-02-08 8:40 ` Robert Klein
2014-02-08 20:41 ` Robert Klein
2014-02-09 7:55 ` Bastien
2014-02-09 14:25 ` Robert Klein
2014-02-10 8:48 ` Bastien
2014-02-10 11:30 ` Nicolas Goaziou
2014-03-04 9:51 ` Robert Klein [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=5315A228.1040105@roklein.de \
--to=roklein@roklein.de \
--cc=bzg@gnu.org \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@gmail.com \
/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).