unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Bastian Beischer <bastian.beischer@rwth-aachen.de>
To: Cynthia Page <pageskipro@yahoo.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: gui emacs from terminal
Date: Fri, 16 Jul 2010 18:22:37 +0200	[thread overview]
Message-ID: <AANLkTik23U8ITWodDyvCh8wdCSoTD3pyke3Q1tf9XDEy@mail.gmail.com> (raw)
In-Reply-To: <955206.27103.qm@web51003.mail.re2.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1591 bytes --]

Hey,

You may find it interesting to know that you can use your own emacs to edit
remote files with the help of "tramp" which comes preinstalled with emacs.

To open a file on a remote server use

C-x C-f
"/user@server:PATH_TO_FILE"

You can even tab complete to find filenames.

Cheers
Bastian

16.07.2010 17:06 schrieb am "Cynthia Page" <pageskipro@yahoo.com>:

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....

[-- Attachment #2: Type: text/html, Size: 2550 bytes --]

  reply	other threads:[~2010-07-16 16:22 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
2010-07-16 16:22       ` Bastian Beischer [this message]
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=AANLkTik23U8ITWodDyvCh8wdCSoTD3pyke3Q1tf9XDEy@mail.gmail.com \
    --to=bastian.beischer@rwth-aachen.de \
    --cc=help-gnu-emacs@gnu.org \
    --cc=pageskipro@yahoo.com \
    /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).