pmchale@UUNET.UU.NET (Paul Mchale) (04/04/91)
Following is a configuration of my system
Sun sparcstation 330
Sony color monitor
environment=
TERM=sun
term=sun
There are two problems:
1. Occasionally, if the cursor is placed at the beginning of a line
that has text from column 0 to whatever, and space is pressed,
the text is moved over one space to the right but the character
in the first column is not erased. ie.
12345
then after putting the cursor under the 1 and pressing space:
112345
the same effect is observed with tab, but you would have for the second line
1234512345
where the first 12345 was not erased.
2. Also, we are having a heck of a time defining properly the keyboard.
The C- and ESC- work fine but the cursor, etc keys do not work.
Any assistance would be greatly appreciated. After using emacs
at another site, we fell in love and would like to implement emacs
locally.
What we have tried:
1 Copied the sun terminal definitions supllied with emacs over top
of the termcap entry supplied by Sun. No effect.
2 Tried to load sun*.el to define cursors. Message
error: void push. No effect.
3 Made sure that Makefiles are all set propperly.
Thanks for your time.pmchale@UUNET.UU.NET (Paul Mchale) (04/04/91)
Following is a configuration of my system
Sun sparcstation 330
Sony color monitor
environment=
TERM=sun
term=sun
There are two problems:
1. Occasionally, if the cursor is placed at the beginning of a line
that has text from column 0 to whatever, and space is pressed,
the text is moved over one space to the right but the character
in the first column is not erased. ie.
12345
then after putting the cursor under the 1 and pressing space:
112345
the same effect is observed with tab, but you would have for the second line
1234512345
where the first 12345 was not erased.
2. Also, we are having a heck of a time defining properly the keyboard.
The C- and ESC- work fine but the cursor, etc keys do not work.
Any assistance would be greatly appreciated. After using emacs
at another site, we fell in love and would like to implement emacs
locally.
What we have tried:
1 Copied the sun terminal definitions supllied with emacs over top
of the termcap entry supplied by Sun. No effect.
2 Tried to load sun*.el to define cursors. Message
error: void push. No effect.
3 Made sure that Makefiles are all set propperly.
4 Tried to load /lisp/term/sun.el in .emacs but makes no difference.
Thanks for your time.par@EAGLE.MIT.EDU (Peter Richards) (05/04/91)
i'm trying to compile gnu emacs here on a siemens nixdorf wx200 (a 386 deskside computer) running sco unix V/386 version 3.2. to compile gnu emacs, one has to build two system-specific header (dot-h) files. these are the "s-" and "m-" files. the s- file reflects the operating-system under which emacs is being compiled. the m- file reflects the machine (hardware). the standard distribution of gnu emacs (version 18.55) contains canned s- and m- files for various machines and operating systems - but not exactly for my situation. the closest files seem to be m-intel386.h (for intel 386 machines) and s-usg5-3.h (for the latest Sys V Unix). when i try to compile with these headers the compilation breaks in the file sysdep.c: the struct tchars is undefined. struct tchars seems to have something to do with the ioctl/termio system. i see the definition on other SysV-like systems here in the file /usr/include/sys/ioctl.h but not on the SCO system. so: i need a different s- file. so has anyone there successfully compiled gnu emacs for sco unix V/386? if so, they could find which s- and m- files are used by looking in the file ...emacs/src/config.h. please reply to par@eagle.mit.edu
harelb@cabot (Harel Barzilai) (05/13/91)
I was extolling the wonders of GNU Emacs to a friend, doing my best to "convert," but the question arose as to whether there is an emacs which would run on his machine. It's an IBM 370 type machine running VM/SP HPO. If you post, please copy me by email [harel@dartmouth.edu] Thanks! Harel
hendrick@ctron.com (Jim Hendrick) (05/15/91)
Wow, now THAT would be a port . . . First, the entire set of unix related system calls can be trashed. Next all that can be redesigned to work in a single-process, non tree structured file system (bag dired, spawning sub-processes, you get the idea). To play the devils advocate for a moment, the default editor on a VM system (XEDIT) is not bad in that realm. I have worked extensively with it and it plays well with the system product interpreter language (REXX) as well as having a reasonable macro facility itself (I wrote an entire "window" user interface including pop-ups etc. using just REXX and XEDIT macros.) Not that it compares with emacs for friendliness (although some would disagree using the "M-x C-\ ESC-footpedal ..." argument). I just wanted to point out the other side of the coin. Tell your friend to learn to live with XEDIT ,or get a job in a unix shop like I did :-).