1 |
A few examples of constructing menubars for rxvt. Used in conjuction |
2 |
with the reference material (rxvtRef.html/txt), it should be possible to |
3 |
piece together some useful menus without too much time. |
4 |
|
5 |
C-shell users be warned. |
6 |
Some of the menu items contain bsh/ksh constructs like ${EDITOR:-vi}\r |
7 |
which will cause your shell to gag. |
8 |
---------------------------------------------------------------------- |
9 |
|
10 |
example.menu: |
11 |
simple menus for Pico and the Shell |
12 |
|
13 |
jedmenu.sl: |
14 |
(almost) self-contained SLang code for loading up a menubar |
15 |
for the Jed editor. It doesn't need terminal.menu, |
16 |
but looks a bit better with it. |
17 |
|
18 |
Note for JED users: |
19 |
since rxvt provides an escape sequence to override the |
20 |
normal XTerm interpretation of Shift-Insert/Prev/Next, |
21 |
"wmark.sl" (MS-windows-style shift marking) works really |
22 |
well and is a nice bonus for those forced to switch |
23 |
to/from MS-windows |
24 |
|
25 |
terminal.menu |
26 |
common rxvt terminal functions used by the other menus |
27 |
|
28 |
menu: |
29 |
a small shell script to reduce the pain of typing |
30 |
echo "ESC]10; ... BEL" for every menubar command. |
31 |
It also contains a sample "default" menu at the bottom. |
32 |
|
33 |
rxvt.menu: |
34 |
A nice script that allows a convenient way to have different |
35 |
menubars used for rlogin|telnet to a machine. |
36 |
Of course to get it to work, you'll need to add your own |
37 |
machine names (and remove mine). |
38 |
|
39 |
The script is set up so that "rxvt" will be called if the first |
40 |
argument to the script does not contain "rxvt". |
41 |
So |
42 |
rxvt.menu [options] |
43 |
is the same as |
44 |
rxvt.menu rxvt [options] |
45 |
|
46 |
To always have this script act as the front-end for rxvt: |
47 |
1) install the rxvt binary somewhere not in your path |
48 |
2) set the `exe' in menu.script to point to this binary |
49 |
eg, |
50 |
exe="/usr/local/X11/rxvt-2.21/rxvt" |
51 |
# default program to execute |
52 |
3) have rxvt.menu linked somewhere in your path as `rxvt' |
53 |
4) add all the various machines/menus combinations to |
54 |
rxvt.menu, or else make a separate database and change |
55 |
the `menu' variable in rxvt.menu to suit. |