[1.0.1] scripts having blanks in path cannot be run --- fixed in 1.1.0

Bug #1234531 reported by RaiMan on 2013-10-03
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

******* problem

Typically I call my Sikuli from a shell script using escaped characters:

/Volumes/GraphicsXRaid/04\ Elements/_AE_Scripts_Effects/scripts\ from\ Kevin/Index\ Comps\ From\ Projects/Suppress_AE_Dialogs.sikuli

But I just ran a quoted version of the escaped path (TEST 2) and also got a similar output. BUT, this time I noticed what it's doing. The output says:

[error] FileManager: Not a valid Sikuli script: /Volumes/GraphicsXRaid/04\.sikuli

This is interesting because even though the space after the 04 in the path name is escaped and the entire path is quoted, it's tried to truncate my path name to "/Volumes/GraphicsXRaid/04\.sikuli" instead of "/Volumes/GraphicsXRaid/04\ Elements/_AE_Scripts_Effects/scripts\ from\ Kevin/Index\ Comps\ From\ Projects/Suppress_AE_Dialogs.sikuli"

I just moved my script to another test directory without a leading number followed by a space and Sikuli is working normally. I can double click and open the script file and it opens fine, as well as launch the script from command line and it works as expected. Is the leading number followed by a space crash a bug or am I missing something?


[Mac OSX 10.6.8] [Sikuli 1.0.1]

When I create a script and try to run the script or executable via command line, the Sikuli icon bounces and is highlighted in the dock, then the java applet bounces and highlights and the yellow banner flashes. At that point, both the java applet disappears and the highlight is removed from the dock icon, indicating that the app is no longer running.

I thought I might be doing something wrong but there's another seemingly related issue. When I double click the .sikuli script file, the IDE opens with that annoying dialog that says click ok or the script will run in 3 seconds. But instead of opening the script as it has in the past, it opens with an untitled document. If I try opening the script again from the file menu, the script will open and run fine.

I've checked the contents of the executable and the .py and html files are there with the correct info. Just not sure why this is no longer working. Any ideas?


RaiMan (raimund-hocke) on 2013-10-03
Changed in sikuli:
status: New → Fix Committed
importance: Undecided → High
assignee: nobody → RaiMan (raimund-hocke)
milestone: none → 1.1.0
description: updated
RaiMan (raimund-hocke) on 2015-06-24
summary: - [1.0.1] scripts having blanks in path cannot be run
+ [1.0.1] scripts having blanks in path cannot be run --- fixed in 1.1.0
Changed in sikuli:
importance: High → Critical
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers