Re: New tramp observations

On Do, 2013-01-31 at 12:50 +0100, Michael Albinus wrote: Maybe we are misunderstanding each other. Thanks for the pointers to the cache. Let me explain my issue again: Edit file / save it / on xemacs "A" Edit file outside of xemacs try to resume editing of file IN xemacs xemacs will detect that the file has changed, and ask you what to do: you have choice to edit the current file ("y"), abort editing ("n") and revert the file to its state on disk ("r"). Maybe there is also option to do a diff between them if I know that I have no local changes in this xemacs buffer, and I know that I changed the file outside xemacs, I would want to type on "r" (revert, means it will load a fresh copy of the file but keep point etc) this used to work for local and tramp files. Now, it gets stuck in an endless loop on tramp files. When I type "r", it asks me again (y/n/r). Only y or n can get me out there. I would expect "r" to revert the file (fetch the changed copy via tramp) and let me resume editing in the buffer. Which is the previous behaviour and the behaviour for local files. Does that make anything clearer? Btw "r" should probably be doing something similar to M-x revert-buffer Nei _______________________________________________ XEmacs-Beta mailing list XEmacs-Beta(a)xemacs.org http://lists.xemacs.org/mailman/listinfo/xemacs-beta