You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/en/build-script-runner-interactive.md
+3-1Lines changed: 3 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,8 @@
1
1
2
2
3
-
When executing flubu script or any other process locally in console it is recomended to run FlubuCore in interactive mode it gives you some really nice features which are listed in the [features section.](#features) To start FlubuCore interactive mode just execute command `flubu -i` in your favorite console.
3
+
When executing flubu script or any other process locally in console it is recomended to run FlubuCore in interactive mode it gives you some really nice features which are listed in the [features section.](#features) To start FlubuCore interactive mode just execute command `flubu -i` in your favorite console.
4
+
5
+
> **Tip:** If you prefer standard terminal usage over interactive mode, FlubuCore also supports [shell tab completion](build-script-runner.md#shell-tab-completion) for bash, zsh, PowerShell, and fish.
4
6
5
7
## **Demo**
6
8

Copy file name to clipboardExpand all lines: docs/en/build-script-runner.md
+39Lines changed: 39 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -50,6 +50,45 @@ It displays all tasks with description that will be executed by target. It also
50
50
that you don't need to execute script at the root directory of the project. Meaning if your project is for example located at "c:\_git\myproject" you can execute script inside any subfolder of that location. The location where a
51
51
.flubu file is found will be used as the "work directory" during a build process, and a correct "work directory" is crucial to use relative paths in our build scripts.
52
52
53
+
### **Shell tab completion**
54
+
55
+
FlubuCore supports shell tab completion for target names, options, and script arguments. Once set up, you can type `flubu <tab>` and get completions directly in your terminal — no need to run `flubu help` or switch to interactive mode.
|`flubu <tab>`| All target names from your build script |
86
+
|`flubu cl<tab>`| Targets starting with "cl" (e.g. `clean`) |
87
+
|`flubu --<tab>`| Options: `--parallel`, `--dryRun`, `--noColor`, `--nodeps`, `--script`, etc. |
88
+
|`flubu -<tab>`| Script arguments defined with `[FromArg]` attributes |
89
+
90
+
Completions are dynamic — targets are discovered from your build script on each tab press. When you add a new target and save the file, it appears in completions immediately.
Copy file name to clipboardExpand all lines: docs/en/getting-started.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -69,6 +69,7 @@ project.json:
69
69
- .net core sdk 2.1.300 or greater must be installed.
70
70
- Install FlubuCore local or global tool: `dotnet tool install --global FlubuCore.Tool`
71
71
- Run `flubu compile` where build script is located. It will compile your solution.
72
+
- Optionally enable [shell tab completion](build-script-runner.md#shell-tab-completion) for target and option completions in your terminal.
72
73
73
74
This is very basic build script just for you to see how simple it is to get you started. FlubuCore has to offer a lot of nice features. Read more about them at [Build script fundamentals].
74
75
You should also take a look at [.net core examples] they will give you hints how to write your build script and see most of the main flubu features in action.
* [FlubuCoreinteractivemode](https://flubucore.dotnetcore.xyz/build-script-runner-interactive/) which offers target tab completition, options tab completition, toogle targets/options, executed commands history. It is also possible to execute external commands and operable programs. For some of them FlubuCore offers tab completion with help displayed at the bottom of console out of the box(such as dotnet, git..)
189
+
* [FlubuCoreinteractivemode](https://flubucore.dotnetcore.xyz/build-script-runner-interactive/) which offers target tab completition, options tab completition, toogle targets/options, executed commands history. It is also possible to execute external commands and operable programs. For some of them FlubuCore offers tab completion with help displayed at the bottom of console out of the box(such as dotnet, git..)
* [Shelltabcompletion](https://flubucore.dotnetcore.xyz/build-script-runner/#shell-tab-completion) for bash, zsh, PowerShell, and fish. Get target and option completions directly in your terminal without entering interactive mode.
0 commit comments