Hello Elias,
yes now it's working fine.
thanks,
Fausto
2015-04-14 15:40 GMT+02:00 Elias Mårtenson :
> OK, I believe I have fixed it. Please check the latest version in git.
>
> Regards,
> Elias
>
> On 14 April 2015 at 19:38, Fausto Saporito
> wrote:
>
>> Hello Jay,
>>
>> I'm using emacs and gn
Hi Peter,
I didn't mean it was not working, I meant I was not able :-)
Thanks for the doc, I read it several days ago, but for some reasons I was
not able to load the keyboard layout.
Now I deleted the previous file, and copied it again and everything seems
ok :-)
Thanks again,
Fausto
2015-04-
Well, yes. But why do you need it? Normally you wouldn't jump to lines in
the code by number, but rather using labels.
That said, it's Emacs so of course it can be done. You can simply add the
following to your Emacs init:
(defun em/gnu-apl-interactive-edit-mode-init ()
(linum-mode nil))
OK, I believe I have fixed it. Please check the latest version in git.
Regards,
Elias
On 14 April 2015 at 19:38, Fausto Saporito
wrote:
> Hello Jay,
>
> I'm using emacs and gnu-apl-mode but when I try to define the operator
> without the space I receive an error: "unable to parse".
>
> Generall
Hi Elias,
thanks a lot.
It should be possible to add also the line numbers when I edit a function
with emacs ?
thanks,
fausto
2015-04-14 13:41 GMT+02:00 Elias Mårtenson :
> That's probably a bug in the parsing on the Emacs side. I'll check it when
> I get back home tonight.
> On 14 Apr 2015 19
That's probably a bug in the parsing on the Emacs side. I'll check it when
I get back home tonight.
On 14 Apr 2015 19:39, "Fausto Saporito" wrote:
> Hello Jay,
>
> I'm using emacs and gnu-apl-mode but when I try to define the operator
> without the space I receive an error: "unable to parse".
>
>
Hello Jay,
I'm using emacs and gnu-apl-mode but when I try to define the operator
without the space I receive an error: "unable to parse".
Generally I use emacs, cause under Mac OS X I'm not able to use the APL
keyboard... I didn't find a way :-) (tried xmodmap, setxbdmap, etc).
I also tried wit
You shouldn't need a space after the right parenthesis.
This works for me:
z←(F scan)x;y
z←⊂y←↑x
∆1:→(0=⍴x←1↓x)/0
z←z,⊂y←y F↑x
→∆1
+scan 2 3 4
2 5 9
I had to:
- change " to ↓ for Drop
- use monadic ↑ instead of ⊃ for First (this is a Dyalog "migration
level" thing)
- replace modified assi
Hi Jürgen,
thanks... my fault. I wrote without space after the right parenthesis and
the interpret gave me an error. I.e. ∇z←(F scan)x;y
I didn't notice the blank space was mandatory.
regards,
Fausto
2015-04-14 12:58 GMT+02:00 Juergen Sauermann
:
> Hi Fausto,
>
> page 30 (Defined Functions
Hi Fausto,
page 30 (Defined Functions and Operators) explains it.
In your example below F is expected to be a function because it
is inside () in the header while the variable(s) are outside ().
/// Jürgen
On 04/14/2015 12:42 P
Hello all,
sorry if I bother you again, but I tried to find some hints in the APL2
Language Reference Manual without luck.
In the Sullivan's paper, there's the reference to a "scan" operator quite
fast more suited to be used with his multi precision package.
This is its definition:
∇ z←(F scan)x
11 matches
Mail list logo
