From bbd16915c318327e7588759a513238399c711d65 Mon Sep 17 00:00:00 2001
From: Nikolaos Kakouros <nkak@kth.se>
Date: Sat, 30 Jan 2021 00:05:51 +0100
Subject: [PATCH] wip
---
commands/core.d/bootstrap | 1 +
lib/system | 2 +-
2 files changed, 2 insertions(+), 1 deletion(-)
diff --git a/commands/core.d/bootstrap b/commands/core.d/bootstrap
index 87fb50e..d87393e 100755
--- a/commands/core.d/bootstrap
+++ b/commands/core.d/bootstrap
@@ -205,6 +205,7 @@ function core_bootstrap() {
core_bootstrap_configure
fi
+ core_parse_project_config
core_bootstrap_git_collab
core_bootstrap_git_hooks
core_bootstrap_git_branches
diff --git a/lib/system b/lib/system
index c224db1..3582739 100755
--- a/lib/system
+++ b/lib/system
@@ -39,7 +39,7 @@ trap system_load_outro EXIT
## doing TAB auto-completion in Bash. Then, the
## '$_HEADSTART_VENDOR_DIR/go-bash-script/libexec/complete' functions are called in an
## execution sequence that includes 4, 5 commands that return 1 when there is no
-## candidate for completion (eg 'headstart world f<TAB>') . This causes Bash
+## candidate for completion (eg 'headstart build f<TAB>') . This causes Bash
## Infinity to trigger exception handling and print execution stacks in the
## command line. Instead, nothing should be printed to the user. One solution
## would be to patch go-script-bash's auto-completion to not return 1 if there is
--
GitLab