[comp.unix.aix] "emacs" terminfo--shell-mode in emacs

edelson@ils.nwu.edu (Daniel Choy Edelson) (02/02/91)

I can't get shell-mode to work in emacs (18.56) on my rs6000 apparently
 because there is no terminfo entry for "emacs".  I looked around 
on some other machines and can find neither an "emacs" terminfo nor
termcap entry.  

Has anyone out there solved this problem yet?  If so, can you 
enlighten me?

Thanks.

---------
Danny Edelson   	Institute for the Learning Sciences
edelson@ils.nwu.edu 	     Northwestern University
(708) 491-3500                 Evanston, IL 60201

marc@ibmpa.awdpa.ibm.com (Marc Pawliger) (02/05/91)

In article <793@anaxagoras.ils.nwu.edu>, edelson@ils.nwu.edu (Daniel Choy Edelson) writes:
|> I can't get shell-mode to work in emacs (18.56) on my rs6000 apparently
|>  because there is no terminfo entry for "emacs".  I looked around 
|> on some other machines and can find neither an "emacs" terminfo nor
|> termcap entry.  
|> 
|> Has anyone out there solved this problem yet?  If so, can you 
|> enlighten me?
|> 
|> Thanks.

I am running 18.57 (came out a few days after 18.56) and the shell mode works
right out of the box on my version 3.1.0003 system.

You are correct that there is no terminfo nor termcap entry for "emacs" but
that should not matter.  What specific problems are you having?  I know that
terminal-emulator mode does not work for reasons I have yet to discover, but
I assume you do mean the more vanilla shell-mode.

AIX TIP:

You can find out the version number of your system by running the command
'lslpp -h bos.obj'.  lslpp lists the Licensed Program Products on your system.
-h means include the history and bos.obj is the Base Operating System objects.
Anyway, the last line of the output should be something like:

ACTIVE COMMIT MM/DD/YY 03.01.XXXX.YYYY userid

The MM/DD/YY is the date the BOS update was applied and XXXX is the update
level of the AIX 3.1 product.

+--Marc Pawliger----IBM Advanced Workstations Division----Palo Alto, CA---+
|   Internet: marc@ibminet.awdpa.ibm.com        VNET:    MARCP at AUSVM6  |
|    UUCP:     uunet!ibminet.awdpa.ibm.com!marc  Phone:   (415) 855-3493  |
+-----IBMinet:  marc@ibmpa.awdpa.ibm.com----------IBM T/L:  465-3493------+

As always, these are my opinions, not IBM's etc etc etc

gmoff@ccu1.aukuni.ac.nz (Moffat) (02/05/91)

marc@ibmpa.awdpa.ibm.com (Marc Pawliger) writes:

>You can find out the version number of your system by running the command
>'lslpp -h bos.obj'.  lslpp lists the Licensed Program Products on your system.
>-h means include the history and bos.obj is the Base Operating System objects.
>Anyway, the last line of the output should be something like:

>ACTIVE COMMIT MM/DD/YY 03.01.XXXX.YYYY userid

>The MM/DD/YY is the date the BOS update was applied and XXXX is the update
>level of the AIX 3.1 product.

Presumably this means 03.01.0001.0003 is what's colloquially known as 3001?
We believe we need 3003 to run our 730 successfully, would this show as
03.01.0003.yyyy?  What is the yyyy part?
-Just a little curious
-- 
    Graeme Moffat,                        Phone : +64 9 737 999  x8384 
    Computer Aided Design Centre,         Fax   : +64 9 366 0702
    School of Engineering,		  Mail  : Private Bag, Auckland, NZ
    University of Auckland		  Email : g.moffat@aukuni.ac.nz

jfh@rpp386.cactus.org (John F Haugh II) (02/05/91)

In article <1991Feb5.071911.3676@ccu1.aukuni.ac.nz> gmoff@ccu1.aukuni.ac.nz (Moffat) writes:
>Presumably this means 03.01.0001.0003 is what's colloquially known as 3001?

Sort of.  The third set of numbers "0001" is what tells you it is "x001",
the "3xxx" tells you it is a cumulative update.  "2xxx" is relative to the
preceeding "2xxx - 1" level.

>We believe we need 3003 to run our 730 successfully, would this show as
>03.01.0003.yyyy?  What is the yyyy part?

The number of iterations of the build process required to produce the
given update.  It has little use outside of IBM and serves primarily to
differentiate one level of code from the next during the development
process.  Some people would argue that it serves primarily to confuse
customers ...
-- 
John F. Haugh II                             UUCP: ...!cs.utexas.edu!rpp386!jfh
Ma Bell: (512) 832-8832                           Domain: jfh@rpp386.cactus.org
"I've never written a device driver, but I have written a device driver manual"
                -- Robert Hartman, IDE Corp.

shair@ux1.cso.uiuc.edu (Bob Shair) (02/06/91)

gmoff@ccu1.aukuni.ac.nz (Moffat) writes:


>Presumably this means 03.01.0001.0003 is what's colloquially known as 3001?
>We believe we need 3003 to run our 730 successfully, would this show as
>03.01.0003.yyyy?  What is the yyyy part?
>-Just a little curious
When we upgraded a 730 here to 3003, we were at 03.01.0003.0013;
applying additional maintenance took it to 03.01.0003.0018.
 
We've not yet enough experience to report stability.
-- 
Bob Shair                          shair@chgvmic1.iinus1.ibm.com
Scientific Computing Specialist    SHAIR@UIUCVMD (bitnet)
IBM Champaign