home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!paladin.american.edu!gatech!usenet.ins.cwru.edu!agate!ucbvax!lrw.com!leichter
- From: leichter@lrw.com (Jerry Leichter)
- Newsgroups: comp.os.vms
- Subject: RE: More than 1 line of command history buffer
- Message-ID: <9212311252.AA06668@uu3.psi.com>
- Date: 31 Dec 92 11:52:46 GMT
- Sender: daemon@ucbvax.BERKELEY.EDU
- Distribution: world
- Organization: The Internet
- Lines: 30
-
-
- I am reading a command line in my program, using C RTL function gets()
- (I suspect that this just does a plain buffered read from the terminal
- with NL as terminator, but I am not sure which VMS system function
- this may be).
-
- Well, ultimately perhaps - but it's a LONG way down the hierarchy to get
- there.
-
- I like to have the command line editing provided courtesy of VMS
- system read procedure, and the fact that I can retrieve the previously
- used command line using the up-arrow key; however, I am spoiled by the
- DCL 20-line command history (and the readline library I am using on
- Unix that remembers commands across login sessions). Is there a
- simple way to increase the command history list size, so that more
- than one last command is remembered?
-
- Of course I could switch to unbuffered/raw read and do the line
- editing and command line history myself, but I would rather not, if I
- don't have to.
-
- Use SMG$READ_COMPOSED_LINE. You can use this function without using SMG to
- maintain your whole screen - you'll need to make a couple of auxiliary calls
- to create some basic SMG objects, but that's it.
-
- (The only other alternative is to "roll your own", starting with the under-
- lying QIO calls. This is MUCH messier than SMG$READ_COMPOSED_LINE.)
-
- -- Jerry
-
-