|
|
Post by George on Jun 11, 2019 15:32:19 GMT -5
I thought I could open up the macro support to allow a macro to have the same name as a built-in command. And it seemed to be working.
But "Oh what a tangled web we weave ..." applies so completely to SPFLite. In researching a question from Ren and walking through the code path, it becomes apparent that allowing macros to be named the same as built-in commands just won't fly. I won't explain why, it just generates "Well why not ..." type questions.
So ... no macro-names = built-in command-names.
George
|
|
|
|
Post by George on Jun 11, 2019 22:04:45 GMT -5
OK, let me explain why this ain't going to happen.
The ROI just isn't there, if we have 2 or 3 users who would take advantage of this I'd be surprised.
Being an internal structural change, I'd be doing the work, Last year we said we were not going to tackle any major changes, yet we've still done some significant stuff, That is ending.
I guess I'm no longer responsive to the argument that "ISPF did it, so SPFLite should". SPFLite is a fine editor now in it's own right, I don't think it has to follow ISPFs lead any more.
The source is now public, if there is truly demand for some new feature or extension, then someone else should step up and take over. I'll happily pass over administration of the web site and forum.
I guess I'm just getting tired. Been working on this for over 15 years now, I've taken it about as far as I can.
George
|
|
|
|
Post by George on Jun 12, 2019 11:06:10 GMT -5
I've created a MACRO.AUTO file for those who wish to colorize the text during edit. Simply copy to your \Documents\SPFLite\AUTO folder and make sure your Profile for MACRO has HILITE AUTO ON. Oh, and of course, that you'e got some colors specified in Options => Scheme. George macro.auto (30.56 KB) |
|
|
|
Post by George on Jun 12, 2019 14:59:13 GMT -5
MixedCase NO is correct, it says the keywords are NOT searced in a case sensitive manner. (May not be intuitive, but that's what the Doc says.)
Yes, the COMMENT is wrong, I'll correct it.
Colors are all up to you. Check your Options SCHEME, the AUTO files I distribute (and I'm working through updating them) use the following color Scheme numbers.
; User Scheme 1 - Comments
; User Scheme 2 - Numeric strings
; User Scheme 3 - Quoted strings
; User Scheme 4 - Delimiters / Operations
; User Scheme 5 - Language Compiler Directives
; User Scheme 6 - Language Equates / Constants / Data Definition Keywords
; User Scheme 7 - Language Keywords Group 1
; User Scheme 8 - Language Keywords Group 2
; User Scheme 9 - API Equates
; User Scheme 10 - API Methods / Functions
So, to use the supplied AUTO files, once they're all converted, setup your SCHEMES accordingly.
If you want to edit the AUTO files to use your own Schemes, feel free, just coordinate your Scheme number usage.
George
|
|
