[Info-vax] Latest GNU Readline Library available for OpenVMS

[A famous IT technical writer]

On Jan 24, 11:48 pm, A famous IT technical writer
<Philippe.vout... at laposte.net> wrote:
> On Jan 21, 4:33 pm, A famous IT technical writer
>
> <Philippe.vout... at laposte.net> wrote:
> > This post is especially dedicated to those porting Opensource codes or
> > writing portable code.http://vouters.dyndns.org/tima/OpenVMS-readline-Latest_Linux_libreadl...
> > Philippe
>
> A night made portable programming example using the GNU Readline
> Library is available athttp://vouters.dyndns.org/tima/Linux-HP-UX-OpenVMS-libreadline-GNU_re...
>
> Currently this programming sample has been successfully tested on both
> Linux Fedora 16 and OpenVMS IA64 V8.3-1H1. The produced sys
> $library:readline.tlb was missing the correct file protections so that
> it could be used by any account on a cc command. This has been
> corrected in the VMS descrip.mms producing the GNU Readline output
> files in their final location. I now realize I am also perhaps missing
> the correct VMS file protections when copying this software C headers
> into HP GNV /usr/include. Feedback by users would be welcomed.
>
> The code at this URL above is awaiting for this week-end to come to be
> also fully tested on HP-UX B.11.31 IA64 using the provided
> information.
>
> Philippe

libreadline is designed to emit a BELL sound if the history buffer
limits are attempted to be overcome with the arrow keys. This BELL
sound fprint'ed to stderr was causing a new line on OpenVMS with the
cursor one line underneath ifs expected position. For example, if your
first command was 1+2 and you pressed the up arrow to recall an
history non existant command, the display would look like:

PROMPT : 1+2

                          <cursor here>

If you typed exit where the cursor is, your last command would be
'1+2exit'. This problem specific to OpenVMS has just been corrected by
avoiding the problematic fprintf(stderr,BELL).



A new patch has been produced.

Philippe