[Bug: 21.5-b28] Problem with dired (C-x d)

[Thomas Mittelstaedt]

Thomas Mittelstaedt schrieb:
> Hmm.
>
> Downloaded the dired package, version 1.17, again, unpacked it, 
> byte-compiled dired.el, and so far, could not
> reproduce the problem anymore. The previous package only had .elc files 
> in it.
>
>   
Nope. Happened again. Sorry, did not do the trace-function-background.
 From within a dired buffer went to the line for the parent directory 
(..) and
that message "buffer ... read-only would come. I had to kill the buffer 
and reopen the directory.


> thomas
>
> Mats Lidell schrieb:
>   
>> Michael Sperber writes:
>>   
>>     
>>> Very odd: It seems it's trying to insert the directory list into
>>> the *Buffer List* buffer.
>>>     
>>>       
>> This sounds like the same problem I have been seeing for years:
>>
>> "http://calypso.tux.org/pipermail/xemacs-beta/2006-May/009236.html"
>>
>> The idea that font locking could be involved let me then to go back to 
>> good old slow font locking and by that I manage to keep the problem 
>> away. But it resurfaced again a few months, maybe even half a year, ago. 
>> So I guess the bug it is lurking inside somewhere.
>>
>>   
>>     
>>> Could you trace the `dired-find-buffer-nocreate' function when it
>>> happens, reproduce the problem, and post the output?  I.e.
>>>
>>> M-x trace-function-backgroud RET
>>> dired-find-buffer-nocreate RET
>>> RET
>>>
>>> and then post the contents of *trace-output*?
>>>     
>>>       
>> I'll try this as well but from my experience when the problem occurs you 
>> are smoked. Trying the operation again does not reveal that much since 
>> the situation is different. And the dired buffer is definitely not right 
>> so you need to look out for other errors caused by that fact. Maybe 
>> deleting the dired buffer and retrying the operation is worth a try if 
>> the other way doesn't work out right.
>>
>> Yours
>> --
>> %% Mats
>>
>>
>>   
>>     
>
>