Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
earhax opened this issue Oct 5, 2022 · 7 comments

Comments

@earhax
Copy link

earhax commented Oct 5, 2022

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
Copy link
Owner

idleberg commented Oct 6, 2022

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
Copy link
Author

earhax commented Oct 6, 2022 via email

@idleberg
Copy link
Owner

idleberg commented Oct 6, 2022

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
Copy link
Owner

idleberg commented Oct 6, 2022

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
Copy link
Author

earhax commented Oct 7, 2022 via email

@earhax
Copy link
Author

earhax commented Oct 7, 2022 via email

@idleberg
Copy link
Owner

idleberg commented Oct 7, 2022

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants