ChatGPT解决这个技术问题 Extra ChatGPT

What is the best way to open remote files with emacs and ssh

I connect to the remote machine with ssh user@192.168.1.5. When I need to open a file in the remote machine I do, e.g.,

emacs /usr/share/nginx/html/index.html

and that opens the index.html file in the shell. I noticed that some emacs commands work but others do not work. For instance, C-w does not work; M-< does not work. How can I fix this, and what is the best way to work with emacs and ssh?

I found this question but it made me more confused.

What are some examples of commands that do work? (Sometimes different keybindings exist on the remote machine - check your .emacs file on the remote machine - and sometimes an entire key works differently - e.g. GNU screen by default absorbs the Ctrl-A part of a command before it can get to emacs.)
C-space, C-F,C-g work
I could not find the .emacs file in the remote machine now but I know I did not make any new key bindings in the other machine
yes, I'm not sure what leads to this set of keybindings not working. Does emacs open the file in the same mode on the remote server as it would open it locally (where all the commands have been working)? Perhaps this could give a clue - M-x describe-mode.
Do you also run emacs on your local machine? Is there any reason you want to use the remote emacs vs. a local one?

C
Carl Groner

I generally prefer opening remote files from a local Emacs instance.

While running Emacs on your local machine, opening a remote file over ssh is not much different than opening any other file besides a slightly different syntax.

For ssh, you can type C-x C-f. Now, in the minubuffer you want to type /ssh:user@host:/path/to/file (Note that tab completion will work once you start typing a path. Also note the leading / character). See the full docs here.

In your example, that would be:

C-x C-f /ssh:user@192.168.1.5:/usr/share/nginx/html/index.html

Now you can edit remote files over ssh in Emacs while using your local configuration and any installed packages, etc...


OP might be interested to know that this functionality is called: tramp and it is one of the most useful things you will ever use. It even compiles remotely!
This works great and all commands appear to work, but I see that it won't let me edit index.html because it says buffer is read-only. But I can edit the same file if I open on the remote computer. By the way, when I opened the file with C-x C-f /ssh:user@host filename it asked me the password.
I tried another file from Documents directory and I could edit that one without problem.
Do you know how to specify port with this?
@PhilipKirkbride The full documented syntax is /method:user@host#port:filename
a
abo-abo

Just to add to the answer above, you can write shortcuts for machines that you use frequently:

(defun connect-remote ()
  (interactive)
  (dired "/user@192.168.1.5:/"))

This will open a dired buffer on a remote machine. You can navigate this buffer as you would a local one.

If you have set up ssh keys for the remote machine, you don't even have to enter the password.

If you have a bunch of remote machines, you can give some recognizable name to each function, e.g. connect-cupcake, connect-kitkat and use smex package for completion.


This is great. I'll try it. Do you also have an answer for the question I asked in the comment above: I can edit this file /usr/share/nginx/html/index.html if I open it in the remote machine; but when I open it with ssh, index.html is read-only. Why is this?
I'm guessing that you're not connecting with root user, and usually only he can write to /usr/share/.
but how do I connect as root user? I tried a few things like C-x C-f /sudo ssh:user@host filename but that does not work.
This is a problem that I tried to solve some time ago with no success. I can use tramp to connect to remote, or to connect to local as sudo, but not both. A workaround is to make yourself the owner of /usr/share/nginx/html/ folder with chown.
I opened the file /etc/nginx/sites-available/example.com.conf and edited it and saved it and closed it. Now I opened it again, and this time I cannot edit it? I assume it has to do something with permissions. Can you help me understand why this is happenning?
D
Drew

And to add to @abo-abo's post about "shortcuts" --

Use Emacs bookmarks. Just create bookmarks normally, when you visit a remote file or directory. Then just use C-x r b to jump to a remote bookmark, whose name you provide (with completion).

If you use Bookmark+ then remote bookmarks are highlighted specially in the *Bookmark List*, so you can recognize them more easily. And remote bookmarks that must be accessed by su or sudo (root) are highlighted differently.

If you use Dired+ then you can also quickly bookmark multiple remote files or directories, by visiting their containing remote directory in Dired, marking them, and hitting C-x b. No need to give the bookmarks names; they are named after the files. Even if you never use those bookmarks for navigating to the remote files, you can use them with Bookmark+ tags to organize the files and thus operate on subsets of them.

If you use Icicles then whenever you use a command to jump to a bookmark, you can narrow the completion candidates to those that are remote by hitting C-M-@ during completion.


A
Alex

The original poster expressed interest in opening remote files as the root user. This can be done with the command:

C-x C-f /ssh:you@remotehost|sudo:remotehost:/path/to/file RET

More documentation can be found here: https://www.emacswiki.org/emacs/TrampMode#toc14


J
JimLohse

A Simple Answer that focuses on the remote machine:

If I plan to do all my emacs work on the remote machine, I use

ssh -X username@hostname

and then run emacs in the remote session, displaying back on my local machine. It's an old question but I wanted to throw this in for completeness. Granted there are some xhost / X config issues but in many networks this will work right off the bat!


D
Drake Sobania

SSH mode for emacs is what you're looking for.

Once you have it set up you just run

M-x ssh RET hostname RET

Then it prompts you for your password twice (once for the command line, once for loading files).

For the most part you can treat it like any other shell (non-interactive and a few minor differences, but that's it).

It keeps track of which directory you're in, so when you want to open a file from the directory you're looking at it automatically starts in the right directory and you just need to enter in the file name.

Emacs Wiki has more info too.