HP3000-L Archives

September 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
"COLE,GLENN (Non-HP-SantaClara,ex2)" <[log in to unmask]>
Reply To:
COLE,GLENN (Non-HP-SantaClara,ex2)
Date:
Thu, 28 Sep 2000 12:56:03 -0600
Content-Type:
text/plain
Parts/Attachments:
text/plain (39 lines)
Barry writes:
> Even if you don't read the communicator, you can find a wealth of
>  information by doing ":help functions" at the CI prompt.

then Wirt:
> Yes, that's true -- if you can remember the "functions" part of the help
> command.

If you forget this, you can try the back door using a known function name.
Using MPEX, that's

   /%print cicat.pub.sys;search=cl "ltrim";prev="\ENTRY"
   \ENTRY=FUNCTIONS
   LTRIM              Trims left end of string
   \ENTRY=LTRIM
   Syntax:     LTRIM(string[,trimstr])
   Example:    'X'+ltrim(' abc')
   /

> The other day, I couldn't, and it just about drove me crazy. There's no
way
> to get to the list of functions other than to remember ":help functions"
> that I could find.

Of course, that's the problem with most "exact keyword" lookup, especially
one like this with little true hierarchy built in.  (The FUNCTIONS entry
above appears on the same level as LTRIM.)

> If Jeff Vance were still listening to this group, I would suggest that the
> word "FUNCTIONS" be put under the system programming group (PROGRAMMING),
> just so that those of us who are growing more elderly by the day can have
> their memories jogged a little more easily -- and at the same time create
a
> more logical top-down route to the functions list.

Good idea!  Perhaps VARIABLES (for the system vars) could be added as well.

--Glenn

ATOM RSS1 RSS2