Paul Gilmartin wrote, re ISPF FIND vs. XEDIT LOCATE: >Can't you front-end that with a macro?
Sure, I could, but FIND is a perfectly legitimate, related XEDIT command. So I don't want to replace it. An ISPF compatibility PROFILE XEDIT would do so, of course. >I have used a vendor product that tried to be intuitive at the expense of compatibility. >with real XEDIT, I ws accustomed to COMMAND QUIT to bypass confirmation. >With that product I needed to do [COMMAND] QQUIT. But in CMS XEDIT, QQUIT >is a synonym. >But I would never have done what IBM did: to make QUIT a synonym for something >else when the QUIT command is native. Even as I loathe UNIX admins who create >aliases for rm, mv, ls, ... in /etc/profile. I agree. I've always assumed that PQUIT came along later in XEDIT development (before GA) and this was a compatibility compromise. >The XEDIT behavior that irritates me most is that even when BANANA is visible in >the window and could merely be highlighted, XEDIT scrolls to center BANANA. >I worked around that with an elaborate set of macros. They broke with a later >release of XEDIT. I gave up. Ah.memories. In the early 80s, when dialup was the rule, I wrote SET VARCURL ON/OFF for XEDIT to do this. It wasn't that hard to make it behave. Some folks hated it, mind you, which is why it was a setting. >When I first encountered ISPF, case-sensitive search was the default. IBM >changed that to case-insensitive, retaining the "T" modifier (for compatibility?) >but removing its mention in the documentation, even though it retains an effect. Huh. See, this is the kind of reason I haven't tried to do an ISPF macro.that kind of historical subtlety! ...phsiii ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
