"AppleScript: Toggle Binary" and AppleScript (Binary) syntax not working properly

[earhax]

When opening a .scpt file in Sublime Text, it always opens in binary/hex view. Neither toggling the binary or changing the syntax converts it into the readable/editable AppleScript format.

[idleberg]

Could you provide a minimal, reproducible example that shows this behaviour? I guess it would also be helpful to know more details about your environment, most importantly your Sublime Text version. Personally, I have long abandoned the editor, but still have version 3 installed.

[earhax]

I'm on stable 4126. Tried removing/adding the package again, but still can't seem to get . scpt files to open in a text-readable/editable format. I'm on macOS Sierra 10.12.6. The issue occurs with any scpt file I open in ST. I've attached a simple one as an example. Which editor are you using now if you've abandoned ST? I'm curious about the top pros & cons compared to ST. Thanks, Mike

…

On Thu, Oct 6, 2022, 04:55 Jan T. Sott ***@***.***> wrote: Could you provide a minimal, reproducible example that shows this behaviour? I guess it would also be helpful to know more details about your environment, most importantly your Sublime Text version. Personally, I have long abandoned the editor, but still have version 3 installed. — Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMCQNZOUDL6GCWYK3G77MBDWB2433ANCNFSM6AAAAAAQ5QYN4E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[idleberg]

For now, I can confirm, that the automatic decoding of .scpt files does not work in Sublime Text 4 (it works fine in ST3). However, you can still use decode an open file using the AppleScript Extensions: Toggle Binary command. I might find some time this weekend to look into it.

Which editor are you using now if you've abandoned ST? I'm curious about
the top pros & cons compared to ST.

I almost valued Sublime Text for its speed and knew it inside out after 8 years of using it. At some point, I started converting some of my ST packages for other editors, without using them myself. I guess that gave me some insights into what else it out there and I liked different things in different editors. For example, I always liked the look of Atom and as a developer, I loved its API (no other editor I've worked with comes close!)

I'm now using Visual Studio Code. Yes, it feels much slower than good old Sublime Text, but in the end, some of its features were simply too compelling or felt less like a workaround (e.g. I disliked the various Terminal integrations in Sublime Text). Microsoft has invested a lot into it that suits me and the languages I work in the most.

I don't want to talk anybody out of the editor that works for them. Keep using what works best for you! At the same time, it might be worth it to look around what else is available. Most modern editors share the groundbreaking features (command palette, multiple cursors, etc) of TextMate or Sublime Text. On the other hand, Sublime Text benefits from some of the innovations in VSCode (e.g. language server protocol). So switching editors isn't as much leaving your comfort zone as you'd probably imagine.

[idleberg]

Update: Actually, ST3 and ST4 behave differently. When ST is closed and I drag & drop a .scpt in ST4, it will not decode the file. When ST is already open and I open the file, it will. Can you confirm this behaviour?

[earhax]

Jan, Thanks for the quick turnaround & support with this.

On Thu, Oct 6, 2022, 14:18 Jan T. Sott ***@***.***> wrote: For now, I can confirm, that the automatic decoding of .scpt files does not work in Sublime Text 4 (it works fine in ST3). However, you can still use decode an open file using the *AppleScript Extensions: Toggle Binary* command. I might find some time this weekend to look into it.

unfortunately, toggle binary doesn't seem to work for me. or is there some other step to decode the file besides selecting the toggle binary command?

Which editor are you using now if you've abandoned ST? I'm curious about the top pros & cons compared to ST. I almost valued Sublime Text for its speed and knew it inside out after 8 years of using it. At some point, I started converting some of my ST packages for other editors, without using them myself. I guess that gave me some insights into what else it out there and I liked different things in different editors. For example, I always liked the look of Atom and as a developer, I loved its API (no other editor I've worked with comes close!) I'm now using Visual Studio Code. Yes, it feels much slower than good old Sublime Text, but in the end, some of its features were simply too compelling or felt less like a workaround (e.g. I disliked the various Terminal integrations in Sublime Text). Microsoft has invested a lot into it that suits me and the languages I work in the most.

Cool. I work in game dev as a technical sound designer. i do various scripting as needed, but not any really heavy lifting on the code side. I've brushed with vs a few times & can definitely see it's potential.

I don't want to talk anybody out of the editor that works for them. Keep using what works best for you! At the same time, it might be worth it to look around what else is available. Most modern editors share the groundbreaking features (command palette, multiple cursors, etc) of TextMate or Sublime Text. On the other hand, Sublime Text benefits from some of the innovations in VSCode (e.g. language server protocol). So switching editors isn't as much leaving your comfort zone as you'd probably imagine.

Yeah at this point I've embedded myself pretty deep into customizations of sublime (theme, macros, completions, snippets, shortcuts, etc). so it would no doubt take quite a while & be very cumbersome to switch to something else at this point. however, in some cases I'll still use other editors on a per-need basis when ST is lacking some feature or behavior. e.g. i often use bbedit for plists & other files that don't seem to open properly in ST.

…

— Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMCQNZJ5V4VQRIGYAP7ZMR3WB463XANCNFSM6AAAAAAQ5QYN4E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[earhax]

Unfortunately, neither method works for me. so far, i just have to resort to copying/pasting between Apple's script editor app & ST when working with these files. i'm wondering if it could be interference from some other package i have installed, or maybe some other local setting. lmk if there's any other info you need that might help. Thanks again, Mike

…

On Thu, Oct 6, 2022, 14:38 Jan T. Sott ***@***.***> wrote: Update: Actually, ST3 and ST4 behave differently. When ST is closed and I drag & drop a .scpt in ST4, it will not decode the file. When ST is already open and I open the file, it will. Can you confirm this behaviour? — Reply to this email directly, view it on GitHub <#11 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMCQNZKIFJTR22M5P5MT7VTWB5BF5ANCNFSM6AAAAAAQ5QYN4E> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[idleberg]

Tested on another computer with a fresh ST4 installation. I still get the same behaviour as described in my earlier post. Regarding interfering packages, could you check the console if there are any error messages?