Karl Voit devn...@karl-voit.at writes:
* Karl Voit devn...@karl-voit.at wrote:
I would be happy to document this method and provide it on Worg. In
my opinion, this would be very handy for many Org-mode users.
I summarized the method on Worg[1].
Can someone please proof read the page? I am
* Karl Voit devn...@karl-voit.at wrote:
I would be happy to document this method and provide it on Worg. In
my opinion, this would be very handy for many Org-mode users.
I summarized the method on Worg[1].
Can someone please proof read the page? I am not a native speaker
and it's always good
Karl Voit devn...@karl-voit.at writes:
* Karl Voit devn...@karl-voit.at wrote:
I would be happy to document this method and provide it on Worg. In
my opinion, this would be very handy for many Org-mode users.
I summarized the method on Worg[1].
Can someone please proof read the page? I am
* Rick Frankel r...@rickster.com wrote:
The solution is to specify the range on the call:
#+call:
graph-from-table(nodes=example-node-table[2:-1],graph=example-graph[2:-1])
[...]
Thank you *very* much for your explanations! You helped me to
understand the method that good that I will soon
* Rick Frankel r...@rickster.com wrote:
And here's a simplier version which uses a graph table in the
following format:
[...]
I tried to use your solution with the #+call: method.
Unfortunately, it fails and due to my limited ELISP knowledge, I can
not debug this issue. I've got the feeling
On 2013-06-28 05:20, Karl Voit wrote:
* Rick Frankel r...@rickster.com wrote:
And here's a simplier version which uses a graph table in the
following format:
[...]
I tried to use your solution with the #+call: method.
Unfortunately, it fails and due to my limited ELISP knowledge, I can
not
* Thorsten Jolitz tjol...@gmail.com wrote:
not really an answer to your question, but I wrote a library
(picodoc.el) that automatically generates PlantUML scripts from PicoLisp
source code:
Thanks for the pointer. Looks interesting but as you wrote, not
really the solution that seems
* Rick Frankel r...@rickster.com wrote:
On 2013-06-26 13:03, Karl Voit wrote:
* Rick Frankel r...@rickster.com wrote:
However, the header information seems to get lost. This requires
hard-coded column content which is a minor drawback of this method.
Just use `:colnames no':
I love
* Eric S Fraga e.fr...@ucl.ac.uk wrote:
Hi Karl,
Hi Eric!
I did something simple for generating graphs but without an adjacency
type of matrix as you have defined and without the special types of
edges. So, quite limited with respect to what you want. In any case,
I've attached what I
On Thu, Jun 27, 2013 at 08:47:14AM +0200, Karl Voit wrote:
* Rick Frankel r...@rickster.com wrote:
- It requires you to specify the range on the node table
Sorry, I did not understand this since I could not locate any range
specification below except that one for
Rick Frankel r...@rickster.com writes:
Where should I place this method? Org-tutorials? [1] probably? New
section in [2]?
1. http://orgmode.org/worg/org-tutorials/#sec-3-2
2. http://orgmode.org/worg/org-tutorials/#sec-4
I'm not sure. Carsten or Bastien would be a better person to ask.
Hi!
I was looking for a reasonable simple method to define processes and
work-flows within Org-mode. My research did not result in anything
existing I found useful. Therefore, I started to read about dot[1]
and found [2].
I would like to define my diagram with the following two tables: one
for
Sorry, minor mistake: I could not find out why dot is not able to
mix directed and not directed graphs in one diagram. Therefore I had
to replace th - in the node table with and the corresponding
results as well:
#+name: foobar-node-table
| *node* | *label*| *shape* |
On 2013-06-26 11:23, Karl Voit wrote:
Hi!
I would like to define my diagram with the following two tables: one
for the node definitions and one for the interconnections between
notes. The syntax should be pretty self-explanatory (or at least I
hope so):
I (not an ELISP hacker) would have to use
Karl Voit devn...@karl-voit.at writes:
Hi,
I was looking for a reasonable simple method to define processes and
work-flows within Org-mode. My research did not result in anything
existing I found useful. Therefore, I started to read about dot[1]
and found [2].
[...]
Some (still missing)
* Rick Frankel r...@rickster.com wrote:
Two things:
1. You don't need to write table parsing code, as passing in a
table as an argument to a code block will convert it to an
array.
#+name: ptable
| head1 | head2 |
|---+---|
| a | 1 |
| b
Hi Karl,
Karl Voit devn...@karl-voit.at writes:
I was looking for a reasonable simple method to define processes and
work-flows within Org-mode. My research did not result in anything
existing I found useful. Therefore, I started to read about dot[1]
and found [2].
I would like to define my
On 2013-06-26 13:03, Karl Voit wrote:
* Rick Frankel r...@rickster.com wrote:
Two things:
1. You don't need to write table parsing code, as passing in a
table as an argument to a code block will convert it to an
array.
t=[[a, 1], [b, 2]]
You're
18 matches
Mail list logo
