What about the output of ``tree``? E.g.::
$ for i in `seq 3`; do for j in `seq 3`; do mkdir -p root/node_$i/
leaf_$j; done; done
$ tree root/
root/
├── node_1
│ ├── leaf_1
│ ├── leaf_2
│ └── leaf_3
├── node_2
│ ├── leaf_1
│ ├── leaf_2
│ └── leaf_3
└── node_3
├── leaf_1
├── leaf_2
└── leaf_3
Cheers!
Felix
On Nov 15, 10:39 pm, Carlos Linares López
<[email protected]> wrote:
> Hi there,
>
> Hope this is the right forum to ask this question, if not, let me know plz
>
> I am a user of Sphinx and I am more than delighted with it. I currently use
> it to generate documentation both in pdf and html. Right now, I'd like to
> describe the contents of a tree structure and my sphinx code looks like:
>
> The repository is organized as follows. First, planners are arranged
> according to the following schema::
>
> planners/
> seq-mco/
> seq-mco-planner-11/
> seq-mco-planner-12/
> ...
>
> seq-opt/
> seq-opt-planner-21/
> seq-opt-planner-22/
> ...
>
> seq-sat/
> seq-sat-planner-31/
> seq-sat-planner-32/
> ...
>
> tempo-sat/
> tempo-sat-planner-41/
> tempo-sat-planner-42/
> ...
>
> which is okay but not as nice as I'd like. Note that I use '::' at the end
> of the first paragraph.
>
> My question is: what would be your recommendation to draw trees like this?
> I already had a look at the available documentation with no luck
>
> Thanks,
--
You received this message because you are subscribed to the Google Groups
"sphinx-dev" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sphinx-dev?hl=en.
