Hello,
Daniele Pizzolli writes:
> Please have a look at the following ECM:
>
> * test table with time constant (not working)
>:PROPERTIES:
>:time_constant: 08:00:00
>:END:
>
> | month | days | time |
> |---+--+--|
> |01 |1 | |
> |02 |3 | |
> #+TB
Eric S Fraga wrote:
> On Friday, 8 May 2015 at 15:22, Leo Ufimtsev wrote:
>> I use org-babel to make graphviz diagrams in my notes.
>>
>> I open resulting images in the side panel via C-u C-c C-o (or right-click
>> image).
>> (See 20 screen shot)
>>
>> Now it shows the image fine at first.
>>
>>
Oh, I forgot to turn on org-use-property-inheritance. Now it works in the
included subtree as well. Thank you so much!From: joon...@outlook.com
To: m...@nicolasgoaziou.fr
CC: emacs-orgmode@gnu.org
Subject: RE: Subtree-specific variables
Date: Sun, 10 May 2015 12:01:23 -0500
> * Subtree root
>
> * Subtree root
> > :PROPERTIES:
> > :EXPORT_Variable: Test> > :END:
> > {{{Variable}}}
> > Would something like this be possible?
> > Best,Joon
>
> It is:
>
> {{{property(EXPORT_Variable)}}}
>
Thank you so much! This will be very useful.
One related question - I'm including another subtr
On Sun, May 10, 2015 at 7:08 PM, Marcin Borkowski wrote:
>
> I looked through org-drill docs and didn't find anything like that.
> Maybe someone did it for themselves already? If not, I'll be happy to
> code it. I assume that writing a suitable function in Elisp is
> a question of 15 minutes at
Hi all,
I'm about to start using org-drill. I find, however, one feature
lacking. In the old days of SuperMemo 7 (the Windows 3 version, which
IMHO had the best UI in the history of SM), items could be marked with
a special (customizable) string so that SM asked the user to /type in/
the answer,
On Friday, 8 May 2015 at 15:22, Leo Ufimtsev wrote:
> Hello,
>
> I use org-babel to make graphviz diagrams in my notes.
>
> I open resulting images in the side panel via C-u C-c C-o (or right-click
> image).
> (See 20 screen shot)
>
> Now it shows the image fine at first.
>
> Then I run org-babe
On Sunday 10 May 2015 12:44 PM, Nicolas Goaziou wrote:
> It will land in the trunk once a library using it for Org core is
> implemented. I put it in a separate branch so that such a library can be
> built, discussed and tested.
1. Do you, as a maintainer, have any specific plans for this library
Hello,
Keith David Bershatsky writes:
> I had a little free time today and was finally able to track down the
> invalid face reference when generating an org-agenda buffer. It is
> caused because the `car` of the `cons` cell created by
> `org-agenda-fontify-properties` is sometimes `nil`. I thre
Hello,
Vaidheeswaran C writes:
> New citation syntax, is it in the trunk yet?.
No, it isn't.
> If "No", under what conditions will it land in the trunk.
At the moment it is a minimal syntax, i.e., it doesn't support
sub-types.
It will land in the trunk once a library using it for Org core is
Joon Ro writes:
> Thank you for the reply. I'm aware of EXPORT_ stuff, but I'm actually looking
> for something like this:
> * Subtree root
> :PROPERTIES:
> :EXPORT_Variable: Test:END:
> {{{Variable}}}
> Would something like this be possible?
> Best,Joon
It is:
{{{property(EXPORT_Variable)}
New citation syntax, is it in the trunk yet?.
If "No", under what conditions will it land in the trunk.
I am thinking of stashing away my ox-jabref.el in to GNU ELPA. If the
citation syntax is only an EXPERIMENTAL feature with no certainty
about it's mainstream availability or maturity, then my
12 matches
Mail list logo
