Display feature availability | ||
---|---|---|
|
Windows
...
Based Systems:
CopSSH:
CopSSH is a Windows SSH Service based on the Linux SSH Implementation OpenSSH in collaboration with Cygwin.
Newer Versions of CopSSH don´t do not support the cmd.sh any more. The „Windows Shell“ "Windows Shell" can only be used as an interactive shell and doesn´t does not support command or script executions , - see https://www.itefix.net/content/windows-shell-sftp .
However, the „Bash "Bash and sFTP shell“ shell" will work on Windows Systems when using the cygwin supported Linux commands.
...
- The Windows command
set
will not be recognized , - useexport
instead. - The
%
special character%
to mark an environment variable like such as%VARIABLENAME%
will not be recognized, : use$VARIABLENAME
instead. - Executing chained Windows commands in one line with the command delimiter
&
or&&
will result in executing only the first command. Use the Linux command delimiter ";"
together with the proper Linux command instead. - prefixing Prefixing a command with
cmd /C
won´t work either.
...
Setting environment variables with set
works, but using this variable for further commands won´t work.
...
Example:
Setting a file name as an environment variable (works):
set TESTFILE=test.txt
calling Calling a command using this variable (doesn´t work):
echo MYPARAM=myTestParam >> %TESTFILE%
will result Instead, it results in:
A File with the name %TESTFILE%
will be being created and MYPARAM=myTestParam
will be being written to that file, which is the opposite to the desired behaviour behavior of creating a file named test.txt
with this entry.