Mercurial > hg > xemacs-beta

comparison lisp/viper/README @ 16:0293115a14e9 r19-15b91

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Import from CVS: tag r19-15b91
author cvs
date Mon, 13 Aug 2007 08:49:20 +0200
parents 9ee227acff29
children 0132846995bd
comparison
equal deleted inserted replaced
15:ad457d5f7d04 16:0293115a14e9
6 Makefile -- Automated installation file 6 Makefile -- Automated installation file
7 7
8 viper.el -- Viper Emacs Lisp code 8 viper.el -- Viper Emacs Lisp code
9 viper-macs.el -- Viper Emacs Lisp code 9 viper-macs.el -- Viper Emacs Lisp code
10 viper-ex.el -- Viper Emacs Lisp code 10 viper-ex.el -- Viper Emacs Lisp code
11 viper-init.el -- Viper Emacs Lisp code
11 viper-util.el -- Viper Emacs Lisp code 12 viper-util.el -- Viper Emacs Lisp code
12 viper-mous.el -- Viper Emacs Lisp code 13 viper-mous.el -- Viper Emacs Lisp code
13 viper-keym.el -- Viper Emacs Lisp code 14 viper-keym.el -- Viper Emacs Lisp code
14 15
15 viper.texi -- Manual in Texinfo format, main part 16 viper.texi -- Manual in Texinfo format, main part
73 if they don't point to the right directories in your installation. 74 if they don't point to the right directories in your installation.
74 You also need to have a write permission for all directories 75 You also need to have a write permission for all directories
75 mentioned in LISPDIR, INFODIR, and ETCDIR. 76 mentioned in LISPDIR, INFODIR, and ETCDIR.
76 77
77 6. XEmacs users must invoke make with the parameter EMACS=xemacs 78 6. XEmacs users must invoke make with the parameter EMACS=xemacs
78 or whatever name is used to invoke XEmacs (some sites still use xemacs 79 or whatever name is used to invoke XEmacs (some backward sites
79 for Emacs 18). An even better thing would be to edit Makefile directly 80 still use xemacs for Emacs 18). An even better thing would be to
80 as indicated in the comments there. 81 edit Makefile directly as indicated in the comments there.
81 82
82 For manual installation, copy viper.elc into a directory on your load-path.
83
84 To install on-line documentation, you need to install the Info files
85 by copying the files
86
87 viper.info*
88
89 into your Info directory (which is emacs-root-dir/info,
90 if emacs-root-dir is the root directory of the installation).
91
92 Then edit the file
93
94 emacs-root-dir/info/dir
95
96 to include the root menu item for Viper (check how other menu
97 items look like in this file).
98
99 In Emacs, this item should look like this:
100
101 * Viper: (viper.info). A VI Plan to Rescue Emacs and a venomous VI PERil
102
103 In XEmacs, it should look like:
104
105 * Viper:: A VI Plan to Rescue Emacs and a venomous VI PERil
106
107
108 If you need a hard copy of the documentation, the files
109
110 viper.dvi
111 viperCard.dvi
112
113 contain the Viper manual and the quick reference card, respectively.
114
115