[Bug-apl] [gnu.org #1374831] Re: meta-bug: mailing list search engine

[Andrew Engelbrecht via RT]

On Sat Apr 06 11:55:00 2019, m...@xn--jrgen-sauermann-zvb.de wrote:

> On 4/6/19 4:57 PM, Patrick Giagnocavo wrote:

> > On the second page, the results page , enter a different search term.
> >
> > You will get zero results because this result page does not properly
> > link to/access the archives and thus has 0 documents to search:
> >
> > "Results:
> >
> > References: [ (can't open the index) ]
> >
> > No document matching your query

Hello Patrick,

This is a known issue with our Namazu instance. There isn't a fix for this 
upstream, but we plan on resolving this issue along with our mailing list and 
mail server upgrades in the coming months. In the meantime, you can hit the 
back button to do a new search on mailing lists. Sorry about that. : /

Thanks,
Andrew

[Bug-apl] 1 2 3 + 3 ⍬ 5

[Hudson Flavio Meneses Lacerda]

Hi.


This is not the newest CVS version, but, if the bug still exists, the
test is simple enough:

  29⎕cr 1 2 3 +¨ 3 '' 5
┏→━━┓
┃4 ┏⊖┓ 8┃
┃  ┃0┃  ┃
┃  ┗━┛  ┃
┗∊━━┛


1 2 3 + 3 ⍬ 5   

==
Assertion failed: !sub_val->is_simple_scalar()
in Function:  PointerCell
in file:  PointerCell.cc:30

Call stack:


-- Stack trace at PointerCell.cc:30

0xB7081A63 __libc_start_main
0x808FA86  main
0x8294C35   Workspace::immediate_execution(bool)
0x80FAC94Command::process_line()
0x80FB5EA Command::do_APL_expression(UCS_string&)
0x80FADB3  Command::finish_context()
0x8109E48   Executable::execute_body() const
0x82140CCStateIndicator::run()
0x81675F5 Prefix::reduce_statements()
0x81605A0  Prefix::reduce_A_F_B_()
0x820EB89   Bif_F12_PLUS::eval_AB(Value_P, Value_P)
0x8208161ScalarFunction::eval_scalar_AB(Value_P, Value_P,
ErrorCode (Cell::*)(Cell*, Cell const*) const) 0x82078EF
ScalarFunction::do_scalar_AB(ErrorCode&, Value_P, Value_P, ErrorCode
(Cell::*)(Cell*, Cell const*) const) 0x8169254
PointerCell::PointerCell(Value*, Value&) 0x80A6791
do_Assert(char const*, char const*, char const*, int)


SI stack:

Depth:  2
Exec:   0x9b13208
Safe exec:  0
Pmode:  ◊  1 2 3 + 3 '' 5
PC: 3 (5) ENDL
Stat:   1 2 3 + 3 '' 5
err_code:   0x0

Depth:  1
Exec:   0x9afe9e8
Safe exec:  0
Pmode:  ◊  1 2 3 + 3 ⍬ 5
PC: 5 (7) ENDL
Stat:   1 2 3 + 3 ⍬ 5
err_code:   0xA01
thrown at:  PointerCell.cc:30
e_msg_1:'Assertion failed'
e_msg_2:''
e_msg_3:''

Depth:  0
Exec:   0x9b0fb78
Safe exec:  0
Pmode:  ◊  1 2 3 + 3 ⍬ 5
PC: 5 (7) ENDL
Stat:   1 2 3 + 3 ⍬ 5
err_code:   0xA01
thrown at:  PointerCell.cc:30
e_msg_1:'Assertion failed'
e_msg_2:''
e_msg_3:''


==
  

[Bug-apl] ⎕plot focus

[Hudson Flavio Meneses Lacerda]

Hi.

The ⎕plot window, just after being drawn, jumps to the background
(minimized). Is there any way to control its focus from GNU APL?

(I do not have GNOME; it looks like FluxBox is not 100% compatible with
new GNOME versions.)

(My workaround is to memorize the layer as the top.)

Hudson

Re: [Bug-apl] ⎕plot focus

[enztec]

i'm assuming you are using apl in an xterm

depending on your 'desperation' or if there isn't a real other fix :)

a workaround might be using wmctrl to focus the window using apl to execute 
wmctrl after your ⎕plot line - i have various fluxbox hot keys (in the 
~/.fluxbox/keys file) to focus an irssi window or mplayer window and see no 
reason it can't focus the apl xterm - but you have to give the xterm a title 
you can identify with   wmctrl -leither as fluxbox hot key   or   in apl 
code

wmctrl -l
parse out for window want  - for example   0x02cd
wmctrl -i -a  0x02cd

i don't use gnome but i recall there is a gconf-editor that might have some pref
i don't think xdotool can do what wmctrl can do here

On Mon, 8 Apr 2019 13:12:44 -0300
Hudson Flavio Meneses Lacerda  wrote:

> Hi.
>
> The ⎕plot window, just after being drawn, jumps to the background
> (minimized). Is there any way to control its focus from GNU APL?
>
> (I do not have GNOME; it looks like FluxBox is not 100% compatible with
> new GNOME versions.)
>
> (My workaround is to memorize the layer as the top.)
>
> Hudson
>
>
>

Re: [Bug-apl] ⎕plot focus

[Christian Robert]

Well, you did not say the linux distribution you are using ...

I use Fedora 28 with KDE and it does not show this kind of behavior with 
Quad-plot

Xtian.

On 2019-04-08 12:12, Hudson Flavio Meneses Lacerda wrote:

Hi.

The ⎕plot window, just after being drawn, jumps to the background
(minimized). Is there any way to control its focus from GNU APL?

(I do not have GNOME; it looks like FluxBox is not 100% compatible with
new GNOME versions.)

(My workaround is to memorize the layer as the top.)

Hudson

Re: [Bug-apl] try-GNU-APL

[Dr . Jürgen Sauermann]

  
  
Hi Blake,
  
  never mid. I have added an APL popup window that one can use
  for copy-and-paste APL characters.
  
  I am working on an improved keyboard that pushes the characters
  clicked into the APL window. It works so far for computing the
  proper
  character, but I am struggling with hot to transfer the character
  from
  the keyboard window to the APL window.

I tried a number of alternatives along the lines of:

   var form =
window.opener.document.forms["APL_input"]["in_form"];
   form.innerHTML = form.innerHTML + key;
  
While key is correct at this point, it never arrives in the
try-GNU-APL.html window, nor does
the above raise an error. I t very much looks like the destination
being is copied rather
than being referenced so that the key lands in the copy and has no
impact on the original.

/// Jürgen


On 4/7/19 10:49 PM, Blake McBride
  wrote:


  
  
Now that I think about it a little more.  I don't
  think the link I gave you will help.  I think
  shellinabox allows an APL program to run over the net in a
  browser, but it didn't allow APL characters to be displayed or
  entered.
  
  



  On Sun, Apr 7, 2019 at 11:02
AM Blake McBride  wrote:
  
  

  Hi Jürgen,

  
I
think you need an akt-like thing for the browser.  I
know it can be done because I've done it before. 
See https://github.com/shellinabox/shellinabox.git 
  That works great with GNU APL!


Can't do much right now, working on https://github.com/blakemcbride/Build


Thanks!


Blake


  
  
  
On Sun, Apr 7, 2019 at
  10:49 AM Dr. Jürgen Sauermann 
  wrote:


   Hi Blake,
  
  I see. Not really sure what a good solution would
  be, but my current thinking is that the page
  should get a separate column on the left side with
  a number of links to other pages that are
  related to GNU APL (GNU APL home, GNU APL
  community, Bits-and-Pieces, info manual,
  etc.).
  
  One of the links could be a copy to a separate
  window with an APL keyboard. Or maybe a
  "Keyboard" button right to the "Enter:" button. I
  am not a web designer so I have to figure how
  to do that (ideally such that a click in the
  keyboard window is pushed into the input field).
  
  Any help is welcome (the current try-GNU-APL page
  is websock/client/apl_js.html in SVN).
  
  Best Regards,
  /// Jürgen
  

On
  4/7/19 5:29 PM, Blake McBride wrote:


  
Hi Jürgen,
  

  I
  kind of got all of that.  Here is the
  problem:
  

  I
  use "akt" to get to APL characters.  I
  don't use any keyboard configuration. 
  Likewise, those new to APL that wish to
  "try" it are not going to have any special
  keyboard setup either.  The will be using
  tryapl.org
  with a regular browser on a
  not-specially-configured keyboard. 
  Although I easily get all that you said,
  the people interested in "trying" APL
  won't.
  

  Thanks.
  

  Blake
  

Re: [Bug-apl] try-GNU-APL

[Elias Mårtenson]

Isn't there some security thing in Javascript that prevents one window from
communicating with another? I think that's what you're running into.

You'll probably have an easier time if you put the virtual keyboard on the
same page.

Regards,
Elias

On Tue, 9 Apr 2019, 04:15 Dr. Jürgen Sauermann, 
wrote:

> Hi Blake,
>
> never mid. I have added an APL popup window that one can use
> for copy-and-paste APL characters.
>
> I am working on an improved keyboard that pushes the characters
> clicked into the APL window. It works so far for computing the proper
> character, but I am struggling with hot to transfer the character from
> the keyboard window to the APL window.
>
> I tried a number of alternatives along the lines of:
>
>
>
> *   var form =
> window.opener.document.forms["APL_input"]["in_form"];
> form.innerHTML = form.innerHTML + key; *
> While key is correct at this point, it never arrives in the
> try-GNU-APL.html window, nor does
> the above raise an error. I t very much looks like the destination being
> is copied rather
> than being referenced so that the key lands in the copy and has no impact
> on the original.
>
> /// Jürgen
>
>
> On 4/7/19 10:49 PM, Blake McBride wrote:
>
> Now that I think about it a little more.  I don't think the link I gave
> you will help.  I think shellinabox allows an APL program to run over the
> net in a browser, but it didn't allow APL characters to be displayed or
> entered.
>
>
> On Sun, Apr 7, 2019 at 11:02 AM Blake McBride  wrote:
>
>> Hi Jürgen,
>>
>> I think you need an akt-like thing for the browser.  I know it can be
>> done because I've done it before.  See
>> https://github.com/shellinabox/shellinabox.git  That works great with
>> GNU APL!
>>
>> Can't do much right now, working on https://github.com/blakemcbride/Build
>>
>> Thanks!
>>
>> Blake
>>
>>
>> On Sun, Apr 7, 2019 at 10:49 AM Dr. Jürgen Sauermann <
>> mail@jürgen-sauermann.de> wrote:
>>
>>> Hi Blake,
>>>
>>> I see. Not really sure what a good solution would be, but my current
>>> thinking is that the page
>>> should get a separate column on the left side with a number of links to
>>> other pages that are
>>> related to GNU APL (GNU APL home, GNU APL community, Bits-and-Pieces,
>>> info manual,
>>> etc.).
>>>
>>> One of the links could be a copy to a separate window with an APL
>>> keyboard. Or maybe a
>>> "Keyboard" button right to the "Enter:" button. I am not a web designer
>>> so I have to figure how
>>> to do that (ideally such that a click in the keyboard window is pushed
>>> into the input field).
>>>
>>> Any help is welcome (the current try-GNU-APL page is
>>> *websock/client/apl_js.html* in SVN).
>>>
>>> Best Regards,
>>> /// Jürgen
>>>
>>>
>>> On 4/7/19 5:29 PM, Blake McBride wrote:
>>>
>>> Hi Jürgen,
>>>
>>> I kind of got all of that.  Here is the problem:
>>>
>>> I use "akt" to get to APL characters.  I don't use any keyboard
>>> configuration.  Likewise, those new to APL that wish to "try" it are not
>>> going to have any special keyboard setup either.  The will be using
>>> tryapl.org with a regular browser on a not-specially-configured
>>> keyboard.  Although I easily get all that you said, the people interested
>>> in "trying" APL won't.
>>>
>>> Thanks.
>>>
>>> Blake
>>>
>>>
>>> On Sun, Apr 7, 2019 at 10:11 AM Dr. Jürgen Sauermann <
>>> mail@jürgen-sauermann.de> wrote:
>>>
 Hi Blake,

 there is an input field (after the text"APL Input:") at the bottom of
 the page.
 You enter your APL command or expression into that field and then press
 enter
 on your keyboard or push the button labelled "Enter". The text entered
 then goes
 straight to the GNU APL interpreter.

 If your keyboard is configured accordingly, then you move the cursor
 over the input
 field (so that it gets the input focus) and then simply type the APL
 characters (using Ctrl-
 or Alt- or whatever your keyboard configuration requires). The normal
 keyboard
 configuration for GNU APL should do it.

 Without a proper keyboard configuration you can first enter command
 *]keyb* to
 display an APL keyboard in the APL output. From that output you can
 then copy
 and paste individual APL characters to the input field (in my browser
 you mark the text
 and then copy it with the middle mouse button, like it is commonly done
 in X-based systems).

 Likewise you can copy and paste longer APL input lines from other web
 pages that display
 APL code (in UTF-8 encoding).

 Best Regards,
 /// Jürgen



 On 4/7/19 4:37 PM, Blake McBride wrote:

 Interesting, but I can't figure out how to input APL characters.

 --blake


 On Sat, Apr 6, 2019 at 1:41 PM Dr. Jürgen Sauermann <
 mail@jürgen-sauermann.de> wrote:

> Hi,
>
> inspired by Dyalog's https://tryapl.org/ I have set up a small server
> with *try-GNU-APL*. Not as fancy as tryapl.