I am trying to launch my Vagrant directly from Phpstorm 6 but I am not able to find the command (Windows).
Screenshot : http://i.stack.imgur.com/d8aUA.png
Is there anything I could do to make it works ?
Thanks!
Have you created an alias for vagrant in "Settings | Command Line Tool Support" ?
Command Line Support Tool does not know what vagrant is, so it tries to execute whole command as is. The problem is -- proper name of app should be vagrant.bat (or vagrant.cmd -- do not remember) -- IDE does not add .bat/.exe/etc automatically like DOS/Windows does.
So either use vagrant.bat up command instead .. or (which is better) create an alias.
P.S.
PhpStorm v7 will search for .bat/.cmd/.exe/etc in your PATH if exact command cannot be found. Still -- making an alias is the best/safest way to go here in Command Line Tools.
An excerpt from: https://www.jetbrains.com/phpstorm/webhelp/vagrant.html
Make sure that the parent folders of the following executable files
are added to the system PATH variable:
vagrant.bat or vagrant from your Vagrant installation. This should be done automatically by the Vagrant installer.
If you've installed Vagrant the standard way then just restart the command prompt itself or phpStorm so it reloads the PATH. Else just find that bat file and run it manually to see if it works or better add the path to the system PATH var.
Related
I get this error:
code . is not recognised as an external or internal command, operable program or batch file
moreover shell commands are not coming in my compiler VS code neither do setx path "%path%;C:\Program Files\Microsoft VS Code" is working in command prompt .
It looks as if you do not have the code program installed. You can open the Command Palette,
Mac: ShiftCmdP
Windows/Linux: ShiftCtrlP
And search "install command", which should return this as one of the options:
Shell Command: Install 'code' command in PATH
Run that, and it should install the code command, after which you should be able to use it.
For Mac OS,
You can paste this into your terminal, or in your .bashrc file (or whatever shell config file you are using) :
export PATH="$PATH:/Applications/Visual Studio Code.app/Contents/Resources/app/bin"
I found it. In the "search" type environment variables then click on the "edit system environment variables".
Inside Environment variables->Path put C:\Users\{your_username}\AppData\Local\Programs\Microsoft VS Code\bin.
Go to the project folder and open the cmd with it typing in the location bar and then type code .
That will do.
in windows problem is with insiders version of VSC.
You can use 'code-insiders .' command or make a copy of 'code-insiders.cmd' file as 'code.cmd' inside folder with code-insider (use 'path' command to see where your VSC is installed)
make sure you run the command in C folder
Then click window key + R and type rundll32.exe sysdm.cpl,EditEnvironmentVariables
then enter .
It will open Environment Variables edit Path variable .
Check whether you have C:\Users\{pc name}\AppData\Local\Programs\Microsoft VS Code\bin if not add it and run code -v in C folder cmd
This worked for me !
For Windows OS
For Windows, you'll need to re-install code. You can download the latest version and just install it overtop of your existing install.
During setup, make sure to check the box to Add to PATH
See Also: The VSCode docs on installing the CLI
After installation, you need to restart your computer to make the PATH changes effective. Post restart, the command worked for me.
about linux, if u can't see the >shell option with ctrl+shif+p, You could install via
sudo snap install --classic code
and try again
code .
I'm not sure how to open Gnuplot from MobaXterm. I've been trying many different commands but they all don't work. When I try, I get the same error.
-bash: gnuplot: command not found
I'm curious if I downloaded Gnuplot to the wrong part of the computer or if I'm not getting the command right? I'm trying to write a program in shell script that opens Gnuplot on it's own and plots data through the shell script.
Any help is appreciated!
mobaxterm is not a linux server. So you cant install packages into it normally.
you must download plugins if you can find the plugin you are looking for
check their list here
http://mobaxterm.mobatek.net/plugins.html
and it seems gnuplot is not there .
in this case your easiest solution is to download cygwin and add gnuplot on it which is possible
other option is to run small virtual machine so you can test on it
in all cases mobaxterm is not real linux enviroment so to be sure your shel do work on normal linux machines you will need to develop and test on real linux
You can install the winbuild of gnuplot and add the path to the bin directory, with gnuplot.exe in it, to mobaxterm's PATH (probably set it in .initrc or .bashrc, whichever you prefer).
MobaXterm is a standalone program which 'emulates' a Linux terminal but has no idea about your frame system (e.g. your Windows and your programs). So if you type 'gnuplot' Moba has no idea what is this. You have to
change the current directory to where is wgnuplot.exe e.g.:
cd /drives/c/Program\ Files/gnuplot-4/bin
./wgnuplot.exe
or run directly it:
/drives/c/Program\ Files/gnuplot-4/bin/wgnuplot.exe
or change your $PATH:
PATH=$PATH:/drives/c/Program\ Files/gnuplot-4/bin
wgnuplot.exe
or create a script named 'gnuplot' which runs wgnuplot.exe
#File name: 'gnuplot'
#!/bin/sh
/drives/c/Program\ Files/gnuplot-4/bin/wgnuplot.exe
and place it into some $PATH directory:
`/bin` or `/usr/bin` or `/drives/c/WINDOWS` or `/drives/c/WINDOWS/system32`
or... :)
The simplest way I found out is to use the Moba Package Manager to install the win version of gnuplot.
Open MobaXterm and type MobApt. An GUI will open up and you can type in "gnuplot" in the filter field.
Just select and install the package, MobApt will take care of any dependencies for you.
I'm gonna to use vagrant on my windows desktop to develop Laravel project. I have followed all the steps to do that. But it has been failed to create homestead.yaml using bash init.sh command.
Below is the error :
Fakhreddin#Lenovo-PC3 /cygdrive/d/laravel-vagrant/homestead
$ bash init.sh
cp: unwritable ‘/home/Fakhreddin/.homestead/Homestead.yaml’ (mode 0500, r-x------); try anyway?
I'm using Cygwin for simulating Unix terminal in the Windows.
(Copy of the comment I wrote above)
Never used Cygwin in my life, but what I would try is to run it as Administrator and re-try.
Otherwise, you may want to consider changing console client. For example, if you install Git, you should be able to use Unix commands via standard Windows console.
I would seriously point the fault at Cygwin, or its settings. I am a member of a team in which all of us run Homestead on Windows 7, with no problems at all. The difference is, we use native Windows command line.
I just created a new Vagrant box using puphpet and I have put a script file in /puphpet/startup-once/once.sh
I am trying to run commands like this to modify php.ini
sudo sed -i 's|;opcache.enable=0|opcache.enable=1|g' /etc/php5/fpm/php.ini
And I am just getting errors like
No such file or directoryd /etc/php5/fpm/php.ini
Then I connect using putty and I can see that the file is actually there. Why can't Vagrant run these files? I am running Virtual Box on Windows 8 if that helps.
The problem was that I was having Windows style line endings. Converted the line endings to UNIX style and the scripts ran just fine.
Just a note that for php.ini settings you should use the php section. Your changes will be overwritten by any future $ vagrant provision due to how the puppet php module handles settings.
I had run the MacPorts installer (2.0.3) for my OS X Leopard (10.5.8) which finished "successfully". Unfortunately the port command was not available so I looked in the MacPorts Guide which says that the installer should have run a so-called "postflight" script that sets the necessary environment variables. I tried to run the postflight script manually (which I downloaded from here), but the execution fails with the following output:
Detected the bash shell.
Your shell already has the right PATH environment variable for use with
MacPorts!
Your shell already has the right MANPATH environment variable for use with
MacPorts!
Your shell already has the right DISPLAY environment variable for use with
MacPorts!
Adding [default] tag to sources.conf if needed...
couldn't read file "/Contents/Resources/upgrade_sources_conf_default.tcl": no
such file or directory
Updating port image format...
couldn't read file "/Contents/Resources/images_to_archives.tcl": no such file or
directory
Synchronizing the MacPorts installation with the project's rsync server...
-bash: __PREFIX__/bin/port: No such file or directory
An attempt to synchronize your recent MacPorts installation with the project's
rsync server failed!
Please run 'sudo port -d selfupdate' manually to find out the cause of the
error.
You have succesfully installed the MacPorts system, launch a terminal and try it
out!
Read the port(1) manual page and http://guide.macports.org for help,
http://www.macports.org/contact.php if you need to get in touch with The
MacPorts Project.
Any ideas?
First invoke the port command directly:
$ /opt/local/bin/port help
If that comes back with something reasonable (like the help text) then it's just that your $PATH isn't being used by your current shell. Try logging off and back on again to resolve that in the short term (this will test that your .bashrc file is correctly configured) or you could just modify the PATH environment variable directly (which doesn't test .bashrc):
$ export PATH=$PATH:/opt/local/bin
You downloaded the postflight script but it alone cannot access the accessory scripts in Contents/ because those are located into the install package.
Those missing Tcl scripts are for upgrading from an older install, the log says PATH was already correctly configured but the macports bin directory could have the wrong position in PATH variables, for instance being at the end of PATH.
If you are doing a fresh install you can just only need PATH and MANPATH -you want man pages provided by macports before system's ones- as per [1]
[1] http://guide.macports.org/#installing.shell.postflight