Shell - Some commands were not successfully executed
See original GitHub issueI am receiving Some commands were not successfully executed message with this below config 😃
This is my install.conf.yaml
file. I am on Windows 10 with Dotbot 1.12.5:
- defaults:
link:
force: true
create: true
relink: true
- clean: ['~']
- link:
~/.gitconfig: git/gitconfig
~/.gitignore_global: git/gitignore_global
~/.minttyrc: mintty/minttyrc
~/.npmrc: npm/npmrc
~/.vim: vim/vim
~/.vimrc: vim/vimrc
- shell:
- vim +PluginInstall +qall
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
How to conditionally do something if a command succeeded ...
if command succeeds, then echo "OK" is executed, and since it's successful, execution stops there. Otherwise, && is skipped, and echo "NOK" ...
Read more >execution of command did not complete suc-cessfully with exit ...
When executing a shell script using a command task in the PowerCenter, command task fails with the following error in the workflow log:...
Read more >shell script execution successful but output has errors, how to ...
The easiest way is to append || exit 1 to the statement which is throwing the error. That will ...
Read more >Check if Command Executed Successfully in Linux - Baeldung
In this tutorial, we'll discuss how to check if a command was executed successfully or not in Linux.
Read more >How to check if a command succeeded? - Ask Ubuntu
So cd /nonexistant && echo success! would not echo success because ... ( 0 on success ); however, some commands don't return a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Nice, glad you got it working!
@anishathalye solved through running Git CMD with administritive privilage instead of Git Bash.