Dear Gil,
Can you share some info on the non-existent FOP mirror? I have a similar
problem with using my docbuild tools on Ubuntu, they used to work but when I
retry them now they do not work. Could be the same problem.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> Am
Dear Gil,
Having slept on it I think you are right, anyone interested in building the
documentation must check out the entire /docs/trunk and so have the tools
folder already.
Would it be acceptable to all if I empty the oorexx-docs-bildutils folder in
the „Files“ section and keep only the
On 1/3/23 23:11, taf wrote:
Do you mean modRexx for apache httpd? If so, that's on me. I know
that the build doc is sadly lacking, I'll put some work into it this
month. May I draft you as guinea pig/tester?
On 2023-01-03 07:13, Bill Turner, WB4ALM wrote:
4) It would be nice if RexxMods
P.O. Johnson: My reply is bottom posted, to provide better
understanding to most readers of this message.
/s/ Bill Turner, wb4alm
On 1/3/23 11:38, P.O. Jonsson wrote:
Am 03.01.2023 um 16:13 schrieb Bill Turner, WB4ALM :
I would also like to suggest, that starting with Release 5, that
Do you mean modRexx for apache httpd? If so, that's on me. I know that
the build doc is sadly lacking, I'll put some work into it this month.
May I draft you as guinea pig/tester?
On 2023-01-03 07:13, Bill Turner, WB4ALM wrote:
4) It would be nice if RexxMods could be brought "up to
Thanks for catching this Rony! I will investigate as I have time along
with the problem with setup.rex on Windows using a non-existent FOP mirror.
Gil
On 1/3/2023 12:32 PM, Rony G. Flatscher wrote:
On 03.01.2023 15:00, Gilbert Barmwater wrote:
While being there we should also consider to
See below; trimmed some of the post...
On 1/3/2023 11:36 AM, Gilbert Barmwater wrote:
I hope to reply specifically later today. GB
On 1/3/2023 10:02 AM, P.O. Jonsson wrote:
Dear Gil and Rony, I have responded to your comments below.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
Forgot to supply 'bldoc.env' which you may find at the end of this post.
On 03.01.2023 18:32, Rony G. Flatscher wrote:
On 03.01.2023 15:00, Gilbert Barmwater wrote:
While being there we should also consider to rename the directory "docs/trunk/oorexx" to
"docs/trunk/Common_Content" as it gets
On 03.01.2023 15:00, Gilbert Barmwater wrote:
While being there we should also consider to rename the directory "docs/trunk/oorexx" to
"docs/trunk/Common_Content" as it gets used for all books. After doing so, we should also consider
to change all the xml-files that refer to "Common_Content"
> Am 03.01.2023 um 16:13 schrieb Bill Turner, WB4ALM :
>
>
> I would also like to suggest, that starting with Release 5, that a version be
> pre-compiled for LINUX MINT 21.
> I have found a number of folks who are not happy with some of the recent
> versions of UBUNTU, and many of them are
I hope to reply specifically later today. GB
On 1/3/2023 10:02 AM, P.O. Jonsson wrote:
Dear Gil and Rony, I have responded to your comments below.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
Am 03.01.2023 um 15:00 schrieb Gilbert Barmwater :
I was going to reply to the OP
Good points Bill. Many Linux(s) have more than one “current” version. One is the most current and the other is the LTS current version. Sometimes they are one and the same. What is our strategy for dealing with this environment?BruceSent by Magic!On Jan 3, 2023, at 7:13 AM, Bill Turner, WB4ALM
I would also like to suggest, that starting with Release 5, that a
version be pre-compiled for LINUX MINT 21.
I have found a number of folks who are not happy with some of the recent
versions of UBUNTU, and many of them are switching to LINUX MINT 17 or
LINUX MINT 21.
Even though the Linux
Dear Gil and Rony, I have responded to your comments below.
Hälsningar/Regards/Grüsse,
P.O. Jonsson
oor...@jonases.se
> Am 03.01.2023 um 15:00 schrieb Gilbert Barmwater :
>
> I was going to reply to the OP that I saw last night but then I saw this
> reply from Rony so I have added my comments
I was going to reply to the OP that I saw last night but then I saw this
reply from Rony so I have added my comments below.
On 1/3/2023 5:44 AM, Rony G. Flatscher wrote:
Thank you (and also Gil) for all of your efforts!
On 03.01.2023 00:18, ooRexx wrote:
My attempt to always have the
Having checked the Markdown with a plugin for Firefox I was surprised to see that SourceForge's
Markdown processor is quite buggy. As a result I had to play around with the text in the Wiki editor
until the results were comparable to release-steps.md.
Used the existing Wiki-entry named
Thank you (and also Gil) for all of your efforts!
On 03.01.2023 00:18, ooRexx wrote:
My attempt to always have the documentation built before windows and macOS build backfired.
"monitoring" the documentation build resulted in Windows and macOS building as soon as there was a
change to the
On 02.01.2023 19:30, Sahananda Sahananda wrote:
Having pressed send, I thought about this some more. Ideally we should have a set of samples
demonstrating the use of cUrl with ooRexx and I wonder if it wouldn't be really nice if they
demonstrated using a restful interface with the JSON class.
Thanks to everyone for the comments, information and ideas. Enclosed please find the next iteration
of that little script. Invoking it with "getOoRexxDocs.rex ?" yields the refurbished (hopefully
clearer) usage text:
getOoRexxDocs.rex [directory [needle]]
a utility to
I just committed a script that will monitor
svn.code.sf.net/p/oorexx/code-0/docs/trunk/tools/ and upload any new items to
oorexx-bildutils in the Files section. The script will be running once a day on
Jenkins and make sure the Files/oorexx-bildutils section is up to date to
minimise manual
20 matches
Mail list logo
