source: trunk/third/nmh/man/vmh.man @ 12455

Revision 12455, 3.3 KB checked in by danw, 26 years ago (diff)
This commit was generated by cvs2svn to compensate for changes in r12454, which included commits to RCS files with non-trunk default branches.
Line 
1.\"
2.\" %nmhwarning%
3.\" $Id: vmh.man,v 1.1.1.1 1999-02-07 18:14:22 danw Exp $
4.\"
5.\" include the -mh macro file
6.so %etcdir%/tmac.h
7.\"
8.TH VMH %manext1% MH.6.8 [%nmhversion%]
9.SH NAME
10vmh \- visual front-end to nmh
11.SH SYNOPSIS
12.in +.5i
13.ti -.5i
14vmh
15\%[\-prompt\ string]
16\%[\-vmhproc\ program] \%[\-novmhproc]
17.br
18\%[switches\ for\ \fIvmhproc\fR]
19\%[\-version]
20\%[\-help]
21.in -.5i
22.SH DESCRIPTION
23\fIvmh\fR is a program which implements the server side of the \fInmh\fR
24window management protocol and uses \fIcurses\fR\0(3) routines to maintain
25a split\-screen interface to any program which implements the client
26side of the protocol.  This latter program, called the \fIvmhproc\fR,
27is specified using the `\-vmhproc\ program' switch.
28
29The upshot of all this is that one can run \fImsh\fR on a display terminal
30and get a nice visual interface.  To do this, for example, just add
31the line
32
33.ti +.5i
34mshproc: vmh
35
36to your \&.mh\(ruprofile.  (This takes advantage of the fact that
37\fImsh\fR is the default \fIvmhproc\fR for \fIvmh\fR.)
38
39In order to facilitate things, if the `\-novmhproc' switch is given,
40and \fIvmh\fR can't run on the user's terminal, the \fIvmhproc\fR is
41run directly without the window management protocol.
42
43After initializing the protocol, \fIvmh\fR prompts the user for a command
44to be given to the client.  Usually, this results in output being sent to
45one or more windows.  If a output to a window would cause it to scroll,
46\fIvmh\fR prompts the user for instructions, roughly permitting the
47capabilities of \fIless\fR or \fImore\fR (e.g., the ability to scroll
48backwards and forwards):
49
50.nf
51.in +.5i
52.ta \w'RETURN  'u +\w'*  'u
53SPACE           advance to the next windowful
54RETURN  *       advance to the next line
55y       *       retreat to the previous line
56d       *       advance to the next ten lines
57u       *       retreat to the previous ten lines
58g       *       go to an arbitrary line
59                (preceed g with the line number)
60G       *       go to the end of the window
61                (if a line number is given, this acts like `g')
62CTRL\-L         refresh the entire screen
63h               print a help message
64q               abort the window
65.re
66.in -.5i
67.fi
68
69(A `*' indicates that a numeric prefix is meaningful for this command.)
70
71Note that if a command resulted in more than one window's worth of
72information being displayed, and you allow the command which is generating
73information for the window to gracefully finish (i.e., you don't use
74the `q' command to abort information being sent to the window), then
75\fIvmh\fR will give you one last change to peruse the window.  This is
76useful for scrolling back and forth.  Just type `q' when you're done.
77
78To abnormally terminate \fIvmh\fR (without core dump), use <QUIT>
79(usually CTRL\-\\).  For instance, this does the \*(lqright\*(rq thing
80with \fIbbc\fR and \fImsh\fR.
81
82.Fi
83^$HOME/\&.mh\(ruprofile~^The user profile
84.Pr
85^Path:~^To determine the user's nmh directory
86.Sa
87msh(1)
88.De
89`\-prompt\ (vmh)\ '
90.Ds
91`\-vmhproc\ msh'
92.Co
93None
94.Bu
95The argument to the `\-prompt' switch must be interpreted as a single
96token by the shell that invokes \fIvmh\fR.  Therefore, one must usually
97place the argument to this switch inside double\-quotes.
98
99At present, there is no way to pass signals (e.g., interrupt, quit) to
100the client.  However, generating QUIT when \fIvmh\fR is reading a command
101from the terminal is sufficient to tell the client to go away quickly.
102
103Acts strangely (loses peer or botches window management protocol with
104peer) on random occasions.
105.En
Note: See TracBrowser for help on using the repository browser.