From: Cynthia Page <pageskipro@yahoo.com>
To: help-gnu-emacs@gnu.org
Subject: Re: gui emacs from terminal
Date: Fri, 16 Jul 2010 07:04:42 -0700 (PDT) [thread overview]
Message-ID: <955206.27103.qm@web51003.mail.re2.yahoo.com> (raw)
In-Reply-To: <A7A4B59D-B0FB-44FF-9972-5C6733B5521D@Web.DE>
[-- Attachment #1: Type: text/plain, Size: 2287 bytes --]
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 is
ssh -Xf username@host xterm.
Thanks again!
Cynthia
________________________________
From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: Kevin Rodgers <kevin.d.rodgers@gmail.com>; Cynthia Lee Page
<Cynthia.Page@Colorado.EDU>
Cc: help-gnu-emacs@gnu.org
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.
>
> ./configure --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
/Applications/Emacs.app/Contents/MacOS/Emacs -nw
--
Greetings
Pete
Never be led astray onto the path of virtue
[-- Attachment #2: Type: text/html, Size: 3093 bytes --]
next prev parent reply other threads:[~2010-07-16 14:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-14 10:47 gui emacs from terminal Cynthia Lee Page
2010-07-15 8:14 ` Peter Dyballa
2010-07-15 11:51 ` Tim Visher
2010-07-16 1:02 ` Kevin Rodgers
2010-07-16 4:27 ` Melton Low
2010-07-16 7:30 ` Peter Dyballa
2010-07-16 14:04 ` Cynthia Page [this message]
2010-07-16 16:22 ` Bastian Beischer
2010-07-16 19:44 ` Peter Dyballa
[not found] <mailman.10.1279168075.3908.help-gnu-emacs@gnu.org>
2010-07-15 16:38 ` Pascal J. Bourguignon
2010-07-16 8:48 ` Giacomo Boffi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=955206.27103.qm@web51003.mail.re2.yahoo.com \
--to=pageskipro@yahoo.com \
--cc=help-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).