On Thu, 3 Mar 2022 14:35:41 +0000, Seymour J Metz <[email protected]> wrote:
>That is not a workaround for the problem that I'm addressing. Consider the >command > > CHANGE /FOO/FOOBARBAZ/ > >on a line with few spaces. With TRUNC 72, text can spill over into the >continuation column. The change I'm suggesting is that there be a new mode in >which > > 1. Any type of insert or string replacement has no effect beyond the > truncation column > 2. Data keyed in beyond the replacement column are retained And I would counter-propose that you create a CHANGE XEDIT macro that does what you want (I was trying to illustrate that a macro can play with the settings). It's not that I'm averse to the idea of a change in XEDIT. In fact, I like "smart" behavior. But it turns out that mucking with defaults has its risks. VM Development was burned by that a couple of years ago when they changed one of the other default behaviors in XEDIT to make life easier. Alan Altmark IBM ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
