I'm encountering a strange problem with Xemacs 21.1. I was using hexl-mode
to try and debug some code which reads a particular file format (doesn't
matter what). What I was seeing in hexl-mode led me to believe that the
documentation I had for the file format was wrong, which was worrying.
However, it turns out that the problem is with Xemacs. When I visit this
file I am asked for Encryption key for FILENAME ? [RET to ignore]: I just
press RET and I get the message No key given. Assumed normal. (What is that
all about anyway ?) and then the file loads. It looks like crap as it's
binary data, but that's neither here nor there. If I then try to save it
immediately I get the message (No changes need to be saved) so I instead
save it as a new file. This saved file and the file I loaded are different !
From what I can see, and I haven't made an exhaustive analysis, bytes = 0x0A
in the original are now = 0x0D in the new file. They also appear as 0x0D if
you view the loaded file in hexl-mode. Any ideas, anyone ?
BTW suggestions to use vi will be viewed as hostile (note complete lack of
smilie). I've just spent a couple of hours wondering how the fsck I can
complete this project when the documentation I have about the file format is
wrong. It's a relief to discover that it's not, but now I need to figure out
what's wrong with my editor :-( I have a gut feeling that the strangeness
and the encryption thing are not unconnected, but I've no idea how or why.
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!