Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
We don’t allow questions seeking recommendations for books, tools, software libraries, and more. You can edit the question so it can be answered with facts and citations.
Closed 11 months ago.
The community reviewed whether to reopen this question 11 months ago and left it closed:
Original close reason(s) were not resolved
Improve this question
For some internal script distribution, I want to be able to give users a single command they can paste into a Windows cmd window that will run a batch script from a URL.
In bash, the equivalent would be eval "$(curl -sS https://example.com/my-script)" or curl https://example.com/my-script | bash (but really I do need something more like the former, because I want to set env vars in the existing cmd session).
Similarly, in PowerShell according to https://stackoverflow.com/a/68530475/68051 this could be iex (iwr https://example.com/my-script).Content.
What's the best equivalent cmd.exe command for doing this?
This is for trusted internal use, so I'm not very worried about security risks of running remote scripts. I'm looking for the quickest easiest command I can give people to paste that will work on a typical Windows machine with no special setup.
Try this:
powershell -Command Invoke-WebRequest -Uri https://example.com/my-script -OutFile %TEMP%\downloaded.bat && %TEMP%\downloaded.bat
It indeed uses powershell to get the file, then it executes it directly in current cmd.
Related
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 months ago.
Improve this question
This answer states that the following will be possible:
For example, from the WSL command line you'll be able to type code /mnt/c/Users/username/src/windows-file.txt to open a Windows file in
VS Code, or type code /home/username/src/linux-file.txt to open a
Linux file in VS Code.
is it already possible with the newest WSL 2 and Windows 11 21H2?
At this point what I can do from inside WSL is to open the folder like this:
explorer.exe .
Which is already pretty awesome. But it would be even better to instead of running:
nano myfile.txt
open the file in Notepad++:
notepadpp myfile.txt
Sure, you can run any Windows executable this way.
notepad.exe myfile.txt will work, for example.
If your Notepad++ is in your PATH, then notepad++.exe would work too - mine isn't, though, so I have to use the full path:
/mnt/c/Program\ Files/Notepad++/notepad++.exe myfile.txt
You can of course create a shell script or an alias to shorten this command.
Just note that if you specify a file with a path then you will have an issue because the Linux path is passed verbatim to the Windows executable, but that can be fixed with wslpath.
Here is an example shell script that you could put into ~/bin/notepadpp for example:
#!/bin/bash
/mnt/c/Program\ Files/Notepad++/notepad++.exe "$(wslpath -w "$1")"
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 2 years ago.
Improve this question
My PhpStorm terminal doesn't work properly on Linux Mint
In Settings > Tools > Terminal my Shell path is "/bin/bash"
When I open Terminal window in PhpStorm and call ls command work properly but php and sudo and etc not work and return bash: php: command not found
Original terminal app:
Terminal in PhpStorm:
PhpStorm CLI interpreters:
Does the issue persist if your start PhpStorm from terminal, either with the command line launcher or with bin/phpstorm.sh?
When being launched from desktop/System menu, PhpStorm only sees environment variables configured in login shell, but not in interactive shell configuration files (like .bashrc or .zshrc).
Possible workarounds:
Workaround 1: make required variables available in a login shell by moving them to the corresponding shell profile config
Workaround 2: run IDE from a terminal
Workaround 3: edit the desktop launcher and set command to /path/to/shell -l -i -c "/path/to/phpstorm.sh" (make sure that the shell you specified there has the needed variables configured in its interactive shell configuration file)
see also https://youtrack.jetbrains.com/issue/IDEABKL-7589
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I've been using Git-BASH terminal for non-git tasks. I prefer to use and am more comfortable using a BASH terminal over the Windows PS or Command Prompt. Basically, I started looking into having a BASH terminal on Windows, when I realized I already have one.
Is there any technical/integrity/security risk to doing this?
There is no "GitHub bash", only the git-bash packaged with Git for Windows.
It is the only alternative to WSL (the Windows Subsystem for Linux).
I usually use Git for Windows with a simplified PATH, which means I have 200+ Linux command right from any shell session, even a simple CMD one.
Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 9 years ago.
Improve this question
When I was using a Linux laptop as my dev machine, I used to do "gedit xxxx" in a Terminal. Now I just switched to MacBook, I d like to do the same thing.
I know that I can open gedit in a command line like "open gedit", but can I add the file name? Otherwise I have to use vim. I am not a fan of vim.
Add
alias gedit="open -a gedit"
to ~/.bash_profile :
Now you'll be able to gedit directly from the command line.
try:
open -a /path/to/gedit /path/to/file.txt
I added the following to my PATH:
:~/Applications/gedit.app/Contents/MacOS/
and afterwards I was able to access gedit from
the command line. One caveat: if gedit is not already running on the system, then it throws an error if I launch it from the command line. Once gedit is already running though, this works to open files in gedit from the command line.
To edit the path, open ~/.profile in an editor
I use textmate for dev, here is a tutorial how it is done for Textmate
http://manual.macromates.com/en/using_textmate_from_terminal.html
I believe the same would apply to gedit.
Hope it helps
Closed. This question is off-topic. It is not currently accepting answers.
Want to improve this question? Update the question so it's on-topic for Stack Overflow.
Closed 10 years ago.
Improve this question
I want to run some Java programs in the background when the system boots in Ubuntu. I have tried to add a script in /etc/init.d directory but failed to start a program. i.e programs are not started. What should I do for that?
First of all, the easiest way to run things at startup is to add them to the file /etc/rc.local.
Another simple way is to use #reboot in your crontab. Read the cron manpage for details.
However, if you want to do things properly, in addition to adding a script to /etc/init.d you need to tell ubuntu when the script should be run and with what parameters. This is done with the command update-rc.d which creates a symlink from some of the /etc/rc* directories to your script. So, you'd need to do something like:
update-rc.d yourscriptname start 2
However, real init scripts should be able to handle a variety of command line options and otherwise integrate to the startup process. The file /etc/init.d/README has some details and further pointers.