Skip to content

spurious spaces in the wolframscript launch command upon saving .wls files #65

@jvo203

Description

@jvo203

My .wls files contain #!/usr/bin/env wolframscript as the first line in order to be able to execute WolframScript files directly from the terminal like this "./hello.wls". (P.S. one must also change the file permissions, i.e. chmod a+x hello.wls)

Unfortunately the official Wolfram Research vscode extension always inserts extra spaces to the launch command, turning it into #! / usr / bin / env wolframscript.

Is there a way to make this extension aware of this terminal launch command so that no spurious spaces are inserted upon saving a .wls file?

Because of this problem it is impossible to use the official Wolfram Research vscode extension. Had to turn to user-provided alternative extensions.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions