Good point. It makes me think I should edit my recent macro posts to make sure end-users are aware of the need to setup an ENV_PATH variable. I assume if they're familiar with Homebrew and installing packages they would already know this... but at the same time I think that was something that tripped me up initially.
If you use this in conjunction with Typinator, the spell check prompt list will be positioned next to the Create new Typinator Item window if it is open.
Hi there! I'd be glad to help you troubleshoot the issue. If possible, post your macro here (or at least a screenshot of the entire macro including triggers). I just want to confirm that nothing critical has been changed, perhaps even unknowingly.
Also, could you clarify what you mean by this part?
Without seeing your macro itself... it looks like maybe you changed the trigger? I see you pressing ⇧⌘C, or something to that affect, but the macro is designed by default to use ⌃⇧S for English and ⌥⇧S for Spanish.
If you changed the triggers can you verify you changed the corresponding lines...
So your copy works just fine on my end, which leads me to believe it's an issue with the Homebrew package; perhaps where it's installed.
Do this: open Terminal, type brew info aspell and note the location where it is installed. On mine it is /usr/local/Cellar/aspell/0.60.8. Verify that your ENV_PATH includes the /usr/local/Cellar part or at least /usr/local/ in it. Report back and we'll go from there.
Hey I'm stoked that you were able to get it working. I should have thought of this a little earlier because my wife's MacBook is an M1 and I had to setup the environmental path variable differently on hers... but that was so long ago I forgot haha.
Anyhoo, be sure to let me know how you like the macro itself and if you have any ideas to improve it.
If you're a Typinator user, check out the macro I built to quickly add a mistyped word to a set using Typinator's AppleScript dictionary and Aspell to provide spelling suggestions.
Finally, I would appreciate the help if someone can implement this on aspell instead of hunspell or edit the macro so it use aspell when it is a normal world and use hunspell when it is a medical term.
Hey there! Thanks for trying out the macro and I'm glad to see it's proven useful for you.
The only way I can think of to easily modify it to differentiate between medical and non-medical words is to use two different triggers, and use the two different CLI programs (aspell and hunspell) according to which trigger you used.
For an idea of what I mean by this, see these two screenshots which are part of another macro I built that also uses Aspell.
Obviously you could simplify that by just using the actual triggers in the switch action; again this is just an example taken from my other aforementioned macro here: