Christian Moe m...@christianmoe.com writes:
- You can simplify repeated use with macros. See the manual, section
11.6. Use the @ notation (section 12.5.3) for literal html tags within
the macros. E.g.:
#+MACRO: mycolor @span style=color: black; background-color:
#f4a460$1@/span
Hi Christian,
Thanks for your thoughtful comments. I have a better understanding of
it now. Here is more as a sort of summary for searchers.
On 2012-04-11, Christian Moe m...@christianmoe.com wrote:
Are those two separate questions, perhaps? I tried with
org-export-as-region, and I still got
Hi again,
On 4/11/12 1:53 AM, Samuel Wales wrote:
Will CSS solutions described in this thread work if you always export
subtrees (not entire .org files) and never include style files?
Yes, CSS styles apply to exported subtrees as well, whether from the
default stylesheet, linked external
Hi Christian,
Thanks for your reply.
I left implicit the question of whether this can solve OP's problem
also, but believe it is potentially related.
However, if I understood CSS well enough to ask the question
precisely, I'd have the answer. So bear with me.
More below:
On 2012-04-07,
Hi, Samuel,
On 4/6/12 8:41 PM, Samuel Wales wrote:
Christian and others,
Will CSS solutions described in this thread work if you always export
subtrees (not entire .org files) and never include style files?
Yes, CSS styles apply to exported subtrees as well, whether from the
default
Hi,
On 4/5/12 5:02 PM, François Pinard wrote:
I understand what you mean by saying it does not make sense with the
current mechanics. Yet, from a user perspective, it surely makes sense
hoping that Org offers a way for adding attributes to either part of a
link, as links are kind of
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
I understand what you mean by saying it does not make sense with the
current mechanics. Yet, from a user perspective, it surely makes sense
hoping that Org offers a way for adding attributes to either part of a
link, as links
Christian and others,
Will CSS solutions described in this thread work if you always export
subtrees (not entire .org files) and never include style files?
If so, how do you go about using them in Org? Is there a less awkward
way than using an HTML block with a div with style=?
This is awkward
On 2012-04-06, Samuel Wales samolog...@gmail.com wrote:
It would be great to have a generic style of some sort, specify the
scoped Org elements with neat syntax (maybe like #+myblock_begin:)
Oops, if we did it this way it would be like #+begin_mycolor ...
#+end_mycolor of course.
But again,
Bastien b...@gnu.org writes:
then I get the display I wanted. Is there a way for having #+ATTR_HTML
to be applied to the inner tag instead of the outer one?
Not -- it would not make sense.
Hello, Bastien.
I understand what you mean by saying it does not make sense with the
current
On 2012-04-02, Bastien b...@gnu.org wrote:
I mean a better description of all possible properties for any
syntactic element. It should be clear by just skimming through
the link above.
Makes sense.
Good to know. We will try to keep things as backward compatible as
possible. There is no
Hi François,
pin...@iro.umontreal.ca (François Pinard) writes:
then I get the display I wanted. Is there a way for having #+ATTR_HTML
to be applied to the inner tag instead of the outer one?
Not -- it would not make sense.
I suggest you fix your css instead.
Best,
--
Bastien
François's problem is probably best fixed with CSS as you suggest.
But it might be nice to be able to set an ALT attribute on an image
used as a link. That doesn't look like it's currently possible with
Org link syntax and ATTR_HTML.
Just pointing it out, not making a feature request --
Hi Christian,
Christian Moe m...@christianmoe.com writes:
François's problem is probably best fixed with CSS as you suggest.
But it might be nice to be able to set an ALT attribute on an image used as
a link. That doesn't look like it's currently possible with Org link syntax
and ATTR_HTML.
On 2012-04-02, Bastien b...@gnu.org wrote:
Agreed -- this is where Nicolas' new export engine will help,
with a more comprehensive syntax for each element.
Is there a description of this part someplace? Do you mean new syntax
or better semantics for existing syntax?
While the new exporter has
Hi Samuel,
Samuel Wales samolog...@gmail.com writes:
On 2012-04-02, Bastien b...@gnu.org wrote:
Agreed -- this is where Nicolas' new export engine will help,
with a more comprehensive syntax for each element.
Is there a description of this part someplace?
The reference document for the
16 matches
Mail list logo
