Hi,
I am trying to create a custom 123.cmd on a per project basis on a OSX platform. By default on osx .cmd files are opened with text edit , once you edit and run for some reason the command promt wont initialize. Just as a test I even grabbed one of those intro cmd files from first steps .

This runs and initializes the texport terminal

# Set the prompt to display the current directory followed by an arrow
prompt ‘`strcat(oppwf(), “Ari -> ")`’

This file reads as a “simple document” on osx , change it to


# Set the prompt to display the current directory followed by an arrow
prompt ‘`strcat(oppwf(), “rob -> ")`’

text edit saves and its listed as a document. I make sure its executable but the texport wont initialize. and I get prompt '`strcat(oppwf(), “rob -> ")` in the terminal.
I normally use code runner on osx but it does not recognise .cmd files . I presume the error is caused by the file type.

Any ideas ?

Rob

in TextEdit try Format menu/Make Plain Text. that saves without formatting

TextWrangler is good too.

Text edit, was set to plain text, ive walked away from it , as expected text wrangler works like a charm

Rob

nice!

Nano in the terminal is also a winner.

All hail the vim :-)