From: Kenneth Tilton
Subject: Whassup with MCL?
Date: 
Message-ID: <ktilton-F6AB32.19453604112004@nyctyp01-ge0.rdc-nyc.rr.com>
Well, setting ccl::*do-unix-hack* does open files nicely, but nothing 
more: a "Save as..." on the same file actually flips back to one-line 
mode. And no improvement is seen on the load of a file via (load... ).

I looked for the menu code but I have the demo version, I do not think 
it comes with that. And anyway, jeez, Lispworks does not have this 
problem.

On another front, I both signed up for the mcl mailing list and 
requested a 30-day key and have not heard a peep since.

I was looking forward to returning to the Lisp I started with back in 
the mid 90's, but... has MCL lost its edge? I understand it is a tugh 
business to be in, but I have to save some money for expensive graphics 
cards with which to piss off Rahul. :)

kenny

From: Ron Garret
Subject: Re: Whassup with MCL?
Date: 
Message-ID: <rNOSPAMon-71539D.23374204112004@nntp1.jpl.nasa.gov>
In article <·····························@nyctyp01-ge0.rdc-nyc.rr.com>,
 Kenneth Tilton <·······@nyc.rr.com> wrote:

> Well, setting ccl::*do-unix-hack* does open files nicely, but nothing 
> more: a "Save as..." on the same file actually flips back to one-line 
> mode. And no improvement is seen on the load of a file via (load... ).
> 
> I looked for the menu code but I have the demo version, I do not think 
> it comes with that. And anyway, jeez, Lispworks does not have this 
> problem.
> 
> On another front, I both signed up for the mcl mailing list and 
> requested a 30-day key and have not heard a peep since.
> 
> I was looking forward to returning to the Lisp I started with back in 
> the mid 90's, but... has MCL lost its edge? I understand it is a tugh 
> business to be in, but I have to save some money for expensive graphics 
> cards with which to piss off Rahul. :)
> 
> kenny

Try:

(setf CCL::*LINEFEED-EQUALS-NEWLINE* t)

rg
From: John DeSoi
Subject: Re: Whassup with MCL?
Date: 
Message-ID: <chEid.4039$Gm6.3885@newsread3.news.atl.earthlink.net>
Hi Kenny,

Kenneth Tilton wrote:
> Well, setting ccl::*do-unix-hack* does open files nicely, but nothing 
> more: a "Save as..." on the same file actually flips back to one-line 
> mode. And no improvement is seen on the load of a file via (load... ).

Below is a hack I put at the top of my OpenMCL init file to allow it to 
read files with Mac line endings. I have not tested it, but I think it 
should do the same for MCL with Unix line endings.

Best,

John DeSoi, Ph.D.



#|

Note: Do not put any semicolon comments before this line.
The next forms define a semicolon reader for both #\linefeed
and #\return line endings so that OpenMCL can read MCL input
files (Mac line endings). Should also work with with MCL for unix files.

|#



(defun semicolon-reader (stream char)
   (declare (ignore char))
   (do ((c #\null)) ((or (char= c #\linefeed) (char= c #\return)))
     (setf c (read-char stream nil #\newline t)))
   (values))


(set-macro-character #\; #'semicolon-reader)
From: Thomas A. Russ
Subject: Re: Whassup with MCL?
Date: 
Message-ID: <ymizn1s6x3k.fsf@sevak.isi.edu>
Kenneth Tilton <·······@nyc.rr.com> writes:

> 
> Well, setting ccl::*do-unix-hack* does open files nicely, but nothing 
> more: a "Save as..." on the same file actually flips back to one-line 
> mode. And no improvement is seen on the load of a file via (load... ).

I have downloaded "CRLF fred" for Fred (the MCL editor) that (mostly)
handles the issue of different endcodings for text files.  I got it from
Javier Diaz Reinoso at:

  http://homepage.mac.com/javier_diaz_r/eng/resources.html


Oh, and another potential gotcha:  The ~\Newline format command.  This
is my fix for that one:

  (setf (aref ccl::*format-char-table* (char-code #\Linefeed))
        (aref ccl::*format-char-table* (char-code #\Return)))

Otherwise you can get errors from format directives with no definition.

-- 
Thomas A. Russ,  USC/Information Sciences Institute