unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: n8vo <nvonnahme@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Files by FTP
Date: Thu, 01 Nov 2007 11:57:31 -0700	[thread overview]
Message-ID: <1193943451.894300.127060@k35g2000prh.googlegroups.com> (raw)
In-Reply-To: <1193932162.768514.198770@o3g2000hsb.googlegroups.com>

On Nov 1, 7:49 am, Defacta <vincent.margue...@gmail.com> wrote:

> Is it possible to edit some PHP files which are on a server using
> Emacs ? Is it too slow to edit them this way ?

You can either run emacs from a commandline SSH session to the server,
or use Tramp or other file transfer extensions if you want to run
emacs locally, transferring the files back and forth as you work.

You may want to use 'emacs -nw' or emacs-nox if it complains about X
not being available when you run it from the command line.

  parent reply	other threads:[~2007-11-01 18:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-01 15:49 Files by FTP Defacta
2007-11-01 16:47 ` Lennart Borgman (gmail)
2007-11-01 18:57 ` n8vo [this message]
2007-11-02  4:09 ` Xah Lee

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=1193943451.894300.127060@k35g2000prh.googlegroups.com \
    --to=nvonnahme@gmail.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).