len
Freshman Member
Posts: 15 
|
Post by len on Dec 18, 2013 16:05:50 GMT -5
When editing cobol, I use > to indent for instance the level and data part of a data description but not the Pic that I want to keep aligned with other Pic's.
Example: 10 Dataname Pic X(8).
When I use line command > to indent 10 Dataname but not Pic X(8), the whole line is right shifted.
This is not the way the ISPF Editor works.
In ISPF only the ) line command works this way.
Is this the intended behaviour or a bug?
|
|
|
|
Post by George on Dec 18, 2013 16:44:57 GMT -5
Hi Len,
You'll have to provide some specifics. The < > shifts are also sensitive to boundaries. If a word (space delimited string) is located AT one of the boundaries, then that word becomes 'anchored' and will not participate in the shift. (This is as per ISPF guidelines)
Can you provide exactly what the line contained, what BOUNDS were active (if other than MAX), what > command you used, and what resulted.
George
Len: Well, yes, we're not doing it quite right, you're correct on that. A bit more playing showed up the bug. Since we're right at the tail end of wrapping up the 7.1 release, this fix will wait till that's out the door. But it will be corrected in the next maintenance after that. And since every major release seems to ship with some niggling bugs, no matter how hard we try, the next fix release after the initial 7.1 probably won't be too far behind.
Thanks for the bug report.
George
|
|
len
Freshman Member
Posts: 15
|
Post by len on Dec 20, 2013 13:24:12 GMT -5
Thank you for your quick reply. I conclude from the second part of your reply that you have the info you need about the bug, but to make it quite clear I include the example below.
=COLS> ----+---1----+----2----+----3----+----4----+----5----+----6----+----7----+----8
00473 > 05 TRCADR-DFHCOMM Pointer.
What I intend is to move 05 TRCADR-DFHCOMM two columns to the right, but leave Pointer where it is. What happens is that Pointer also moves two columns to the right.
I think you have made a marvelous piece of code and your support seems to be superior.
I just started using SPFLite and it enables me to do a lot of coding work at home without access to a mainframe.
The feeling is like the real ISPF Editor. I specially liked your HILITE support.
If anybody is interested to try it I modified your cobol.auto so the SCHEME part of it is
SCHEME 0 0 7
SCHEME 1 5 7
SCHEME 2 14 7
SCHEME 3 9 7
SCHEME 4 5 7
SCHEME 5 6 7
(Black background is not mandatory even if you are a mainframe addict!)
I will send you my little money contribution shortly.
Please have a Happy Christmas!
Regards / len
|
|
|
|
Post by George on Dec 21, 2013 13:33:56 GMT -5
Len: Robert got interested in the problem, so I've passed the fix over to him. Actually, you're better off with him doing it, he's a lot more thorough with things than I tend to be. (I'm a quick and dirty programmer by nature, Robert is constantly acting as my conscience in things).
So you MAY see the fix in 7.1, no promises.
As to colorizing, yes it's hard providing samples since everyone has different ideas about the basic stuff. Like you, I've 'gone off' the old black screen. In 7.1, the options for specifying colors in the AUTO files has been expanded to support more format options for the color specification. You may also want to check out the alternating background colors (banding - like the old green/white printout paper). Once you try it, I'm sure it will become your standard. (It's in the 7.0 version)
George
|
|
len
Freshman Member
Posts: 15
|
Post by len on Dec 23, 2013 13:13:52 GMT -5
Hello Robert,
Thanks a lot for your energy! It would be wonderful if the new code could do it into the 7.1 release.
I understand after reading your description that there are a lot of effects to consider when rewriting the code.
I use bounds sometimes but normally not when editing program code, rather when manipulating test data.
So if you can´t get it all into the 7.1 release, a viable solution that would work fine for me would be to temporarily invalidate the < and > commands when bounds are set to something else than 1 and max-column (in case you need a plan B, but I doubt it!).
Kind regards / Lennart
|
|
len
Freshman Member
Posts: 15
|
Post by len on Jan 15, 2014 5:21:25 GMT -5
Hi Robert,
I installed 7.1 about a week ago. Now < and > work as a charm. I haven't found any problems with them. I have never been aware of or concerned by the issue of quoted blanks, so I haven´t tried that. My main use of < and > is to indent Cobol code properly, where I often want specifications further to the right to keep their alignment when I indent the main code on the left side. I am sorry I did not answer you sooner.
I have some more minor issues that I have collected in a list. I will open some new threads for them.
Regards / Len
|
|
