|
Post by Stefan on Nov 14, 2022 10:10:44 GMT -5
George,
Would you consider assigning "special" sessions like CLIP, SET, EFT, DIFF, etc a named Profile each?
Presently they all operate using the DEFAULT profile. Especially the EFT would benefit from some profile-related features, such as tab stops and AUTO-colorisation to aid readability.
Adding this to the DEFAULT profile would do the job, but also means that every new profile SPFLITE creates will inherit the setting (eg. tab stops) and the AUTO colorisation would apply to every file using the DEFUALT profile.
Not Ideal.
Would it be possible for such sessions to use a profile which matches their name (e.g. a CLIP session uses CLIP profile, EFT uses the EFT profile, etc)?
|
|
|
Post by George on Nov 25, 2022 14:24:51 GMT -5
Stefan: In the latest Beta.
George
|
|
|
Post by George on Nov 25, 2022 16:28:31 GMT -5
I didn't include DIFF because it has some special attributes with special handling.
George
|
|
|
Post by Stefan on Nov 26, 2022 12:23:12 GMT -5
George,
In version 2.7.22328 beta,
Two things.... a) What profile is assigned to say... a SET edit session please?
I tried SET and SET_EDIT but neither had any effect - the SET session opens with DEFAULT profile, although a DEFAULT.AUTO colorisation file has no effect despite HILITE FIND AUTO.
b) Given my penchant for macros, you won't be surprised to learn that the omission of DIFF is slightly disappointing. On the face if it, I agree, there appears to be little point in the case of DIFF. But the IMACRO facility is provided via the Profile, so no profile means no IMACRO capability. Which in turn removes users' ability to improve their productivity by tailoring the output from the DIFF command.
By the way - another slight oddity regarding the SPFLite window's 'TITLE' bar...
When editing a file,say ABC.AUTO,
the title bar reads EDIT - ABC.AUTO - SPFLite(v2.7.22328) S:\SPFLite\AUTO\ABC.AUTO
For a CLIP session, the Title bar reads CLIP - SPFLite(v2.7.22328)
For a DIFF session, the Title bar reads CLIP - SPFLite(v2.7.22328) For a EFT session, the Title bar reads EFT-Edit - SPFLite(v2.7.22328) For a SET session, the Title bar reads SET-Edit - SPFLite for: DEFAULT
The SET example strikes me as especially curious.
|
|
|
Post by George on Nov 26, 2022 12:39:41 GMT -5
I'll look at DIFF again, maybe I was worrying excessively about interaction with the unique DIFF display.
George
|
|
|
Post by Stefan on Nov 26, 2022 12:56:08 GMT -5
Thanks.
Ahh, our actions, crossed, please refer to previous post re title bars.
|
|
|
Post by George on Nov 26, 2022 15:32:46 GMT -5
See the Beta post, it lists the Profile names as CLIP, SETEdit and EFTEdit.
George
|
|
|
Post by Stefan on Nov 27, 2022 6:39:28 GMT -5
George,
Maybe I'm losing my marbles (can't really afford to - not many left as it is), but...
I'm running the v22329 beta. I've created a profile call SETEDIT I've create a SETEDIT.AUTO colorisation file I type SET primary command and the SET-Edit session opens. Status Bar shows it is using Profile DEFAULT. Issue PROFILE primary command and the same is confirmed. Stumped.
|
|
|
Post by George on Nov 27, 2022 10:30:51 GMT -5
Stefan: OK, there's something wrong in there, you're not going crazy. Well, that's what Betas are for.
I'm chasing it down.
George
|
|
|
Post by George on Nov 27, 2022 11:49:32 GMT -5
Robert: Correct guess. The whole process of opening ANY file in a new tab gets incredibly involved, and the special cases just add another complexity layer. Add in the .profilename command override requirement to the mix and just tracing one open through it all takes forever.
It's working now.
Stefan: DIFF is now also supported.
George
|
|
|
Post by Stefan on Nov 28, 2022 11:00:32 GMT -5
George,
Thank you for following up on this. We're definitely getting closer.
Using v2.7.22331 beta
SET primary comamnd opens the SET-EDIT session using the SETEDIT profile. Both the Status Bar and a PROFILE primary command confirm this.
However, only some of the profile settings appear to be applied e.g. MARK or TABS work, but AUTO colorisation and IMacro don't work
|
|
|
Post by George on Nov 28, 2022 11:18:29 GMT -5
Stefan: Shows how those special Edit sessions really are special.
Checking.
George [UPDATE]
Corrected, check Beta 22332
[/UPDATE]
|
|
|
Post by Stefan on Nov 28, 2022 16:39:38 GMT -5
Hmm - I'm running 22332. Will try again.
|
|
|
Post by Stefan on Nov 29, 2022 11:00:58 GMT -5
George, Good news and thank you. I have the IMACRO and Auto colourisation working for SETEDIT profile. SETEDIT is already is a more readable experience. I had hoped that it might also be consistent with EFT and offer the ; comment syntax, but alas it does not. My first thought was that this is because ';' is the comamnd separator, but SET-EDIT doesn't allow one ALIAS to execute more than one command anyway.
So could we perhaps have the ; comment syntax in SET-Edit sessions?
It would help me remember why on earth I have some of the SET entries that I do have.
I envisage something like this
|
|
|
Post by George on Nov 29, 2022 11:50:32 GMT -5
Stefan: I'm doing stuff in SET right now anyway, so I'll have a look. It's harder than you'd think.
I'm yanking the PUSH / POP support. I never understood the thought behind it, and I don't believe anyone ever used it to my knowledge.
George
|
|