From: Simon Strandgaard <0bz63fz3m1qt3001@...> Date: 2003-07-02T15:54:59+09:00 Subject: Re: [ANN] Aeditor-0.1 is unleashed On Wed, 02 Jul 2003 14:58:45 +0900, Stephen Lewis wrote: > On Wed, 2 Jul 2003 08:39:16 +0900 > Mark Wilson wrote: > >> >> This is first time I release a ruby-package. I am therefore very >> >> curious >> >> about install issues.. Tell me if installation works for you :-) >> >> Please tell me your ideas/opinions/suggestions/flames ? >> > [snip] >> >> Hi, >> >> I had to add 'aeditor/' to the require statements. I then had an error >> >> when I tried to run it. > > Same problem here - running your "aeditor" script doesn't work ( > it's unable to find the files required from main.rb ). What does work > is changing to the installed aeditor directory and running "main.rb" > manually. Interesting, running the 'aeditor' script works here? I guess I have an earlier installation, where I didn't have any 'lib/aeditor' dir is screwing up here. I better reinstall ruby+aeditor on my machine and look closer at the problem. > A few other things that I noticed fairly quickly: > 1) How should I quit? - I found many ways to "quit" through > unhandled exceptions (escape enter, shift-fkey, ctrl-c enter etc > :) Escape (ascii code 27) should terminate the application. The story about Ncurses and the escape key is wierd: I think it is trying to compose a escape code, if no cobination key is pressed within a second, the ascii code 27 should be omitted ? At the moment ascii-code 27 is the only way to terminate it. > 2) Running in a large xterm, the top status bar seems to have a hard > coded width Admitted.. This is hardcoded, I will fix it later. > 3) No backspace (or foward-delete)? ctrl-h didn't work either The delete-key is not yet supported. The backspace-key (ascii code 9) should be bound to cmd_backspace. Maybe your backspace-key is generating something else ? Can tell me what happens in the 'log' file if you press Escape ? The message should look like the following: Control#dispatch: Unknown event occured ncurses-event = xxx > 4) the "play" action raises an uncaught exception if nothing has been > recorded yet. On that note, it might be nice to change "record" to > "stop" during the record operation Oh... my fault, will fix it :-) > 5) Single line is fairly sluggish (I know, I know, premature > optimisation :) three lines is the minimum: 2 lines containing menues, 1 line containing text. Rigth now it raises an exception if one attempt to make the window smaller than 3 lines. I assume you are in this '3 line' situation ? 'sluggish' => slow ? Is it slower than a window spanning multiple lines ? > Looks promising tho, I'll be keeping an eye on development. I quite > like the period as an EOL marker - hadn't seen that before. EOL markers should be an enable/disable option :-) -- Simon Strandgaard