Gil Barmwater

Thanks for that! That code has been there a long time so I guess no one ever tried it on a non-Windows system.

Thanks to Rick, we know that this behavior was introduced as part of RFE 777. There does not seem to be any documented request for this feature, only that MS recomended it. We also know that there are several examples of "bad" behavior resulting from its introduction. So, I agree that adding a function that would allow DISABLE_NEWLINE_AUTO_RETURN to be turned on/off seems to be needed. The remaining question is what the default/startup behavior should be. Whichever one is chosen, the potential for...

It appears this was introduced with 5.0.0 as I cannot reproduce it with 4.2.0. I would be interested to learn if there was a use-case that inititiated that change.

I am surprised that no one has replied to your post so far. I do know that this list isn't as heavily followed as some of the others so I would suggest re-posting on the developers list where, hopefully, you will get some responses.

Actually, you need only to identify the routines in PgmA needed by PgmB and move them to a new PgmC, then identify the routines in PgmB needed by PgmA and move them to PgmC too. Finally, change the Requires in PgmA to use PgmC instead of PgmB and change the Requires in PgmB to use PgmC instead of PgmA. It sounds more complicated than it is. BTW, PgmC now clearly identifies the "common" routines needed by the other programs. FWIW

First question: I would build the documents just before the Release candidate is built. That way if any last minute fixes require documentation changes, they will be included (not likely however). Second questions: the Publish subdirectories in oorexx are from before I became involved so perhaps they had something to do with Publican. I would ignore the three warnings as the documents seem to build OK in spite of them. Final question: I am not that familiar with the Jenkins build process so I don't...

I was able to get the zip file, open it (Windows treats it as a folder), and double click on the readme.pdf. Adobe Reader was able to display the document which looked normal and complete. So I have no idea why you would not be able to upload it to SF. Sorry :-(

I will have a look at the zip file later today. No changes needed to HTML, this fix only affects the PDFs.