🚀 go-pugleaf

> 
> 
> 			There are a couple of bugs in this package of programs.
> The first one is in the make file for ` rf.c '. The make file should include
> termcap for the libraries to be used. Eg, LIBS = -lcurses -ltermcap. The
> second problem seems to be two functions which are not part of our curses
> library ( BSD 4.3 ). Namely, idlok() & setscrreg(), thus rf.c won't compile.
Replace idlok by newwin and setscreg by subwin. Furthermore replace the lines
reading
X	attron(A_REVERSE);
by
X	standout();
and the lines reading
X	attroff(A_REVERSE);
by
X	standend();
This works fine for me under BSD4.3. A pity there isn't yet an option to
add entries to rf_data (or did I miss something??)
> 	Finally, there are a couple of undefined variables in ` rolo.c '. If
> any one has fix for these last two items please let know what they are.
You're referring to quite another program here. There were so many different
programs under this name that you should be specific as to which one you
refer (they ALL compiled o.k. here).
By the way does anybody know about a version of rolo ( or another adressbase)
that lets you add a substantial amount of text under COMMENTS ?
> 
> 						paul.......
> ================================================================================
> Paul Zemancheff		      PHONE: +61 3 487 9263
> CSIRO Division of	      ACSNET or CSNET: paz@mimir.dmt.oz
> Manufacturing Technology,     ARPA: paz%mimir.dmt.oz@uunet.uu.net
> Melbourne, Australia.	      UUCP: {uunet,ukc,mcvax}!munnari!mimir.dmt.oz!paz
> ================================================================================
fmr@cwi.nl
-- 
It is better never to have been born. But who among us has such luck?

In article <1081@mimir.dmt.oz> paz@mimir.dmt.oz (Paul Zemancheff) writes:
>
>			There are a couple of bugs in this package of programs.
>The first one is in the make file for ` rf.c '. The make file should include
>termcap for the libraries to be used. Eg, LIBS = -lcurses -ltermcap. The
>second problem seems to be two functions which are not part of our curses
>library ( BSD 4.3 ). Namely, idlok() & setscrreg(), thus rf.c won't compile.

  It sounds as though the options you are using are not correct for your
system, as I have done it on SysV, Xenix and BSD without problems.  I
sure hope VMS works, too, because it's a useful program. 

  For Xenix, V7 and BSD, I used option TERMCAP, and both curses and
termcap libraries. On SysV the termlib is usually bundled with curses,
so I used TERMLIB and just the curses library.

  Hope this helps.
PS: our mailer won't have your address, so I'm posting this.
-- 
	bill davidsen		(wedu@ge-crd.arpa)
  {uunet | philabs | seismo}!steinmetz!crdos1!davidsen
"Stupidity, like virtue, is its own reward" -me

In article <443@sering.cwi.nl> fmr@cwi.nl (Frank Rahmani) writes:
>> library ( BSD 4.3 ). Namely, idlok() & setscrreg(), thus rf.c won't compile.
>Replace idlok by newwin and setscreg by subwin. Furthermore replace the lines

idlok != newwin and setscreg != subwin

idlok(win,flag)
	If flag is enabled, curses will concider using hardware
	"insert/delete line" terminal features.  If disabled,
	it will seldom use it.  This option is always concidered.
	It needs to be enabled only if your application needs it,
	such as a screen editor.  It tends to be annoying when
	used in applications where it isn't really needed.  If it
	cannot be used, curses will redraw the changed lines.

setscrreg(top,bot)
wsetscrreg(win,top,bot)
	These allow a user to set a software scrolling region in a
	window.  top and bot are line numbers of the top and bottom
	margin of the scrolling region.  This has nothing to do with
	the terminals physical scrolling capability.


Hope this helps.  This is from the SVR3 curses documentation.

David Connet
ihnp4!ihlpe!dcon

In article <443@sering.cwi.nl>, fmr@cwi.nl (Frank Rahmani) writes:
> ...
> This works fine for me under BSD4.3.

	I'm glad someone made it BSD-compatible, insofar as the curses
implementation is concerned.  Unfortunately, neither myself nor anyone
else in my organization had enough BSD experience to offer the correct
BSD options.

> A pity there isn't yet an option to
> add entries to rf_data (or did I miss something??)

	Actually, most users prefer to simply edit the database file
using vi or emacs.  I do have a shell/awk script which inserts new
entries in the database file (after verifying that no duplication exists),
but since it was a quick hack and was not "idiot-proof", I elected not to
include it with the comp.sources submission.  It's quite simple to write
a script using sed or awk for this purpose, and a script is indeed
appropriate here since execution speed is not important for adding new
entries.  Modifying existing entries using a script is a little trickier,
but not that big a deal (I find the entry to be modified and write it to
a temp file, then I write the database less the modified entry to a second
temp file; the temp file containing the single entry is modified using an
invocation of vi, followed by appending it to the other temp file, which
in turn overwrites the original database file.
	Since I wanted to keep rf(1L) "simple", I never felt like writing
the C code necessary to write/edit/update the database file; this would
probably require more code that the original rf.c module.
	Incidently, when I wrote rf(1L) in 1985, it was my first use of
curses(3X) under SVR2.  The program was an exercise which paid off well;
properly using curses was all downhill after I understood what was
necessary to write the program.

<>  Larry Lippman @ Recognition Research Corp., Clarence, New York
<>  UUCP:  {allegra|ames|boulder|decvax|rutgers|watmath}!sunybcs!kitty!larry
<>  VOICE: 716/688-1231        {hplabs|ihnp4|mtune|utzoo|uunet}!/
<>  FAX:   716/741-9635 {G1,G2,G3 modes}   "Have you hugged your cat today?"