Just a guy who likes to program. Ved was originally created because I didn't
like any of the editors available to me. So, I wrote Ved. It has just keep on
evolving to it's present state.
In an effort to make the editor run in as many different environments as possible,
we've used ncurses. It is a fairly compact and efficient wrapper for the nitty-gritty
of managing an display device. We've tryed to write optimizaton routines in the past
for managing terminal updates, etc. and it is not an easy thing to do.
Not at the present time. We do have, in the back of our minds, the idea that
it might be neat to have an XVed which would probably just run in an stripped
down XTerm, but still use ncurses.
Compiling should be quite simple...especially if your system is the
same as mine.
The command ``make all'' should work. However, it assumes that you have
some other programs already installed:
``make clean'' will delete all old object, debug and core files.
``make tar'' gathers the source files, docs, and aux programs into a
distribution.
We are using Linux 2.0.36. This is from a rather old Slackware installation
which has been updated in an adhoc basis. However, it does appear to be
quite solid. If you are using a different OS, then we really can't help
all that much; however, we'd like to hear of your success and/or changes
so that we can update this document.
As mentioned in the docs, Ved relies on ncurses. See the docs for the correct version information. Also, read the documentation files distributed with ncurses, especially the README and INSTALL files.
Please note that our experience has shown that 95
with Ved are not problems with the program, but problems with the ncurses
installation of the terminfo library. If you are having problems with Ved
you will probably have problems with other ncurses applications. Did you
run the tests in the ncurses distribution? If they don't work, you can be
assured that Ved won't either.
As mentioned in the documenation, Ved relies on the ncurses library and database. For some, unknown to me, reason, the default settings for an Xterm do not set colors. What you will have to do is to properly set the TERM variable so that the proper terminfo entry is found. This can be done in several ways:
should work.
to
One problem with this is that some applications don't like the
xterm-xf86-v33 definition. These applications are probably using
the termcap database, which may not have an entry for this terminal.
Other applications just check this to make sure that you're running
an Xterm. In any event, it is easy enough to just ``export TERM xterm''
in these cases.
Unlike the above suggestion, this is specific to a user. You may have to change this for all users using the termcap database.
The only problem with this is that if you update your terminfo database the link will quite possibly get clobbered.
For some reason, the Redhat installation sets up xterm to override the normal definitions given to the Page-up and Page-down keys. It does this in the .Xdefaults file. If you examine your .Xdefaults file you'll find some lines which look like:
This sets up you Page-Up/Down keys to act as terminal scroll keys. By default, an Xterm uses the Shifted Page-Up/Down keys and this command sets the unshifted keys to act the same. Unfortunately, the person who did this forgot that an application using the terminfo database thinks that the information in that database is correct... So, comment out these lines by placing a ``#'' in column 0 in each line. Restart your Xterm and all should be okay.
Mouse support is a function of the ncurses library. You should read the
docs with ncurses.
Ncurses only supports one mouse button (well, easily).
This document was generated using the
LaTeX2HTML translator Version 98.1p1 release (March 2nd, 1998)
Copyright © 1993, 1994, 1995, 1996, 1997,
Nikos Drakos,
Computer Based Learning Unit, University of Leeds.
The command line arguments were:
The translation was initiated by Bob van der Poel on 1999-05-14
Contents
1. About Ved
1.1 Who is Bob van der Poel and why this Editor?
1.2 I see you have used the ncurses library. Why?
1.3 Do you plan to do an X version of Ved?
2. Compilation and Appearance Problems
2.1 I'm having some problems getting things to compile.
The ``make all'' command also creates the objs directory. If you don't
want to do a ``make all'', create the objs directory by hand and then
do a ``make''. This should create a binary in your current directory.
2.2 I get funny things displayed on the screen. I get incorrect responses to some keys. What did I do wrong?
2.3 The documentation mentions different colors for different parts of Ved. I am running an Xterm and all the windows are the same color. What's going on?
export TERM=xterm-xf86-v33
XTerm.TermName: xterm
XTerm.TermName: xterm-xf86-v33
XTerm.TermName: xterm-xf86-v33
ln -s xterm-xf86-v33 xterm
2.4 The Page-up and Page-down keys on my RedHat (other??) system don't work with Ved. What's up?
xterm*VT100.Translations: #override\n\
<KeyPress>Prior : scroll-back(1,page)\n\
<KeyPress>Next : scroll-forw(1,page)
nxterm*VT100.Translations: #override\n\
<KeyPress>Prior : scroll-back(1,page)\n\
<KeyPress>Next : scroll-forw(1,page)
2.5 My mouse doen't work. Why do you only support the one mouse button?
About this document ...
latex2html -dir faq -local_icons -no_navigation -show_section_numbers -no_footnode -split +0 faq.
Bob van der Poel
1999-05-14