Alastair,
Thanks for the reply...
>>>>> "A" == Alastair Reid <[EMAIL PROTECTED]> writes:
>> On Unix, but it seems not on the PC version of Hugs,
>> in a literate script ^M doesn't count as a whitespace character.
>> Thus, if you ship a file from DOS (ugh) to Unix,
>> and it has ^M at the end of every line, the Unix version
>> of Hugs gives you "comment next to program line" errors.
>> This is just annoying.
A> I don't really see this as a Hugs problem but as a file-transfer problem.
A> If you used Hugs on Unix and on an IBM mainframe, you'd have to convert
A> EBCDIC to ASCII and back again. For PC-ascii to Unix-ascii, you can do
A> one of the following:
A> 1) In ftp, use ASCII mode.
A> 2) Using zip, specify the -a (autodetect ascii files) flag.
A> 3) Use a translator program - there's plenty about.
A> My favourite conversion program is: perl -p -i -e "s/\r//" *.*
A> 4) Tell emacs on the PC to treat your Hugs files as Unix files.
A> (Details in emacs FAQ)
Well, you're absolutely right about all of that.
However, it's *still* annoying because:
1) this is a mistake users can easily make, and
2) it's extremely easy to fix.
Why do you want to treat ^M as anything other than a whitespace character?
Why would you want to put a (small) roadblock in the way of new users
(I'm thinking of my students)? All of your suggested fixes, while simple,
require a little more sophistication than what the average users may think of.
No big deal, but I still think it would be nice to treat ^M as whitespace.
You must already be doing that on PCs, so the code is there...
I'll get back to you on the other problem after I've installed the latest beta.
Gary
