blob: 64d5a83b2799b9e6b6a941d959fa4d33063fcf9e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
|
If you want to use the pruned tree out of broot (for example for a documentation), you may use the `:print_tree` verb.
It can be used in several ways.
The easiest is to execute it from inside the application (the verb is also accessible with the `:pt` shortcut). This quits broot and you find the tree on your console, without the status line and the input, but with the same filtering state as when you were browsing.
Example with a filter:
Example without style or color, thanks to `--no-style`:
This is also how would look the tree directly exported into a file.
With the `--out` command, the tree is written in a given file. For example `br --out test.txt`.
You can also redirect the output of broot in a standard unix way.
You don't have to enter broot, you may also directly get the tree by using the [`--cmd` argument](../launch/#the-cmd-launch-argument). An additional parameter may come handy: `--height` which specifies the size of the virtual screen, which may be smaller or bigger than the real one (no problem if you want 10000 lines).
For example
broot --cmd ":pt" --no-style > my_file.txt
will export the local tree to the `my_file.txt` file.
Or
broot --no-style > tree.txt
in which case you'll manually do `:pt` when in broot but after having had the opportunity to navigate, filter and change toggles as desired.
|
