Skip to content

Commit 8e29531

Browse files
committed
v 0.1.0
1 parent 9b0adf5 commit 8e29531

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
# Adobe Script Runner
2-
Script runner for Adobe applications right from VSCode on Mac.
2+
Script runner for Adobe applications right from VSCode.
33

44
![Adobe Script Runner](/resources/Adobe-Script-Runner.gif)
55

@@ -19,7 +19,7 @@ Extension will open host application first if it's not running, and then execute
1919

2020
> Tip: You don't need to have file saved inside VSCode. Extension will be able to run code from unsaved documents. Kaboom!
2121
22-
Map keyboard shortcuts to execute the script even faster.
22+
Map keyboard shortcuts to execute the script even faster. Read how to do this on [Key Bindings for Visual Studio Code](https://code.visualstudio.com/docs/getstarted/keybindings) page.
2323

2424
**Note:** Contribution to support other Adobe applications as well as Windows is highly encouraged.
2525

@@ -51,7 +51,7 @@ Click `Cmd+,` on Mac or `Ctrl+,` on Windows to modify settings. Extension expose
5151
* `adobeScriptRunner.winIllustratorExe`: path to Adobe Illustrator executable (Illustrator.exe).
5252
* `adobeScriptRunner.winPhotoshopExe`: path to Adobe Photoshop executable (Photoshop.exe).
5353

54-
Executable paths for InCopy and InDesign for Windows are not exposed because they are handles differently then the rest of the apps. Go figure Adobe ¯\\\_(ツ)\_
54+
Executable paths for InCopy and InDesign for Windows are not exposed because they are handled differently than the rest of the apps. Go figure Adobe ¯\\\_(ツ)\_
5555

5656

5757
## Known issues

extension.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -82,7 +82,7 @@ function buildCommand(hostApp) {
8282
let appExe = '';
8383
if (osName === 'win') {
8484
// InDesign and InCopy does not expose 'appExe' in preferences - they are launched via Visual Basic magic.
85-
if (tempCommand.match('{appExe}')) {
85+
if (tempCommand.includes('{appExe}')) {
8686
appExe = getExePath(applicationName);
8787
if (!appExe || !fs.existsSync(appExe)) {
8888
showErrorMessage(`Unable to find ${applicationName} executable defined in preferences. Make sure you have that path set-up correctly.`);

0 commit comments

Comments
 (0)