Re: tramp (2.2.5-pre); Lingering default-directory causing damage

[Thierry Volpiatto]

Dave Abrahams <address@hidden> writes:

> on Wed Jul 04 2012, Michael Albinus <michael.albinus-AT-gmx.de> wrote:
>
>> Dave Abrahams <address@hidden> writes:
>>
>> Hi Dave,
>>
>> during my monthly check of the SPAM folder, I've found your message. No
>> idea why my provider believes you belong to, hopefully they don't
>> continue to handle you so.
>>
>>>> But it would be a good reason to ask the gnus folks for proper use of
>>>> `gnus-default-directory', if they don't.
>>>
>>> What do you consider "proper" in this case?  Do you think you might ask,
>>> if you are clear on what the right behavior is.
>>
>> Yes. For every single process-file call, they shall wrap it by
>>
>> (let ((default-directory (or gnus-default-directory default-directory)))
>>   (process-file ...))
>>
>> Hopefully, they do. Have you tried to check, whether 
>>
>> (setq gnus-default-directory "/tmp")
>>
>> or something similar works for you?
>
> I customized it to "~" and I haven't been seeing the problem since.
Don't know if it is related, but actually I have really hard time to
keep a repeated remote async process (grep) inside its context:

(let ((default-directory foo))
   (start-file-process.....)

First call is done in this let-bound directory path (the remote),
but second one (without quitting) is done locally.

You can reproduce with last version of helm by creating two similar files:

one on your local machine:
/tmp/foo.txt
write inside: "this is the local file"

one on the remote machine:
/tmp/foo.txt
write inside: "this is the remote file"

lauch grep from helm and grep the remote file:
Enter 4 char, then remove one, add one etc...

You should see that sometimes, the process is called outside of its let
clause and the result is what you have in local file.

It works as expected if you are really slow to type.(or bounding 
a delay >= 3 seconds).

-- 
  Thierry
Get my Gnupg key:
gpg --keyserver pgp.mit.edu --recv-keys 59F29997