krulwich@ils.nwu.edu (Bruce Krulwich) (10/31/89)
In RMAIL buffers are maintained for mail files after RMAIL is quitted, and
they are kept around READ-ONLY. Two mail components use them if they exist,
one being the RMAIL-OUTPUT-TO-MAIL-FILE command and the other being the
MAIL-DO-FCC command. The first makes sure to turn off the read-only status
before writing to the buffer, the second does not. This means that if you
have a default FCC mailbox (ie, a MAIL-ARCHIVE-FILE-NAME) you'll get an error
("file is write protected) if you've visitted the mailbox previously.
The obvious fix is to do what OUTPUT does, namely to temporarily
un-read-only-ify the buffer while writing to it (by binding BUFFER-READ-ONLY
to NIL). Does anyone see any problems with doing this??
Bruce Krulwich
Institute for the Learning Sciences
krulwich@ils.nwu.edurlk@think.com (Robert Krawitz) (10/31/89)
In article <1435@accuvax.nwu.edu>, krulwich@ils (Bruce Krulwich) writes:
]have a default FCC mailbox (ie, a MAIL-ARCHIVE-FILE-NAME) you'll get an error
]("file is write protected) if you've visitted the mailbox previously.
]
]The obvious fix is to do what OUTPUT does, namely to temporarily
]un-read-only-ify the buffer while writing to it (by binding BUFFER-READ-ONLY
]to NIL). Does anyone see any problems with doing this??
This is the right thing to do, in my opinion.
--
ames >>>>>>>>> | Robert Krawitz <rlk@think.com> 245 First St.
bloom-beacon > |think!rlk (postmaster) Cambridge, MA 02142
harvard >>>>>> . Thinking Machines Corp. (617)876-1111