turbo-editors/turbo-golopublic Fork 0
main
Commits
Clone
git clone https://git.rickub.com/turbo-editors/turbo-golo.git
git clone ssh://git@rickub.com/turbo-editors/turbo-golo.git

Host key fingerprint (ed25519): SHA256:iycHnxEyq0Q7uyVpB7JlznP0G7JrTPXLYRcAU5CSLhc — verify it before your first connect.

browse-a-project.md · 73 lines · 3.6 KBmarkdown Blame HistoryRaw
📦 Turbo Golo d710c1b k33g 12h ago1# How to browse a project and open files from a tree
2
3This guide shows how to open the project tree, walk it, and open a file from it. It assumes Turbo Golo is already installed.
4
5## Open the tree
6
7Start the editor **from the project's own directory**, then press `F9`, or choose **Window ▸ Project tree**.
8
9A window opens showing the project's files, named after the directory the editor was started in:
10
11```
12╔═[x]═══════════ turbo-golo ═══════════2═[■]╗
13║ ▶ .turbo-golo ║
14║ ▼ demos ║
15║ ▶ hello ║
16║ ▼ shapes ║
17║ shapes.golo ║
18║ shapes_test.golo ║
19║ ▶ syntax-tour ║
20║ ▶ internal ║
21║ .gitignore ║
22║ Makefile ║
23║ main.go ║
24╚═══════════════════════════════════════════╝
25```
26
27Directories come first, then files, each group sorted. `.git` is the only thing hidden — `.turbo-golo`, `.gitignore` and the rest are files of your project, and you may well want to open them.
28
29Pressing `F9` again brings that window forward rather than opening a second tree.
30
31## Walk it
32
33| Key | Effect |
34| --- | --- |
35| `↑` `↓` | Move the highlight |
36| `→` | Open a closed directory; on anything else, step to the next row |
37| `←` | Close an open directory; on anything else, step out to the directory it is in |
38| `Enter` | Open a file, or open and close a directory |
39| `Home` `End` | First / last row |
40| `PgUp` `PgDn` | A screenful at a time |
41
42A directory is read the first time you open it, so a tree on a large project costs one listing rather than a walk of everything.
43
44## Open a file
45
46Put the highlight on it and press `Enter`, or click it twice.
47
48The file opens in a window of its own, in front of the tree. A file that is already open is brought forward rather than opened twice.
49
50## See a file that was made after you opened the tree
51
52The tree does not watch the disk. Press **`F5`** or **`Ctrl-R`** with the tree focused, and it re-reads the project — keeping open whatever you had open, and keeping the highlight on the same entry.
53
54Saving a file refreshes the tree for you, so a **File ▸ Save as** into a new name shows up without asking. A file created another way — `golo new main` or `gogolo build` in a terminal window, or `git checkout` — needs the refresh key.
55
56## Work with the tree and a file side by side
57
58The tree is an ordinary window, so all the window commands apply:
59
60- **Window ▸ Tile** puts the tree and your file side by side.
61- Drag its bottom-right corner to make it narrower once you know your way around.
62- `[x]` closes it; `F9` brings it back.
63
64## Variants
65
66- **You started the editor from a subdirectory.** The tree is rooted there, showing only that part of the project. Start from the project's own directory instead — the same rule `.turbo-golo/settings.toml` follows.
67- **A directory shows as open but empty.** It could not be read, most often a permissions problem. The rest of the tree is unaffected; fix the permissions and press `F5`.
68
69## See also
70
71- Every key and what the tree shows, exactly: [Project tree reference](../reference/project-tree.md)
72- Why it is a window rather than a docked panel, and why it does not watch the disk: [Project tree](../explanation/project-tree.md)
73- Colouring it: [Theme file format](../reference/themes.md)