On Tue, Feb 17, 2015 at 4:41 AM, Paul Bailey <PaulBailey@xxxxxxxxxx> wrote:
We also have that problem, and we don't use the IFS to
store the source.
This strikes me (as someone who doesn't use RDi, but uses other
programmer's editors for Windows) as very odd. If your source is in source
physical files, then the record lengths are fixed; and in principle, you
*should* have blank spaces at the end of every line, to pad the record. (I
presume this is what Charles meant when he said the "trailing space issue"
should only be for folks with source in (stream files in the non-QSYS
portion of) the IFS.)
So maybe there are different "sensibilities" for folks using RDi.
One thing some editors do is to not allow navigation beyond the last
nonblank character on a line, except when doing rectangular selection. And
this is settable, so you can opt out of this limitation.
I would think something like RDi, which would be used for both source
physical files and stream files, would have something like this. Further,
I would expect it to have a "trim trailing spaces when saving to stream
file" option. (I don't fully understand the "trim trailing spaces when
opening" proposal, because of the aforementioned *conceptually necessary*
spaces in source PFs. Maybe what is meant is "behave as though there are
no trailing spaces", which is tantamount to what I was describing above.
Perhaps some folks would find it more intuitive to call this "trim trailing
spaces when loading editing buffer"?)
John Y.
midrange.com
