1af56ddaa2
* Add .tedit files for Lafite manual and release notes -- PDFs on Google Drive * use 'docs' for subfolder name; wliminate dup * Remove duplicate LAFITEMANUAL-GLOSSARY-CUSTOMER.TEDIT --------- Co-authored-by: Nick Briggs <nicholas.h.briggs@gmail.com>
24 lines
3.1 KiB
Plaintext
24 lines
3.1 KiB
Plaintext
There is a new and substantially revised version of Lafite on [Phylum]<Lisp>Library>Lafite.dcom and in [Phylum]<Lisp>Current>Full.SYSOUT. If you want to load the new Lafite on top of an old Lafite, please Quit the old Lafite first.
|
||
|
||
The changes in this version are mostly in the internal implementation, rather than the user interface, but there are a few user-visible changes. The major such change is that Lafite no longer attempts to keep your mail browser and the mail file itself consistent with each other at all times. In particular, changes (deletions, marks changed) only get written out to the file when you do an Update, and "MoveTo"s are only guaranteed to have finished then, too. To make this more feasible, there are now two flavors of update: "Update by writing out changes only" and "Expunge deleted messages". The latter is like the old Update, the former can be thought of like a SAVEVM: it does not compact out deleted messages, but does write out changed marks and an updated contents file, assuring that if you booted your machine after the Update that you could browse the mail file again and get back to your previous state.
|
||
|
||
When you close or shrink a browser that has changed in any way needing update, you get a menu of choices--the two flavors of update, or no update at all.
|
||
|
||
The value of the variable LAFITESTATUSWINDOWPOSITION is now the lower left corner of the entire window, as you would expect, rather than the lower left corner of the "You have new mail" part of it.
|
||
|
||
The variable LAFITEUSEHIGHESTVERSIONFLG has gone away. Lafite always reads the highest extent version of a file, and Update goes to that version. That version is, of course, ;1 if you are a using Laurel on the same disk.
|
||
|
||
There is a completely new table of contents format, which is more compact and allows a more efficient update, one that is only proportional to the number of changed messages, rather than to the total number of messages. If you have an old table of contents for a file you browse with the new Lafite, it will be discarded.
|
||
|
||
Assorted bugs have been fixed, including some relating to resuming over Logout or SaveVm, or clicking GetMail too soon. I would be surprised if I'd caught all such bugs, though. If you have some favorite old bug (as opposed to suggestion) that hasn't been fixed, you might want to retransmit a bug report for it.
|
||
|
||
Many internal data structures have been revised; some algorithms that took time proportional to the number of messages in a file are now constant-time algorithms; there is a completely new message header parser. If you rely on any undocumented features of Lafite, let me know, as they may well have changed.
|
||
|
||
If you are a Laurel 6.1 user, you may find that Laurel has transformed some spaces in your messages from character 40Q to 240Q as some sort of line-breaking hack. There is a little function COPY7BITFILE that can be used to copy such a file removing the high-order bits. Args are SRCFIL and DSTFIL, with DSTFIL defaulting to a new version of SRCFIL.
|
||
|
||
There will be updated documentation some day soon.
|
||
|
||
Complaints and suggestions to LafiteSupport as usual.
|
||
E
|
||
TIMESROMAN GACHA
|
||
E z<> |