Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!tut.cis.ohio-state.edu!SHARKEY.CC.UMICH.EDU!had!larry
From: had!larry@SHARKEY.CC.UMICH.EDU (Larry Siden)
Newsgroups: gnu.emacs.bug
Subject: emacs bug
Message-ID: <8912061933@had>
Date: 6 Dec 89 19:33:02 GMT
Sender: daemon@tut.cis.ohio-state.edu
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 27

Hello,
	I am running EMACS version 18.52 and I keep encountering the following
bug whenever I attempt one of the functions 'minibuffer-complete-word' or
'minibuffer-completion' while building an argument to a command that takes
a file-name (e.g. 'find-file').  After typing a complete pathname prefix (e.g.
"/users/larry/", a TAB will produce the message "[Complete, but not unique]"
in the minibuffer, and a space will produce a directory listing in the window
*Completions* .  But if I type a space after "/users/larry" (sans final '/')
I will get a message that reads:

"Wrong type argumnent: sequencep, #<EMACS BUG: ILLEGAL DATATYPE (#o 57) Save your"

The message is cut off after the word "your".

Do you know what this is?
Do you have a more up-to-date version of the culprit module (.o file) to send
me that I can re-link with the others?

Here is the output of the *Backtrace* buffer:

Signalling: (wrong-type-argument sequencep #<EMACS BUG: ILLEGAL DATATYPE (#o 57) Save your buffers immediately and please report this bug>)
  read-file-name-internal("~/fsf" "~/" nil)
  minibuffer-complete-word()
  call-interactively(minibuffer-complete-word)
  call-interactively(find-file)

note: "fsf" is the name of a directory.