Definitely a big improvement.
There is still the problem that Publican doesn't produce a decent index
section. You can't go to the
F's without scrolling through all the pages starting at "%"
--
Mark Miesfeld
On Sun, Dec 15, 2013 at 9:50 AM, David Ashley wrote:
> All -
>
> I fixed the syntax
On Sun, Dec 15, 2013 at 8:13 AM, Oliver Sims <
oliver.s...@simsassociates.co.uk> wrote:
> Any chance of somewhow providing a reference to Chapter 2 of the Rexx
> Programmer Guide?
>
Sure there is a chance.
I've been working on this over the weekend. When I get everything working
I was going to
All -
I fixed the syntax errors that prevented rexxref from building last
night. I then put the latest build of rexxref up on the Build machine.
I also made a quick scan of the whole document this morning. With the
switch to publican our docs now look really professional. And the
content is not b
Any chance of somewhow providing a reference to Chapter 2 of the Rexx
Programmer Guide? This is a good "starter" for any newbie, and saves them
having to fossick around to find the right documentation. For example, I
think this is the only place that mentions that the file extension of an
ooRexx pr
If you are referring to 'umask u-x,g=x,o+w', this removes execute
permission for the owner ('user'), adds write permission for 'others'
and sets the group permissions to be only the execute permission,
removing any others. IOW, the executable bit is set for the group and
all other group permis
It works as I would have expected now.
David Ashley
On Sun, 2013-12-15 at 15:50 +0100, Uli Zinngrebe wrote:
> On Saturday 14 Dec 2013 18:12:11 Rick McGuire wrote:
> > Ok, the fix has been committed to both trunk and branch. Someone needs to
> > check this out on a non-Windows system.
> >
>
> F
Well, x86 architecture compatible.
Rick
On Sun, Dec 15, 2013 at 10:22 AM, Mike Cowlishaw wrote:
>
>
> The readme in question was the one for Windows, not the general
> requirements. The only hardware we support it on currently is Intel x86,
> so I'm just trying to get that wording sorted out.
The readme in question was the one for Windows, not the general requirements.
The only hardware we support it on currently is Intel x86, so I'm just trying to
get that wording sorted out. I don't think anybody's attempted to build it yet
for the Surface RT, but I'm not even sure you could insta
Rene,
The readme in question was the one for Windows, not the general
requirements. The only hardware we support it on currently is Intel x86,
so I'm just trying to get that wording sorted out. I don't think anybody's
attempted to build it yet for the Surface RT, but I'm not even sure you
could
On Saturday 14 Dec 2013 18:12:11 Rick McGuire wrote:
> Ok, the fix has been committed to both trunk and branch. Someone needs to
> check this out on a non-Windows system.
>
File permissions now adapt to umask settings.
In the second example I'm not sure whether umask means
- that the execut
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On 12/15/2013 02:49 PM, René Jansen wrote:
> I suggest we state the ISA's where it is tested on, their current
> OS support (for example, z has Linux but not z/OS), and the fact
> that we have pre-built binaries for Linux (on Intel) and WIndows
> (IA
Also, it is fairly arbitrary, because it currently builds on ARM, z, PPC,
X-86-32, X86-64, etc.
That RexxLA only chooses to support it on Windows and Linux is also fairly
arbitrary, but doubtlessly a given qua resource availability, although I
distinctly remember the efforts to support AIX-PPC
When reviewing Patch file 189 (let's see if this creates a real link for the
mailing list.[patches:#189]), I noticed we give the hardware requirements as:
IBM-compatible, Pentium or AMD processor, or higher. Both 32-bit and 64-bit
processors are supported.
It's been a long time since I've hea
13 matches
Mail list logo
