Re: Tramp 2.1.9

[Michael Albinus]

Pete Forman <address@hidden> writes:

Hi Pete,

first of all thanks for testing!

> plink would not work at first because tramp-default-user-alist makes
> it pick up user-login-name (my Windows username) when I want it to use
> tramp-default-user (my UNIX username).  So I Customized the alist to
> remove the remsh...plink entry.

Both `tramp-default-user-alist' and `tramp-default-user' are
_proposals_ only. There is no good default which your remote user name
could be but your local user name ...

In fact Tramp expects that a user specifies his remote user name
either in the file name. Or that the user adds its own default to
`tramp-default-user-alist'.

`add-to-list' inserts by default at the beginning of the list; your
own settings have priority over Tramp's settings. So there is no need
to nukenize `tramp-default-user-alist'.

Maybe I shall precise the documentation with respect to this.

> That was not smooth either as the alist had been changed in
> tramp-fish.el.  The add-to-list in there needs to be merged into the
> defcustom in tramp.el.

I wouldn't like to move it. All fish related settings shall be in
tramp-fish.el. And it isn't really necessary, see above.

> plinkx is working too.
>
> Perhaps I should not be using tramp-default-user.  There is a warning
> in its doc about mucking up some config files.

The "plinkx" method does not pass "-u user" to the plink command. So
it shouldn't harm. `tramp-default-user' would be used only if set and
if the corresponding PuTTY session does not specify a user. Given that
"plinkx" is _intended_ to reuse defined PuTTY sessions, I don't see a
big problem.

> I've now reset it to its default of nil and put my UNIX username
> into the remsh... entry of the default alist.  Presumably that is
> the correct way of doing things but it was not obvious from just
> looking at tramp-default-user.

`tramp-default-user-alist' should always be preferred over
`tramp-default-user'. The latter one is only useful if you have just
one and only one remote user name under all circumstances.

In fact `tramp-default-user' is kept for backwards compatibility
reasons only. A simple

(add-to-list 'tramp-default-user-alist `(nil nil ,your-default-user) t)

would do the same job.

> Auto-completion on session name is not working but then I suspect that
> it is failing for all methods.  tramp-parse-putty looks to be working
> from the *scratch* buffer.  Completion of the file name works and that
> is all I tend to use anyway.

Oops. It worked for me @home (and I was proud on being able to read
the Windows registry :-) Maybe somebody else could report ...

Best regards, Michael.