1384 |
I guess that another workaround is to run Emacs under Cygwin, or to run |
I guess that another workaround is to run Emacs under Cygwin, or to run |
1385 |
a Cygwinized Emacs. |
a Cygwinized Emacs. |
1386 |
|
|
1387 |
|
@cindex Cygwin and ssh-agent |
1388 |
|
@cindex SSH_AUTH_SOCK and Emacs on Windows |
1389 |
|
If you want to use either @code{ssh} based method on Windows, then you |
1390 |
|
might encounter problems with @code{ssh-agent}. Using this program, you |
1391 |
|
can avoid typing the pass-phrase every time you log in (and the |
1392 |
|
@code{scpx} method more or less requires you to use @code{ssh-agent} |
1393 |
|
because it does not allow you to type a password or pass-phrase). |
1394 |
|
However, if you start Emacs from a desktop shortcut, then the |
1395 |
|
environment variable @code{SSH_AUTH_SOCK} is not set and so Emacs and |
1396 |
|
thus Tramp and thus @code{ssh} and @code{scp} started from Tramp cannot |
1397 |
|
communicate with @code{ssh-agent}. It works better to start Emacs from |
1398 |
|
the shell. |
1399 |
|
|
1400 |
|
If anyone knows how to start @code{ssh-agent} under Windows in such a |
1401 |
|
way that desktop shortcuts can profit, please holler. I don't really |
1402 |
|
know anything at all about Windows@dots |
1403 |
|
|
1404 |
|
|
1405 |
@node Usage |
@node Usage |
1406 |
@chapter Using @tramp |
@chapter Using @tramp |