I think we would all agree that the defaults for XEDIT are "not the way
I would have done it." But, we should also agree that changing just
about anything with XEDIT is possible, and in most cases easy using the
tools provided with XEDIT.
So, let's not hang our thoughts about XEDIT based on one such setting,
especially, col 72 when editing assembler.
Tony Thigpen
Phil Smith III wrote on 2/24/22 14:44:
Paul Gilmartin wrote:
But it's overdue for the ISPF and XEDIT designers to do what ISPF promised
never to do: introduce support for curses/terminfo-based terminals. Most
desktops have those nowadays.
Not sure how that would work, since it's a 3270 data stream. Would mean a
HUGE rewrite, and for what (at this point)? That ship has sailed, alas.
How does KEDIT treat column 72?
A fair question; I think the answer is that it's not comparable, since KEDIT
doesn't have the same physical screen limitations (including attribute
bytes), nor does it have the concept of "filetype" per se. It does say:
The truncation column, controlled by SET TRUNC, is normally set equal to the
WIDTH setting.
So maybe that's the answer you want? IOW, unless you set it, TRUNC
effectively doesn't get set.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
