-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create a bash command argument completion file for manage.sh
#78
Comments
Earth talking to Galactica. I hear that Capitan JJ won't do it. I guess admiral JCK is busy next couple of weeks. Shall we assign democratically to lieutenant JMB? |
Get in the habit of @-mentioning people who you want to read the message. In this case mentioning @jmbenlloch would have been a good idea. I suggest that he assign himself, if he feels like taking it on. Otherwise, it can sit there in the list of issues until somebody takes pity on it, or someone thinks it needs to be given a higher priority. It's possibly not of the highest priority at the moment. |
Ay, Ay, sir!
As for JM he is sitting by my side, so he has taken notice! And he is assigning himself to the task. He is indeed pretty busy, but also pretty fast, so no worries.
… On 15 Jan 2017, at 20:08, jacg ***@***.***> wrote:
Get in the habit of @-mentioning people who you want to read the message. In this case mentioning @jmbenlloch <https://github.com/jmbenlloch> would have been a good idea.
I suggest that he assign himself, if he feels like taking it on. Otherwise, it can sit there in the list of issues until somebody takes pity on it, or someone thinks it needs to be given a higher priority. It's possibly not of the highest priority at the moment.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#78 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AHskD1pgPc-slqEX8sXp-iHdJuYPUQ1aks5rSm6ggaJpZM4Lj_uL>.
|
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
First you need to execute the script: . bash_manage.sh Then you it will autocomplete `bash manage.sh` or `source manage.sh` in this way: $ source manage.sh [TAB][TAB] clean install run_tests compile_and_test install_and_check work_in_python_version download_test_db make_environment If you chose an option requiring python version it will offer you 2.7 and 3.5: $ source manage.sh work_in_python_version [TAB][TAB] 2.7 3.5 The only problem is that some bash options are overwrite. For instance, this will happen before executing the script: $ bash --[TAB][TAB] --debug --help --noprofile --restricted --debugger --init-file --norc --verbose --dump-po-strings --login --posix --version --dump-strings --noediting --rcfile This same file can be used by `zsh`: before sourcing `bash_manage.sh`, you first have to instruct `zsh` to understand the `bash` autocomplete instructons with autoload bashcompinit bashcompinit source bash_manage.sh
Our
manage.sh
script is acquiring (#77) a large number of long and inconvenient to type command arguments. It would benefit immensely from completion help from the shell. I get the impression that most of us are usingbash
or some derivative. Let's provide a file which teachesbash
how to completemanage.sh
's arguments for us.How this can be done seems to be described here.
Once made, this file can be sourced to enable the completion. You could do this in your
.bashrc
or similar.The text was updated successfully, but these errors were encountered: