Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[discussion] Processing 3 #6

Open
geo7 opened this issue Oct 12, 2015 · 10 comments
Open

[discussion] Processing 3 #6

geo7 opened this issue Oct 12, 2015 · 10 comments

Comments

@geo7
Copy link

geo7 commented Oct 12, 2015

I was just wondering what the compatibility was with processing 3?

Not sure if there are any 'gotchas' or not.

Thanks!

@myrjola
Copy link
Contributor

myrjola commented Oct 14, 2015

I haven't found any gotchas. At least the basic functionality works smoothly. Maybe the Readme should be changed to state that this package also supports processing 3.

@ptrv
Copy link
Owner

ptrv commented Oct 14, 2015

Maybe there are some new keywords in processing 3 that need to be added to the keywords list.

@ghost
Copy link

ghost commented Nov 2, 2015

processing 3 adds a new debbuger; so there's that.

@Krisselack
Copy link

Hi, i was not able to run a processing sketch under windows 7 (emacs 25.1.1, processing 3.3.).

.emacs-modification:
(setq processing-location ""C:/Program\ Files/processing-3.3/processing-java"")
(setq processing-application-dir ""C:/R/wd/processing/"")
(setq processing-sketchbook-dir ""C:/R/wd/processing/"")

processing-compilation-output:
-- mode: processing-compilation; default-directory: "c:/R/wd/processing/Reaktor1/" --
Processing Compilation started at Thu Mar 9 15:08:54
--force --sketch="c:/R/wd/processing/Reaktor1/" --run --output="c:/R/wd/processing/Reaktor1/output"
Der Befehl "--force" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.
Processing Compilation exited abnormally with code 1 at Thu Mar 9 15:08:55

Do you have any clues? Wouldn't know where else to ask.

@ptrv
Copy link
Owner

ptrv commented Mar 10, 2017

Why do you have double quotes around the values for the processing variables in your .emacs?
Does this also happen when you set processing-location to .../processing-java.exe instead of .../processing-java?

@Krisselack
Copy link

Double quotes are apparently necessary, otherwise the path wouldn't be recognized at all. The addition of .exe didn't change the output. Thanks.

@KevOrr
Copy link

KevOrr commented Jan 10, 2018

Necrobump, but the double double-quotes are the problem. ""a"" is actually three forms: the empty string "", the symbol a, and the empty string "". So (setq var ""a"") is equivalent to (setq var "" a ""), since whitespace is insignificant in this instance. In this case, var is set to the empty string, and a is set to the empty string.

Check the value of the variable C:/Program\ Files/processing-3.3/processing-java; it should be "" :P

@Krisselack
Copy link

Thank you! I tried to change it:
(setq processing-location "C:/Program Files/processing-3.3/processing-java.exe")

The value of processing-value:

processing-location is a variable defined in ‘processing-mode.el’.
Its value is "C:/Program Files/processing-3.3/processing-java.exe"
Original value was nil

Result was:
C:/Program Files/processing-3.3/processing-java.exe --force --sketch="c:/R/wd/processing/sketch_170309a/" --run --output="c:/R/wd/processing/sketch_170309a/output"
Der Befehl "C:/Program" ist entweder falsch geschrieben oder
konnte nicht gefunden werden. (the separated term program files was not identified as path)

KevOrr added a commit to KevOrr/processing2-emacs that referenced this issue Jan 16, 2018
* Changed `(symbolp 'cmd)` to `(symbolp cmd)`
* Instead of shell-escaping bits of the full command and then gluing it together
  manually (which is error-prone), instead collect the argument list and then
  call combine-and-quote-strings
* Should fix ptrv#6 (comment)
@KevOrr
Copy link

KevOrr commented Jan 16, 2018

@Krisselack see if the above patch helps. This is somewhat unrelated to the original issue however, so if you are still facing problems, you should probably open up a new issue.

@Krisselack
Copy link

Thanks! I applied the patch, however nothing changed. What helped now, was to rename the folder from "Program Files" to (german) "Programme". Apparently the issue was the space between "Program" and "Files".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants