8000 dotnet-script init error when setting permissions when working directory path includes a space. · Issue #605 · dotnet-script/dotnet-script · GitHub
[go: up one dir, main page]

Skip to content
dotnet-script init error when setting permissions when working directory path includes a space. #605
Closed
@easp

Description

@easp

I'm running on MacOS 10.15.7. My working director is in iCloud documents (basically Apple's cloud sync service, like OneDrive, or Dropbox 5652 ). The directory path has a space in one of the directory names. This seems to cause a problem for botnet-script init (see below). It appears that the file path is not being quoted when it tries to run chmod to set execute permissions on the script.

MyComputer:dotnetscripting eas$ dotnet-script init
Creating VS Code launch configuration file
...'/Users/Me/Library/Mobile Documents/com~apple~CloudDocs/prj/dotnetscripting/.vscode/launch.json' already exists' [Skipping]
Creating OmniSharp configuration file
...'/Users/Me/Library/Mobile Documents/com~apple~CloudDocs/prj/dotnetscripting/omnisharp.json' [Created]
Creating default script file 'main.csx'
Creating 'main.csx'
fail: Dotnet.Script.DependencyModel.Process.CommandRunner[0]
      chmod: /Users/Me/Library/Mobile: No such file or directory
fail: Dotnet.Script.DependencyModel.Process.CommandRunner[0]
      chmod: Documents/com~apple~CloudDocs/prj/dotnetscripting/main.csx: No such file or directory
...'/Users/Me/Library/Mobile Documents/com~apple~CloudDocs/prj/dotnetscripting/main.csx' [Created]

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

      0