Re: [Bug-apl] Another attention signal issue

Hi, the issues should be fixed in SVN 386. When large value are printed then the computation of the output as well as the printout itself can be interrupted (two ^C within 500 ms). There is still some latency after the ^Cs because some internal functions are not interruptible, but it is much sm

Re: [Bug-apl] Another attention signal issue

Good to hear that a solution is in sight. :) On Tue, Jul 22, 2014 at 12:04 PM, Juergen Sauermann < juergen.sauerm...@t-online.de> wrote: > Hi David, > > thank you very much. I read the paragraph below several times. > Unfortunately > the behavior of readline is somewhat different. The problem s

Re: [Bug-apl] Another attention signal issue

Hi David, thank you very much. I read the paragraph below several times. Unfortunately the behavior of readline is somewhat different. The problem seemed to be that signal handling is "too transparent" in that it ignores settings made in the signal handler. But I am on the way towards a solut

Re: [Bug-apl] Another attention signal issue

J'uergen, I noticed this paragraph in the readline documentation: " Readline contains an internal signal handler that is installed for a number of signals (`SIGINT', `SIGQUIT', `SIGTERM', `SIGALRM', `SIGTSTP', `SIGTTIN', and `SIGTTOU'). When one of these signals is received, the signal handler

Re: [Bug-apl] Another attention signal issue

Hi Blake, I tried, but it did not work. The deeper I go into readline the more weird it gets. If I do nothing then I get the first ^C delivered as signal but not subsequent ones. I would have preferred if two ^Cs (i.e. INTERRUPT rather than ATTENTION) would stop printouts, but readline deliv

Re: [Bug-apl] Another attention signal issue

Hi Blake, thanks for that information. Actually the SIGINT is delivered to GNU APL as expected. The problem is that when I return from the GNU APL SIGINT handler then readline seems to be blocked in the old readline() call and returns only after another char (any char - does not have to be new

Re: [Bug-apl] Another attention signal issue

This is correct. Emacs mode disables readline (it could work with it too, but it's more stable without it). Regards, Elias On 22 Jul 2014 06:01, "David B. Lamkins" wrote: > Emacs mode passes --rawCIN to APL. If I'm not mistaken, that bypasses > readline. Therefore you should be able to eliminate

Re: [Bug-apl] Another attention signal issue

Emacs mode passes --rawCIN to APL. If I'm not mistaken, that bypasses readline. Therefore you should be able to eliminate or replace readline without consideration for emacs mode. On Mon, 2014-07-21 at 19:39 +0200, Juergen Sauermann wrote: > Long term I will most likely replace readline because s

Re: [Bug-apl] Another attention signal issue

Does this help? This may be related to the cooked/uncooked/rare terminal modes; ^C does not always send a signal. It seems likely that readline uncooks the terminal, and thus any signals caused by keyboard

Re: [Bug-apl] Another attention signal issue

This too may be applicable: http://www.delorie.com/gnu/docs/readline/rlman_43.html On Mon, Jul 21, 2014 at 1:12 PM, Blake McBride wrote: > Does this help? > > This may be related to the cooked/uncooked/rare >

Re: [Bug-apl] Another attention signal issue

Does this help? This may be related to the cooked/uncooked/rare terminal modes; ^C does not always send a signal. It seems likely that readline uncooks the terminal, and thus any signals caused by keyboard

Re: [Bug-apl] Another attention signal issue

Hi David, I see. The problem is that the line input (readline) does not return even though I tell it to (by setting *rl_done* in the signal handler for ^C). I haven't found a way to fix this (hints more than welcome). This could also be caused by terminal settings ("cooked mode") but I thought

Re: [Bug-apl] Another attention signal issue

Thanks, Jüergen. The real issue, from my perspective, is that APL doesn't report the ATTENTION message until it sees a newline on input. It seems to me that typing a ^C should immediately suspend execution and show the ATTENTION message. On Mon, 2014-07-21 at 18:23 +0200, Juergen Sauermann wrote:

Re: [Bug-apl] Another attention signal issue

Hi David, I have changed readline to display a new line right after ^C, see SVN 382. For reasons that I don't fully understand, the next character after ^C will be eaten by readline; I tried a number of things to prevent this but haven't succeeded. I believe readline will be one of the next t

[Bug-apl] Another attention signal issue

When the session is not executing APL code, the attention signal is not handled until the next newline. To see this, enter the characters Control-C, 1, Return. -- "The secret to creativity is knowing how to hide your sources." Albert Einstein http://soundcloud.com/davidlamkins http://rever