1363 |
|
|
1364 |
This section needs a lot of work! Please help. |
This section needs a lot of work! Please help. |
1365 |
|
|
1366 |
@cindex method smx with Cygwin |
@cindex method sshx with Cygwin |
1367 |
@cindex smx method with Cygwin |
@cindex sshx method with Cygwin |
1368 |
If you use the Cygwin installation of ssh (you have to explicitly select |
If you use the Cygwin installation of ssh (you have to explicitly select |
1369 |
it in the installer), then it should work out of the box to just select |
it in the installer), then it should work out of the box to just select |
1370 |
@code{smx} as the connection method. You can find information about |
@code{sshx} as the connection method. You can find information about |
1371 |
setting up Cygwin in their FAQ at @uref{http://cygwin.com/faq/}. |
setting up Cygwin in their FAQ at @uref{http://cygwin.com/faq/}. |
1372 |
|
|
1373 |
|
@cindex method scpx with Cygwin |
1374 |
|
@cindex scpx method with Cygwin |
1375 |
|
If you wish to use the @code{scpx} connection method, then you might |
1376 |
|
have the problem that Emacs calls @code{scp} with a Windows filename |
1377 |
|
such as @code{c:/foo}. The Cygwin version of @code{scp} does not know |
1378 |
|
about Windows filenames and interprets this as a remote filename on the |
1379 |
|
host @code{c}. |
1380 |
|
|
1381 |
|
One possible workaround is to write a wrapper script for @code{scp} |
1382 |
|
which converts the Windows filename to a Cygwinized filename. |
1383 |
|
|
1384 |
|
I guess that another workaround is to run Emacs under Cygwin, or to run |
1385 |
|
a Cygwinized Emacs. |
1386 |
|
|
1387 |
|
|
1388 |
@node Usage |
@node Usage |
1389 |
@chapter Using @tramp |
@chapter Using @tramp |