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

Again have trouble acessing a directory: Debugger entered--Lisp error: (error "dired-subdir-alist seems to be mangled") signal(error ("dired-subdir-alist seems to be mangled")) cerror("dired-subdir-alist seems to be mangled") apply(cerror "dired-subdir-alist seems to be mangled" nil) error("dired-subdir-alist seems to be mangled") dired-current-directory() dired-sort-toggle-or-edit(nil) call-interactively(dired-sort-toggle-or-edit) (dispatch-event "[internal]") recursive-edit() byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3) debug(error (error "No file on this line")) signal(error ("No file on this line")) cerror("No file on this line") apply(cerror "No file on this line" nil) error("No file on this line") dired-move-to-filename(t 292 344) dired-get-filename(nil) dired-get-marked-files(nil nil) (let ((on-each ...) (files ...) (dir ...)) (list (dired-read-shell-command ... ... ...) current-prefix-arg files nil)) call-interactively(dired-do-shell-command) (dispatch-event "[internal]") recursive-edit() byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3) debug(error (buffer-read-only #<buffer "elftests">)) call-interactively(self-insert-command) (dispatch-event "[internal]") and another one Debugger entered--Lisp error: (buffer-read-only #<buffer "elftests">) call-interactively(self-insert-command) (dispatch-event "[internal]") recursive-edit() byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3) debug(error (error "dired-subdir-alist seems to be mangled")) signal(error ("dired-subdir-alist seems to be mangled")) cerror("dired-subdir-alist seems to be mangled") apply(cerror "dired-subdir-alist seems to be mangled" nil) error("dired-subdir-alist seems to be mangled") dired-current-directory() dired-sort-toggle-or-edit(nil) call-interactively(dired-sort-toggle-or-edit) (dispatch-event "[internal]") recursive-edit() byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3) debug(error (error "No file on this line")) signal(error ("No file on this line")) cerror("No file on this line") apply(cerror "No file on this line" nil) error("No file on this line") dired-move-to-filename(t 292 344) dired-get-filename(nil) dired-get-marked-files(nil nil) (let ((on-each ...) (files ...) (dir ...)) (list (dired-read-shell-command ... ... ...) current-prefix-arg files nil)) call-interactively(dired-do-shell-command) (dispatch-event "[internal]") recursive-edit() byte-code("..." [buffer-read-only noninteractive debugger-buffer middlestart debugger-args debugger-batch-max-lines pop-to-buffer debugger-mode debugger-setup-buffer count-lines 2 "...\n" message buffer-string kill-emacs debug backtrace-debug 3 t debugger-reenable "" nil recursive-edit standard-output] 3) debug(error (buffer-read-only #<buffer "elftests">)) call-interactively(self-insert-command) (dispatch-event "[internal]") Thomas Mittelstaedt schrieb: > 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 >>> >>> >>> >>> >>> >>> >> >> >> > >