Every time I start the installer under Linux, a terminal window opens with the message "Starting Installer ..."
Where is the option to disable this terminal window?
The installer is a shell script. The desktop environment opens a terminal if you execute a shell script. In some desktop environments you can disable this on a per-executable basis.
In any case, this is a manual process that cannot be configured in install4j.
Related
On Windows, when I open a folder from the terminal in VSCode with the "code ." command, it opens VSCode correctly but the terminal window becomes a slave, running all console commands from the app without returning command to me. If I close the terminal, VSCode also closes, it seems that the application thread is being run as child of the terminal process that gets killed with its parent. The same does not happen with "xp . ", my shortcut for the file explorer.
My question is how to make VSCode open as its own process letting the terminal be free.
Found the solution:
cmd /c start "VSCode" "code.exe" .
I am trying to hide CMD After opening VSCode from Run window in Windows and don't work, I test those solutions
How to exit Command Prompt after launching VSCode
But it didn't work.
I have the latest version of VSC installed on a Windows 10 machine. If I run VSC regularly, so not as an admin, then if I try to open a terminal I get a 740 error. If I start VSC with Administrator privileges everything works fine.
What could be causing this? I would prefer if I didn't have to run VSC with Admin privileges.
P.S.
I'm using VSC its integrated Terminal.
If I switch to Command Prompt as external Terminal, the problem is gone. But I would prefer to continue to use the integrated Terminal.
There are some other Slack topics that point to ensure not running VSC in compatibility mode, which is indeed disabled on my end.
I found out the cause. Git Bash was configured as the Integrated Terminal of VSC. Its run file C:\Program Files\Git\bin\bash.exe was configured in Windows to "Run as Administrator". As a result, I also had to start VSC "as administrator" to open a Terminal. After unchecking the box "Run as Administrator" for Git Bash, I no longer need to run VSC as administrator to be able to open the Terminal.
Until yesterday, my VSC worked fine. I opened, edited, and run my python scripts without a problem.
However since today when I start my VSC session, it starts on Powershell Terminal, that doesn't recognize my conda enviroment despite I set the default terminal as cmd:
When I open the cmd terminal manually, automatically loads my conda env, however when I run the command "Run Python File in terminal" it always opens on Powershell
Any suggestion on how to fix this?
As in the topic, how do I change it so that powershell DOESN'T open and cmd terminal does open when starting the IDE? Windows' cmd is set as default but still powershell opens when I start the IDE