NetNews Usenet Archive 1992 #18/NN_1992_18.iso/spool/comp/emacs/2878

Internet Message Format | 1992-08-17 | 1.6 KB

Path: sparky!uunet!mcsun!sunic!dkuug!daimi!aau!oase!morten
From: [e-mail] (Morten Kjeldgaard)
Newsgroups: comp.emacs
Subject: Re: Emacs on the SGI Indigo
Message-ID: <morten.714127217@oase>
Date: 18 Aug 92 08:40:17 GMT
References: <[e-mail]> <[e-mail]>
Sender: [e-mail]
Organization: Aarhus University, Denmark
Lines: 23
Nntp-Posting-Host: oase.kemi.aau.dk

In <[e-mail]> [e-mail] (Simon Leinen) writes:

>Sure, GNU Emacs 18.58 contains support for IRIX 4.0 and compiles out
>of the box (as they say).  Use the "s-irix4-0.h" and "m-iris4d.h"
>files in src/config.h.  The only problem is that stripping the binary
>causes it to core dump - I include (without permission) a patch for
>this from a friendly person at SGI.

I too, have successfully installed GNU emacs on the Indigo; I haven't
encountered the above problem, because I never stripped the binary. I have
another problem, however, that I think there is a simple solution to which I
haven't found: When starting emacs from the console, there is no problem,
the X server pops up a window. When starting from a remote terminal,
however, one has to remember the -nw switch. This everybody *ALWAYS*
forgets. On an ESV system we have, emacs figures out for itself to do the
appropriate thing. How does one set this up??

/Morten
--
Morten Kjeldgaard  ~ [e-mail] ~ [e-mail]
Biostructural Chemistry, Department of Chemistry, Aarhus University
Langelandsgade 140, DK-8000 Aarhus C, Denmark
Phone: [phone] ~ [phone] x6752 ~ Fax: [phone]