Thank you.
On Mon, Dec 26, 2016 at 11:01:17PM +0100, Juergen Sauermann wrote:
> Hi David,
>
> fixed in SVN 832 (I hope). Should have been only a warning without an effect.
>
> /// Jürgen
>
>
> On 12/26/2016 10:44 PM, David B. Lamkins wrote:
>
> The recent addition to the user preferences
Hi
- debian testing or stable
- ")copy myworkspace" doesn't copy functions from workspace
- ")copy myworkspace myfunction" does copy "myfunction"
This started in the first few versions after Version / SVN: 1.6 / 825M.
On 26 December 2016 at 20:09, Juergen Sauermann wrote:
> Kacper: you can now enable change of ⎕PW via the WINCH signal. This may not
> work on all platforms, therefore is has to be enabled in one of your
> preferences files.
Works great, thanks.
It's okay that it requires enabling, it's not someth
Hi,
I assume --without-libapl should be the same as --with-libapl=no, as it
logically follows.
I guess there is a bug either in the build system or in
autoconf/automake tools. I've never written scripts for them so I can't
judge; but all my previous experience building software with ./configure
s
Hi Alexey,
first of all, --without-libapl is not a
valid ./configure option, and there is no mentioning
of --without-libapl
in README-2-configure.
Not building libapl is the default, so instead of
saying --without-libapl you
Hi David,
fixed in SVN 832 (I hope). Should have been only a warning
without an effect.
/// Jürgen
On 12/26/2016 10:44 PM, David B.
Lamkins wrote:
The recent addition to the user preferences parser causes APL to report
The recent addition to the user preferences parser causes APL to report that
the 'Profile' keyword is invalid.
Hi,
It seems what even if I set
./configure --without-libapl
the configure scripts still reports
checking if we want to build libapl.so... yes
--
Br,
/Alexey
Hi Alexey, Kacper,
I have made some changes related to ⎕PW in SVN 830.
Alexey: you can now also specify the inital ⎕PW in your
preferences file(s) instead
of on the command line.
Kacper: you can now enable change of ⎕PW via the WINCH
There are a couple of existing guidelines. If you poke around in wslib5, you'll
see examples of both.
http://www.gnu.org/software/apl/Library-Guidelines.html
This is intended for modern APLs (i.e. those which are able to load APL
programs as Unicode) in general; this document links to another
Hi,
The question is rather silly but raised since earlier in discussion
Jurgen mentioned what the workspaces is the outdate way to work with
APL.
So what is the current (modern) ways supported by GNU APL would be?
I could imagine the organization of the program the following:
1) set of UTF-8 text
11 matches
Mail list logo
