Bitbucket is a code hosting site with unlimited public and private repositories. We're also free for small teams!

Close
This directory:

README	    	-- This file
Makefile	-- Automated installation file

viper.el    	-- Viper Emacs Lisp code
viper-cmd.el   	-- Viper Emacs Lisp code
viper-macs.el	-- Viper Emacs Lisp code
viper-ex.el	-- Viper Emacs Lisp code
viper-init.el	-- Viper Emacs Lisp code
viper-util.el	-- Viper Emacs Lisp code
viper-mous.el	-- Viper Emacs Lisp code
viper-keym.el	-- Viper Emacs Lisp code

viper.texi  	-- Manual in Texinfo format

viperCard.tex   -- Reference card in TeX format

viper, viper-?	-- The Info files

viper.dvi	-- Dvi version of the Viper manual
viperCard.dvi	-- Dvi version of the quick reference card

To install Viper, do:

		uncompress viper.tar.Z
		tar xf viper.tar


Then do the following:

1. To compile Lisp:
		
      	    	make elc
   
   Since the DVI and Info files are bundled with the distribution, this is
   the only make command you need.
   
2. To recompile the DVI files (if you have to), type:
		
	       make dvi
		
3. To re-make the info files (if needed), type:

	       make info
	       
4. To redo everything:

	       make all
	       
   "make all" is useful if you made your own changes to the *.texi or
   *.el files. This way, this single command will recompile exactly what's
   needed.
   
5. You can also run

	       make install
	       
   to do what "make all" does plus to copy viper*.elc into
   a suitable Lisp directory and Viper Info files into the Info
   directory; DVI files containing printable version of Viper
   Manual and Reference Card will be copied into the 'etc' directory.
   
   You will still have to edit the 'dir' file manually (see below), if
   you haven't done so during a previous installation.
   
   To make all this happen, you will most likely have to change the PREFIX
   variable in Makefile and, possibly, one or more of these variables:
   
   	DATADIR, LISPDIR, INFODIR, ETCDIR, and VERSION
	
   if they don't point to the right directories in your installation.
   You also need to have a write permission for all directories
   mentioned in LISPDIR, INFODIR, and ETCDIR.
   
6. XEmacs users must invoke make with the parameter EMACS=xemacs.
   Even better: edit Makefile directly as indicated in the comments there.

Recent activity

viteno-guest

Commits by viteno-guest were pushed to xemacs/viper

75ab8da - Increment VERSION in Makefile
kifer-guest

Commits by kifer-guest were pushed to xemacs/viper

cd4deee - 2009-11-22 Michael Kifer <kifer@cs.stonybrook.edu> * viper-cmd.el: use viper-last-command-char instead of last-command-char/last-command-event. (viper-prefix-arg-value): do correct conversion of event-char for XEmacs. * viper-util.el, viper.el: use viper-last-command-char instead ...
viteno

Commits by viteno were pushed to xemacs/viper

e3a492f - Increment VERSION in Makefile
michaelk

Commits by michaelk were pushed to xemacs/viper

3b37e50 - * viper-cmd.el (viper-insert-isearch-string): new function. (viper-if-string): redefine C-s in the minibuffer to insert the last incremental search string. * Changes from the Emacs trunk: last-command-char ...
viteno

Commits by viteno were pushed to xemacs/viper

2e48963 - Increment VERSION in Makefile
michaelk

Commits by michaelk were pushed to xemacs/viper

43c52f8 - * viper.el: date change. * viper-cmd.el (viper-envelop-ESC-key): viper-translate-all-ESC-keysequences is now a function. * viper-init (viper-translate-all-ESC-keysequences): make this variable into a function. * viper.texi (viper-translate-all-ESC-keysequences): description ...
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.