home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 5 Edit
/
05-Edit.zip
/
me34src.zip
/
me3
/
doc
/
errata
< prev
next >
Wrap
Text File
|
1995-01-14
|
7KB
|
154 lines
-*-text-*-
========================================================================
== ME2 Errata and machine/OS specifics Craig Durland ==
========================================================================
========================================================================
BUGS
========================================================================
* MS-DOS
If you install TSRs (terminate and stay resident - things like Side
Kick) from within ME (ie ^X! or from a shell invoked by ME) and
don't exit ME, there is a good chance that sometime later ME will
not be able to write out files (it will say something like "Error
closing file"). If this happens, you are screwed - your file is
cleared from the disk and there is no way you can save it.
Another symptom is problems allocating memory ("Cannot allocate x
bytes"). print.com is the only TSR I have verified causing these
problems but don't press your luck.
Note: is OK to use TSRs from within ME. ie using print.com to
print a file while in ME is OK as long as print was installed
outside of ME.
EGA 43 line mode: If you are using nansi.sys, switching into 43 line
mode and then invoking a shell or running a program (^X!) the cursor
may disappear. This is caused by a bug in nansi.sys. When going
into 43 line mode it should set 40:87H bit 0 and clear that bit when
returning to 25 line mode but it don't.
* UNIX
XON/XOFF can screw things up. ME turns off XON/XOFF because XON is
^S and XOFF is ^Q and most Emacs users are very attached to those
keys. This can lead to terminal overruns if the terminal cannot
keep up at the baud rate selected or there is not enough padding.
Sometimes the connection to the computer runs though a server
device that also talks XON/XOFF. If this is the case ^S will stop
the display and some times ME will start searching for no apparent
reason. Talk to a guru and find out how to fix the server or
rebind ^S and ^Q to "" and use the alternate keys (^\ and ^^).
=========================================================================
MS-DOS specifics
=========================================================================
* Filenames can contain "/" or "\". Case is ignored.
* Filename completion may be turned off. If not, you can use csh like
wild cards. See UNIX specifics.
* Strango characters
MS-DOS ME allows you to enter ^Z or NULL (0) and write out the file but
a line with NULL in it gets truncated (at the NULL) when read in.
Some versions allow you to enter a character by typing in its decimal
value (eg "A" is decimal 65) (see below). Note that entering most
keys is like pressing the key on the keyboard so you may want to
quote (^Q) the character.
IBM PC: hold down ALT and type the value on the number pad. The
character is added when the ALT key is lifted.
Portable Plus: Put into Num pad mode (Extend Num), hold down Extend and
press the value on the number pad (the blue numbers). The character
is added when the ALT key is lifted. Now switch back to regular mode
(Extend Num). This is easier to do than to say.
*Eric Turnblom (turnblom@nature.berkeley.edu) writes:
On my Amdek monitor, driven by AST HERCULES monochrome graphics
emulation card, (cursor-shape "1:8") gave me a nice reverse video
block cursor with the top slightly above the line of text, and the
bottom slightly below the line of text.
Mark van der Velden adds:
On my XT (hercules) the scan lines are from 0 to 12. (cursor-shape
"8:12") activates exactly scan lines 8 up to 12, which gives a nice
big underscore.
========================================================================
UNIX specifics
========================================================================
* You can use csh style wildcards: ~, [], [^], ?, * (eg ~craig,
~/tools, foo[123], foo*, etc) for (insert-file), (read-file),
(rename-buffer), (visit-file), (write-file) and current-directory.
Note that ? and " " are also used for filename completion so you
might want to quote them (C-q?).
See dir.mut for examples of cwd, dirs, push directory, pop directory.
* If you want to input 8 bit text (eg edit European languages) make sure:
- Your terminal will pass 8 bit data. You can check this by using
"stty -a". Look for "-istrip" (don't set the 8th bit to zero) and
"cs8" (pass 8 bit data, probably only effects terminals connected to
serial ports). To set these, use "stty -istrip cs8".
- Your keyboard can generate characters with the 8th bit set.
- Your terminal font character set has the right characters above 127.
Here is a Mutt program that will put all 255 characters into the
current buffer. You can use it to look at your font.
(include me2.h)
(include mod.mut)
(defun
all-the-ASCII-characters
{
(int j)
(for (j 1) (< j 256) (+= j 1)
{
(insert-text (convert-to CHARACTER j))
(if (== 0 (mod j 32)) (newline))
})
})
* Function keys, arrow keys, other termainal specific things. I don't
try to parse keys other than the ASCII character set. Trying to use
the termcap entries for special keys (function, arrow, etc) has been a
real pain (especially on HP terminals) and I can never figure out
everything for all termainals. So I don't bother. What I do do is
parse some of them in Mutt. xterm.mut parses vt100 and xterms,
hpterm.mut does HP terminal function keys.
========================================================================
========================================================================
* Screen size:
Sometimes the same code runs on machines with different screen sizes.
If this is your case, you'll need to resize the screen.
For example:
HP110: use me150.exe and put (screen-length 16) in your myme file.
EGA 43 line mode: If you have a IBM PC, EGA and NANSI.SYS (or some
other way to get into 43 line mode), ME can use all 43 lines.
If you are already in 43 line mode: (screen-length 43).
To switch into 43 line mode: (puts "^[[=43h")(screen-length 43)
2 handy pgms:
(defun
EGA {(puts "^[[=43h")(screen-length 43)}
noEGA {(puts "^[[=3h")(screen-length 25)}
)
==================================================================
== Philosophy ==
==================================================================
* ME should behave the same on every machine it runs on.
* ME is an editing engine:
The core functionality should allow ME to be used stand alone. The
core has been patterned after (a subset of) Emacs (where Emacs is
usually GNU Emacs and sometimes Unipress (Goslings') Emacs).
The bells, whistles and features that "personalize" an editor are
Mutt extensions added by the user.
* If you find bugs I want to fix them so let me know.
If you have enhancement requests or stuff you would like to see added,
I am interested.
Restrictions:
Distributed under the terms of the GNU General Public License: Use,
share, enjoy.
* No Warranty - you get what you pay for.
* I am:
Craig Durland (503) 750-3354
3419 SW Knollbrook, Corvallis, OR 97333
craig@cv.hp.com