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
Currently one can't configure the editor to use when using commands like buildtest config edit to edit configuration file or buildtest buildspec edit <test> or buildtest buildspec edit-file <buildspec>.
By default it will look at value of environment EDITOR if its set it will use it otherwise it will resort to vi. This can be problematic for users that may not have vi or perhaps they don't like their editor.
One option is to allow one to specify editor to use using one of the following method
Environment Variable perhaps BUILDTEST_EDITOR?
Configuration property perhaps editor in buildtest configuration which specify full path to editor for instance editor: /usr/bin/vim
Another option is to specify editor on command line buildtest --editor /usr/bin/vim config edit
In this case the order of preference is following
Command Line
Environment Variable
Configuration File
Let me know your thoughts @Xiangs18@JeffreyFG and whether this would be good approach.
Currently one can't configure the editor to use when using commands like
buildtest config edit
to edit configuration file orbuildtest buildspec edit <test>
orbuildtest buildspec edit-file <buildspec>
.By default it will look at value of environment
EDITOR
if its set it will use it otherwise it will resort tovi
. This can be problematic for users that may not havevi
or perhaps they don't like their editor.One option is to allow one to specify editor to use using one of the following method
BUILDTEST_EDITOR
?editor
in buildtest configuration which specify full path to editor for instanceeditor: /usr/bin/vim
buildtest --editor /usr/bin/vim config edit
In this case the order of preference is following
Let me know your thoughts @Xiangs18 @JeffreyFG and whether this would be good approach.
This will impact the following files
The text was updated successfully, but these errors were encountered: