Skip to main content
Swamplander1
Swamplander1
Participant
August 27, 2022
Question

How to use the aliasPath in ExtendScript Debugger when using symlinks?

  • August 27, 2022
  • 1 reply
  • 278 views

While the 2.0.3 release notes say there are improved docs for the `aliasPath` attribute, I still can't figure out how this is supposed to work or what the value should be. Google search for "aliasPath ExtendScript" isn't helping either...

 

I've tried using the path to where the CEP is loaded from, the local webroot path, and their parent paths... but I can't get anything to work. Also looks like this property isn't respecting the ${workspaceFolderBasename} variable...

 

An example scenario would go a LONG way like:

 

If your project is stored in `~/repos/myCepProject`, and you've created a symlink to it like `sudo ln -s ~/repos/myCepProject "/Library/Application Support/Adobe/CEP/extensions"`, you should set the value of `aliasPath` to the following: ?????

This topic has been closed for replies.

1 reply

sberic
sberic
Legend
September 7, 2022

That's great feedback! Thanks for providing it! To hopefully resolve all five of those question marks at once:

 

If your project is stored in:

    ~/repos/myCepProject

and you've created a simlink to it with a command like:

    sudo ln -s ~/repos/myCepProject "~/Library/Application Support/Adobe/CEP/extensions"

then you should set the aliasPath property to one of the following:

    "aliasPath": "/Users/{username}/Library/Application Support/Adobe/CEP/extensions/myCepProject"

    "aliasPath": "~/Library/Application Support/Adobe/CEP/extensions/myCepProject"

 

Please note that the commands and path examples above are formatted for macOS. The feature otherwise works identically on Windows.

 

Hope this helps!

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices