[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Editting Unix files using MCL.
- To: firstname.lastname@example.org
- Subject: Editting Unix files using MCL.
- From: email@example.com (Mark Peot)
- Date: Wed, 2 Dec 92 19:28:42 PST
- Cc: firstname.lastname@example.org
- In-reply-to: Bob Hall's message of Tue, 1 Dec 92 16:21:42 EST <9212012120.AA09627@rpal.rockwell.com>
- Reply-to: email@example.com
Bob Hall writes:
> I have not experienced any problem like this. I regularly
> read/write/create files in both UNIX (using Gnuemacs and Allegro CL v4.1)
The problem only pertains to files that are *editted*. Lisp itself does not care
about the kind of white space it encounters... The problem concerns the
appearance of the file in different editors. Gnu Emacs uses the linefeed
character to mark the end of a line. MCL uses a carriage return. When I read
MCL files using Emacs, I see lots of ^M's where carriage returns ought to be.
When I read Emacs files using FRED, I see lots of boxes (the unprintable
character is the linefeed character) where the carriage returns ought to be.
Tell me if the following 'bombs' in your environment. *Create* a new file:
using MCL. Save it to your Unix file server. Look at it using Emacs. On my
machine it looks like:
This happens 'cause the natural newline character for emacs is the linefeed
character, not the carriage return character...
> I tentatively conclude that either a white knight (in the AI planning sense)
> is fixing things behind my back, or else the problem is not with MCL.
Hmmm... I am still betting that it is an MCL/Macintosh "feature" :^)
BTW: I am using MCL 2.0 Final with CLIM 1.1.