I am running PHPUnit from command line on Windows 7. I tried to enable color output via phpunit --color. But it still display same, no color output. How can I get color output of PHPUnit from command line on Win7?
You will have to use http://softkube.com/blog/ansi-command-line-colors-under-windows or get some sane console like conemu https://code.google.com/p/conemu-maximus5/
Also, I suggest to download git for windows and use bash as your default shell.
Download Git for Windows, run phpunit from the command line in the Bash shell, and you will get colors.
Related
If I'm in my terminal and open a file with the code command, vscode will launch and the terminal inside code will show my full zsh setup that I have configured in hyper terminal. But if I open up code through windows, and select wsl as my default shell, it's pretty much useless. Anything I try, like sudo, git, apt, etc will return a command not found message.
So if I want to commit any changes in the terminal inside code then I have to use the git bash shell. Is it possible to get my zsh working without first launching from my terminal emulator so I'm using wsl instead of git bash?
running wslconfig.exe /list in powershell showed me that WSL was set to docker as the default shell, so then running wslconfig.exe /setdefault "Ubuntu" in powershell fixed my problem.
Whenever I execute cargo run, all colors in the console are displayed as color-codes. Other programs which display colors work normal and show the color.
When I redirect stdout like cargo run > output.txt all colors are shown just fine. This is the same for cmd, powershell and hyper (terminal emulator I use).
cargo 0.20.0 works as expected, but cargo 0.21.1 has the same bug as cargo#0.22.0.
I'm using Windows 10 16299.19. I'm not using the legacy console and I already deleted the Computer\HKEY_CURRENT_USER\Console in the registry to reset the cmd colors.
I then tried it on an other account on my machine and everything worked. A clean install of windows didn't help.
Issue on Github.
The problem was the term environment variable which doesn't work properly with the termcolor crate used by cargo.
I am trying to understand why some of the puppet code do not work as expected. I run the puppet beaker test using "rake beaker" command. I am failing to understand how can I tell netbeans to run this command after I set the break points in the sources. I tried to set the project configuration with the appropriate parameters from following command line which "rake beaker" invokes.
/usr/local/rvm/rubies/ruby-1.9.3-p545/bin/ruby -I
/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-support-3.1.0/lib:
/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/lib
/usr/local/rvm/gems/ruby-1.9.3-p545/gems/rspec-core-3.1.4/exe/rspec spec/acceptance --color
But the debugger simply starts and ends?
Any idea, how can I debug a rake task?
Update:
As per this I can start the rake beaker task using the ruby-debug-ide, however it does not break at the break points I have set. As per the blog I believe I have break points set in the files, which will run using ruby-debug-ide.
By the way I am running Netbeans 8.0.1 on CentOS 6.4
One way I found out is to
Create a Netbeans ruby project
Set the breakpoints wherever needed.
Open the rspec binary file in Netbeans editor window.
Debug rspec file, by pressing Ctrl-Shift-F5
Provide the parameters in the debug dialog as shown in picture below
And you are done
I am trying to redirect Terminal output to Eclipse console using external tools where I specified Terminal path (for example /usr/bin/xterm). When I run this tool it opens Terminal outside eclipse. When I did same thing in Windows 7, setting external tool location to Windows\System32\cmd.exe it ran inside Eclipse console. I wonder how I can make Terminal (in Ubuntu 14.04) work the same way.
You should use /bin/sh as command interpreter.
In Windows, cmd.exe combines two functions—interpreting commands and displaying terminal window. In Unix these functions are strictly separated. /bin/sh interprets commands and /usr/bin/xterm (or /usr/bin/x-terminal-emulator) displays terminal window, inside which it runs /bin/sh (or other shell like /bin/bash, /bin/zsh etc.) to interpret commands.
So if you ask Eclipse to run something via /usr/bin/xterm, it will appear in a new window, because that's what XTerm does. If you just want Eclipse to capture the output, ask it to run it directly via /bin/sh.
I have installed the ShellEd plugin in eclipse. Whenever I run a bash script it runs it using dash even if I specify interpreter directive #! /bin/bash at the top of the script.
How do I change this behavior?
You need to install Cygwin or MSYS/MinGW.
Add the interpreter bash.exe path in eclipse as follows:
Window->Preferences->Shell Script -> Interpreters
THere should be an option to set the bash interpreter as follows:
Window->Preferences-><the_plugin_name>->Interpreter.
you need to set you bash interpreter path here (/bin/bash).
Eclipse will use the value you set here to execute your program.
In new versions of Eclipse current v2.23.0 and beyond the path to change terminal is:
Windows > Preferences > Shell > Local Terminal, under subtitle Show in there is a button labeled Add