Dear list,
When I have a table like
| $ | | rho=33 |
|---+---+|
| # | 3 | 99 |
#+TBLFM: $3=$rho*$2
it works ok.
But as soon as I replace
rho -> \rho
to get a nice greek letter
(I also use #+STARTUP: entitiespretty),
I get
| $ | | \rho=33 |
|---+---+|
| # | 3 |
Hello,
Jens Lechtenboerger writes:
> for HTML export, attributes are added to links with what is called a
> “HACK” in a comment in ox-html.el: Attribute :attr_html is read from
> the parent, to be transferred to the first link.
>
> That mechanism can used to assign attributes to the first link
On 2018-12-08 at 09:47 -0800, Leo Gaspard wrote:
> However, I think it may be a good idea to allow eg. this kind of
> timestamps:
> <2018-02-04 Tue evening> That would be handled as though it
> was eg. <2018-02-04 Tue 18:00-22:00> (which would be configurable), so
> that it would be
Hello,
In the process of migrating all my self-organization to org-mode, I
noticed there is something that cannot currently be encoded in
timestamps: fuzzy times, where an appointment is made for “Dec 4, Tue,
evening” but with the hours not yet fixed.
Currently my way of handling this has been
Hi there,
for HTML export, attributes are added to links with what is called a
“HACK” in a comment in ox-html.el: Attribute :attr_html is read from
the parent, to be transferred to the first link.
That mechanism can used to assign attributes to the first link in
each paragraph/sentence. For
Hello!
On 2018-12-08, at 12:46, Nicolas Goaziou wrote:
> Jens Lechtenboerger writes:
>
>> Function org-reveal-headline calls org-html-headline to generate
>> h-elements. Of course, I could parse the generated HTML in
>> ox-reveal and add a class attribute based on org properties, but
>> doing
On Saturday, 8 Dec 2018 at 10:56, Nicolas Goaziou wrote:
> I'm nowhere close to being a LaTeX expert. If depending on xcolor is not
> too invasive, I'd rather do it than introduce yet another customization
> option.
>
> Maybe real LaTeX experts could chime in.
Whether expert or not, I can say
Hello,
Jens Lechtenboerger writes:
> Function org-reveal-headline calls org-html-headline to generate
> h-elements. Of course, I could parse the generated HTML in
> ox-reveal and add a class attribute based on org properties, but
> doing so in ox-html seems much cleaner to me. (Besides, given
Hello,
Allen Li writes:
> There's an escaping bug in Org capture:
>
> 1. emacs -Q
> 2. Evaluate:
>
> (setq org-capture-templates
>'(("Z" "org-protocol capture" entry
> (file "/tmp/tmp")
> "* %?
> %(let ((x \"%:annotation\")) (if (string= x \"\") \"\" (concat x
> \"\\n\")))%i")))
Hello,
Carlos Pita writes:
>> Would you want to provide a patch for that?
>
> Yes, sure, just give me a few days since I'm quite busy right know.
>
> Are you ok with depending on xcolor by default or do you prefer a
> customization option?
I'm nowhere close to being a LaTeX expert. If
Hello,
Allen Li writes:
> Attached patch fixing this.
>
> This was caused by a bug in a feature that I did not realize existed
> (prefixing each line in %i). I have also included patches to clarify
> the documentation.
Thank you.
However, with the documentation patch, along with your past
Hello,
Kaushal Modi writes:
> Here is a MWE:
>
> 1. With point on the "** Foo" section, running C-c C-e C-s h o, will
> result in noweb-duplicate-bug.html with the <> block
> expanded only once, as expected.
>
> 2. But with point on the "* Foo Included" section, running the same
> C-c C-e C-s h
12 matches
Mail list logo
