| 2013-07-10 13:57:50 |
Andrew Ohm |
bug |
|
|
added bug |
| 2013-07-10 13:59:03 |
Andrew Ohm |
description |
Hello,
Sorry if this has been reported or fixed already, but it appears I am having issues running scripts with a few command line parameters.
For instance:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
Note the actual command I use is being truncated. This isn't a visual thing only, those parameters actually were not passed.
What's interesting, is this seems like a maximum character thing, as opposed to maximum arguments. For instance if I remove the "-te Cash" part, I get "room" for two extra command line arguments:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
+++ this Sikuli version is 32-Bit
Could this be fixed for 1.1? If a temporary fix or workaround is available that I or others who stumble upon this issue have, that'd be awesome too. |
Hello,
Sorry if this has been reported or fixed already, but it appears I am having issues running scripts with a few command line parameters.
For instance:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
Note the actual command I use is being truncated. This isn't a visual thing only, those parameters actually were not passed.
What's interesting, is this seems like a maximum character thing, as opposed to maximum arguments. For instance if I remove the "-te Cash" part, I get "room" for two extra command line arguments:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
+++ this Sikuli version is 32-Bit
Could this be fixed for 1.1? If a temporary fix or workaround is available that I or others who stumble upon this issue have, that'd be awesome too. |
|
| 2013-07-10 14:37:44 |
Andrew Ohm |
summary |
Command line arguments cut off |
[1.0]Command line arguments cut off |
|
| 2013-07-10 14:37:50 |
Andrew Ohm |
summary |
[1.0]Command line arguments cut off |
[1.0] Command line arguments cut off |
|
| 2013-07-10 14:57:57 |
RaiMan |
sikuli: status |
New |
Fix Committed |
|
| 2013-07-10 14:58:01 |
RaiMan |
sikuli: importance |
Undecided |
High |
|
| 2013-07-10 14:58:05 |
RaiMan |
sikuli: assignee |
|
RaiMan (raimund-hocke) |
|
| 2013-07-10 14:58:08 |
RaiMan |
sikuli: milestone |
|
1.1.0 |
|
| 2013-07-16 06:00:48 |
RaiMan |
tags |
arguments |
scriptrun |
|
| 2013-07-16 06:02:34 |
RaiMan |
summary |
[1.0] Command line arguments cut off |
[1.0] Windows: Command line arguments cut off |
|
| 2013-07-16 15:07:58 |
RaiMan |
sikuli: importance |
High |
Critical |
|
| 2013-07-16 15:08:16 |
RaiMan |
description |
Hello,
Sorry if this has been reported or fixed already, but it appears I am having issues running scripts with a few command line parameters.
For instance:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
Note the actual command I use is being truncated. This isn't a visual thing only, those parameters actually were not passed.
What's interesting, is this seems like a maximum character thing, as opposed to maximum arguments. For instance if I remove the "-te Cash" part, I get "room" for two extra command line arguments:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
+++ this Sikuli version is 32-Bit
Could this be fixed for 1.1? If a temporary fix or workaround is available that I or others who stumble upon this issue have, that'd be awesome too. |
--- fixed with 1.0.1
Hello,
Sorry if this has been reported or fixed already, but it appears I am having issues running scripts with a few command line parameters.
For instance:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -te Cash -sa
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
Note the actual command I use is being truncated. This isn't a visual thing only, those parameters actually were not passed.
What's interesting, is this seems like a maximum character thing, as opposed to maximum arguments. For instance if I remove the "-te Cash" part, I get "room" for two extra command line arguments:
C:\Windows\system32>c:\Sikuli\Sikuli\sikuli-script.cmd -j6 -r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
-Xms64M -Xmx512M -Dfile.encoding=UTF-8
-r c:\Sikuli\test.sikuli --args -w 2 -it 2 -sa -c -re
+++ using as SIKULIX_HOME: c:\Sikuli\Sikuli\
+++ this Sikuli version is 32-Bit
Could this be fixed for 1.1? If a temporary fix or workaround is available that I or others who stumble upon this issue have, that'd be awesome too. |
|
| 2013-08-14 13:52:58 |
RaiMan |
summary |
[1.0] Windows: Command line arguments cut off |
[1.0.1 ok] Windows: Command line arguments cut off |
|
