Thanks everyone for your time and helpful information on this post. I am sorry to say that so many of your questions and comments are over my head, so please forgive me if I don't attempt an answer
I found that I needed to invoke xterm when I ssh'd into the remote machine.
I had a basic misunderstanding of the processes I needed to accomplish remote file editing. Originally I thought I was using the emacs that was installed on my machine, when I edited files on a server that I was ssh' ing to. Now I realize that when I ssh to a server, I am using a version of emacs that has been installed on that server. Also that I need X11 on my machine so that I can use xterm to run emacs application (from the server) in an xterm window and with some menu driven support.
So the command
ssh -Xf address@hidden xterm.
From: Peter Dyballa <address@hidden>
To: Kevin Rodgers <address@hidden>; Cynthia Lee Page <address@hidden>
Sent: Fri, July 16, 2010 1:30:21 AM
Subject: Re: gui emacs from terminal
Am 16.07.2010 um 03:02 schrieb Kevin Rodgers:
> I always log the output for future reference e.g.
--with-ns 2>&1 | tee configure.log
You could also use M-x compile RET <configure command> RET to create a *compilation* buffer in which the use of faces emphasises some text output to see more easily what is going on, potentially failing. Finally the *compilation* buffer needs to be saved and closed, in order to save it from being reused and overwritten by next compilation.
Anyway, the Carbon, NS, and AppKit variants of GNU Emacs have no networking capability in a manner like an X client because Apple's windowing system is like that from MS not network aware, only local like the windowing systems from 30 years ago (on Xerox Star, Pet, Lisa, Atari, Amiga, Sun with SunView, Apollo with Presentation Manager). TRAMP in Emacs allows to edit files in remote file systems, and Apple's Terminal application would allow to launch any Carbon, NS, or AppKit variant of GNU Emacs without GUI inside it as
Never be led astray onto the path of virtue