Re: Operator vs. Command precedence
Re: Operator vs. Command precedence
- Subject: Re: Operator vs. Command precedence
- From: has <email@hidden>
- Date: Sat, 6 Jun 2009 20:14:10 +0100
Doug McNutt wrote:
All you can do is better educate users as to the similarities and
differences between commands whose names are identifiers and
commands whose names are keywords, and the gotchas that they need
to look out for when dealing with them.
On thing that would really help is a syntax coloring editor with
some capabilities that are more than just color.
Some artwork in the fonts that would tie together word pairs that
are going to be treated as a single command or variable would really
help.
Suggestion c/o Chris Nebel: apply underline formats to application
keywords. This will also underline any spaces within keywords, making
it easy to see where each keyword begins and ends; for example, path
to startup disk will appear as path to startup disk. To do this,
highlight the Application keywords style in the Preferences dialog's
Formatting pane and select Font > Show Fonts to bring up the Fonts
palette. Click on the popup menu in the top-left corner of the Fonts
palette and select the Single underline style.
HTH
has
--
Control AppleScriptable applications from Python, Ruby and ObjC:
http://appscript.sourceforge.net
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden