Article View: gnu.epoch.misc
Article #839Re: Missing subject header
From: Chuck Thompson
Date: Thu, 27 May 1993 19:02
Date: Thu, 27 May 1993 19:02
63 lines
3081 bytes
3081 bytes
In article <1993May27.175127.13229@rchland.ibm.com> mjruss@rchland.vnet.ibm.com (Mike Russell) writes: > I have allot of epoch code that uses zones. Is this called multi- > font support and not available in emacs 19.7? If so no way will I > move. I like epoch, am not interested in spending allot of time > migrating to lucid faces or emacs 19.7. However, Lucid faces appear > to be allot faster than zones The C++ mode for lucid allows larger > buffers to be displayed because the faces implementation is more > efficient. > 1. What will lepoch 5.0 use for a basis of epoch zones? The > current lemacs C code or the epoch code. The merged version will use the Lucid code for zones. These are _much_ more efficiently implemented and switching to them is a big win for a number of Epoch features, including the redisplay model. > 2. We are big users of selective display. Lucid has this turned > off. If lucid is used as a start point this needs to be fixed. When > will the great display code rewrite happen. Will this be fixed for > lepoch 5.0? Selective display will be fully operational in the merged version. The redisplay rewrite is in progress right now. See the note posted by Jamie Zawinski in alt.lucid-emacs.help for more information on the merger and expected availability. > 3. emacs 19.7 supports scroll bars. I do not think that lemacs > does. Hopefully, lepoch 5.0 will. The merged version will have scroll bars. > 4. epoch zones are unusable for column data today. I have a table > format that users want highlighted using different colors in cols . > The table is a PLA kind of thing with allot of zone changes. epoch > takes 10+ sec to do a pageup if I use this many zones. Can this be > made more efficient? As mentioned above, the zone implementation will be Lucid's extents. These are already much more efficient than Epoch's zones. You should have no problems doing this. > Thanks for epoch. If lepoch means fewer migration problems for > epoch users I vote for your emacs alternative. A compatibility package will be available with the merged version, possibly even before the merged version is released. -- Chuck Thompson Epoch Development Team Department of Computer Science University of Illinois @ Urbana-Champaign
Technical Details
Message-ID:
<CTHOMP.93May27140213@hal.cs.uiuc.edu>Path:
arc1-ca.pugleaf.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!ux1.cso.uiuc.edu!cs.uiuc.edu!hal.cs.uiuc.edu!cthompReferences:
<1993May27.175127.13229@rchland.ibm.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fc7ee,9c62da5a7f28fd23 X-Google-Attributes: gidfc7ee,public X-Google-ArrivalTime: 1993-05-27 12:19:43 PST Newsgroups: gnu.epoch.misc Path: arc1-ca.pugleaf.net!gmd.de!newsserver.jvnc.net!howland.reston.ans.net!ux1.cso.uiuc.edu!cs.uiuc.edu!hal.cs.uiuc.edu!cthomp From: cthomp@hal.cs.uiuc.edu (Chuck Thompson) Subject: Re: Missing subject header In-Reply-To: mjruss@rchland.vnet.ibm.com's message of Thu, 27 May 1993 17:51:27 GMT Message-ID: <CTHOMP.93May27140213@hal.cs.uiuc.edu> Sender: cthomp@cs.uiuc.edu (Chuck Thompson) Organization: /home/staff/cthomp/.organization References: <1993May27.175127.13229@rchland.ibm.com> Date: Thu, 27 May 1993 19:02:12 GMT Lines: 63