diff options
| author | Angelos Evripiotis <jevripiotis@bloomberg.net> | 2019-02-05 15:26:58 +0000 |
|---|---|---|
| committer | Angelos Evripiotis <angelos.evripiotis@gmail.com> | 2019-02-15 13:56:48 +0000 |
| commit | c24f2971db15c8ef23fb569f9ee204ade643ec14 (patch) | |
| tree | 8f166ae80ebb2ad6280dd54b47ddcb5d6f75f656 /buildstream/data/userconfig.yaml | |
| parent | 0921ccf40f167ed524a1a2ff7023949f2542e14f (diff) | |
| download | buildstream-c24f2971db15c8ef23fb569f9ee204ade643ec14.tar.gz | |
userconfig: rm really-workspace-close-project-inaccessibleare_you_sure2
Remove the need for the 'really-workspace-close-project-inaccessible'
config option, as well as the option itself.
As agreed on the mailing list [1], all the 'are you sure?' prompts on
workspace reset and close were removed. While that discussion was going
on, this new prompt and option was added. At the 2019 BuildStream
Gathering, it was verbally agreed between myself and Tristan VB that we
would also remove this instance.
It was also agreed that we should have a notice to let the user know
what they'd done, this was already in place if interactive. Moved it to
be unconditional so that there's no difference in non-interactive
behaviour. Made it output to stderr, as it's diagnostic meant for the
user. Made it the last thing echo'd so it's next to the prompt - it's
very relevant to what they type next. Added a test to make sure the text
makes it to stderr in the appropriate case, and not in an inappropriate
one.
This is the last instance of any prompt configuration, so BuildStream
can also forget all of that machinery.
[1] https://mail.gnome.org/archives/buildstream-list/2018-December/msg00111.html
Diffstat (limited to 'buildstream/data/userconfig.yaml')
| -rw-r--r-- | buildstream/data/userconfig.yaml | 17 |
1 files changed, 0 insertions, 17 deletions
diff --git a/buildstream/data/userconfig.yaml b/buildstream/data/userconfig.yaml index 0b4535cea..f17dac88c 100644 --- a/buildstream/data/userconfig.yaml +++ b/buildstream/data/userconfig.yaml @@ -111,20 +111,3 @@ logging: message-format: | [%{elapsed}][%{key}][%{element}] %{action} %{message} - -# -# Prompt overrides -# -# Here you can suppress 'are you sure?' and other kinds of prompts by supplying -# override values. Note that e.g. 'yes' and 'no' have the same meaning here as -# they do in the actual cli prompt. -# -prompt: - - # Whether to really proceed with 'bst workspace close' when doing so would - # stop them from running bst commands in this workspace. - # - # ask - Ask the user if they are sure. - # yes - Always close, without asking. - # - really-workspace-close-project-inaccessible: ask |