I had the same problem with the binary characters in the prj.el being interpreted by
shell scripts as EOF and thus triggering project file truncation. To share my prj.el
file among my teammates, I used to apply variable expansion using sed on the prj.el
(to convert absolutes path into relative paths using an environement variables then
expanded into the project file by a script). However, some key bindings contained
binary characters that were interpreted as end-of-file marker. So I wrote a perl
script to apply the pattern substitution in my binary prj.el file.
I hope this can help,
Guillaume.
> -----Original Message-----
> From: Britton, Chris [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, December 12, 2000 12:01 AM
> To: [EMAIL PROTECTED]
> Subject: RE: File mode specification error
>
>
>
> In particular, look for key bindings in the first statement
> that look like
> [?^C ? ?^S](i.e. no key specified after the second "?" in the
> expression)
> and in the second statement that look like [?^C ?^V ?] (i.e. no key
> specified after the third "?" in the expression.
>
> In my case the problem was Microsoft Visual SourceSafe.
> Whenever I would
> check a prj.el file into SourceSafe, it would strip the "^Z" for those
> expressions which corrupts the file.
>
[...]
>
> After repairing (or regenerating) prj.el, I specified all my
> prj.el files as
> binary (instead of text) files in SourceSafe.
>
> Hope this helps.
>
> --
> Chris Britton
> [EMAIL PROTECTED]
>
>
