Strange things in 21.5 (and dired!?)

[Mats Lidell]

Hi,

This is bad bug report but I must share this experience. Maybe you have
some suggestion on how I can track this further down? Anyway this is what
sometimes happens in 21.5.

When I save a file I get this message in the modeline:

    No file on this line

After som further editing and a new save I get:

    Error in dired-find-file-place

---------------------------------------------------------------
The *Backtrace* is here:
Signaling: (error "Error in dired-find-file-place")
  signal(error ("Error in dired-find-file-place"))
  cerror("Error in dired-find-file-place")
  apply(cerror "Error in dired-find-file-place" nil)
  error("Error in dired-find-file-place")
  dired-find-file-place("/cygdrive/m/records/2004/" "20041007")
  dired-add-entry("/cygdrive/m/records/2004/20041007" nil relist)
  dired-relist-entry("/cygdrive/m/records/2004/20041007")
  apply(dired-relist-entry "/cygdrive/m/records/2004/20041007")
  dired-fun-in-all-buffers("/cygdrive/m/records/2004/" dired-relist-entry
"/cygdrive/m/records/2004/20041007")
  dired-relist-file("/cygdrive/m/records/2004/20041007")
  dired-handler-fn-3((1 4437 "/cygdrive/m/records/2004/20041007" nil t
"m:/records/2004/20041007" #<coding-system raw-text-unix no-conversion
eol-type=lf>))
  dired-handler-fn(write-region 1 4437 "/cygdrive/m/records/2004/20041007"
nil t "m:/records/2004/20041007" #<coding-system raw-text-unix
no-conversion eol-type=lf>)
  write-region-internal(1 4437 "/cygdrive/m/records/2004/20041007" nil t
"m:/records/2004/20041007" raw-text-unix)
  write-region(1 4437 "/cygdrive/m/records/2004/20041007" nil t
"m:/records/2004/20041007")
  basic-write-file-data("/cygdrive/m/records/2004/20041007"
"m:/records/2004/20041007")
  basic-save-buffer-2()
  basic-save-buffer-1()
  basic-save-buffer()
  save-buffer(1)
  call-interactively(save-buffer)
  (dispatch-event "[internal]")
---------------------------------------------------------------

As you see this happens under cygwin but I get it under Linux as well. I
have tried to force it under a vanilla xemacs, no stuff loaded, but I have
so far failed. So it could be some bad interaction with some personal
stuff maybe!?

Yours
--
%% Mats