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