yary <[EMAIL PROTECTED]> writes: > On Sat, Oct 18, 2008 at 3:41 AM, Michael Albinus <[EMAIL PROTECTED]> wrote: > ... >> Try "M-x tramp-cleanup-all-connections". > > That worked, thanks!
Good to know. > I'm thinking of putting a call to that in ~/.emacs - any > downside/reason not to? It depends. Tramp 2.1 has introduced a cache, which keeps information about remote hosts persistently. This information enables Tramp to access remote hosts faster. In your case, the information about the test command has been changed, which Tramp couldn't know. `tramp-cleanup-all-connections' is a good way to flush the cache, in order to recompute all those information. It shouldn't be necessary very often. Additionally, Tramp flushes the cache on its own, when "uname -sr" returns a changed result on the remote hosts. All those measures should keep the cache consistent, as far as possible. However, if you are in a situation, that remote hosts configuration changes often, and Tramp does not notify, you might enable the command in your .emacs. See also (info "(tramp)Connection caching") Best regards, Michael. _______________________________________________ Tramp-devel mailing list Tramp-devel@gnu.org http://lists.gnu.org/mailman/listinfo/tramp-devel
