July 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Lisp Package updates for XEmacs-21.0-pre8-pre2 (aka b51-pre2) 26 years

SL Baur

I committed one small change to configure by Jan Vroonhof to fix a configure typo. If you haven't broken on an error message about `dash_r' or "-rpath" or "-R" you don't need to bother with it. The major architectural change is that Lisp packages can be built from a top-level make without requiring XEmacs/Mule. Modify XEmacs.rules and comment out the line reading: BUILD_MULE=t As of today, I consider it fair game to start reporting bugs on global builds from CVS[1]. The updated package-get-base file is named: package-get-base.el-21.0-pre8-pre2 Lisp Package Updates nonfunctional, nonuser-visible build only changes: For CVS the files: ChangeLog, Makefile, XEmacs.rules, package-compile.el, and oa/Makefile were updated. calendar-1.05 empty file diary-ins.el removed footnote-1.04 tm-1.11 apel-1.05 edict-1.04 egg-its-1.08 leim-1.08 skk-1.08 auctex-1.10 allow building with XEmacs/no-Mule vm-1.10 vc-1.10 package-info.in fix (remove `dump t' marking) Sun-1.07 tooltalk-1.06 dumped-lisp.el removed Updated Packages with user-visible changes prog-modes-1.08 Postscript syntax fix for '}' edit-utils-1.26 func-menu.el-2.57 mine-1.07 V1.9 (Hrvoje Niksic patches from xemacs-beta merged) gnus-1.23 Gnus-5.6.27 xemacs-devel-1.14 find-func.el update locale-1.08 German Menubar, allowing building with XEmacs/no-Mule tpu-1.05 package-info.in typo fix, Lucid->XEmacs eudc-1.20 Major update, bbdb and LDAP backends now supported calc-1.07 Port to 21.2, Lucid->XEmacs mule-base-1.20 TUTORIAL run-time fix, allow building with XEmacs/no-Mule pc-1.11 Allowing toggling of selection deletion behavior vc-cc-1.06 Fix package-info.in (remove `dump t' marking), menu fix texinfo-1.11 Character quote syntax fix Footnotes: [1] Not that I'll have a whole lot of time to do much about it in the near term.

1 participants
0 comments

Re: Problem with PNG 26 years

SL Baur

An upgrade to libpng-1.0.2 solves the squished image problem, except now the transparent background doesn't appear to get handled optimally. It appears white in XEmacs, gray in display and black in xv.

1 participants
0 comments

Problem with PNG 26 years

SL Baur

The attached PNG (pengbrew_160x160.png) works in display or xv, but displays oddly in XEmacs (24 bit color depth). I've attached a side-by-side screen shot to show what I see. The bad PNG: The bad PNG alongside display showing it correctly:

2 participants
1 comments

xemacs-21.0-b50: --with-gif failure on Solaris 2.6 26 years

Michael Kifer

Configure dies with a PANIC msg. The config.log file says: /usr/local/sparc-sun-solaris2.5.1/bin/ld: cannot open -lgifreader: No such file or directory Does --with-gif now require gifreader? Xemacs 20.4 doesn't need it to compile. --michael

1 participants
0 comments

Re: [PATCH] Re: Core dump in Benadir 26 years

SL Baur

Marcus Thiessel <thiessel(a)hpbbse.bbn.hp.com> writes in xemacs-beta(a)xemacs.org: > SL Baur writes: ... >> You can get Canna from ftp://ftp.xemacs.org/pub/xemacs/aux/. >> >> I'm using a hacked Canna 3.5b2. > I downloaded a copy and it is compiling. O.K. >> I'm not submitting this patch to xemacs-patches yet. All relevant patches are now in CVS. >> Please test it if your XEmacs/Mule is crashing. > I let you if I have the results. O.K. Thanks.

1 participants
0 comments

Re: scheme - my opinion 26 years

Michael Sperber

>>>>> "Holger" == Holger Schauer <schauer(a)coling.uni-freiburg.de> writes: >>>>> "SJT" == Stephen J Turnbull schrieb am Fri, 17 Jul 1998 12:28:15 +0900 (JST): SJT> We want an engine that will be usable on all platforms we SJT> support, an efficiency improvement on most of them, and a big SJT> efficiency improvement on as many as possible. Holger> How many of the Scheme implementations mentioned does are ruled out by Holger> this commitment (to which I totally agree) ? None. The efficiency varies greatly among them, but all are vastly faster than Elisp. -- Cheers =8-} Chipsy Friede, Völkerverständigung und überhaupt blabla

1 participants
0 comments

YAG[1]: XEmacs 21.0-pre8-pre1 "Corsican" has been committed to CVS 26 years

SL Baur

I've committed the patches so far for XEmacs-21.0pre8 (b51). They're bug fixes and documentation changes. A couple of coredumping bugs should be gone. I plan on making pre8 as a full distribution some time next week or thereabouts. package-get-base.el has *not* been updated, though it doesn't make too much difference. A new version will be committed after the highest priority pending package changes are committed. There's a patch from virgin 21.0-pre7 "Benadir" and what would have been 21.0-pre6 "Belgian Fawn" in ftp://ftp.xemacs.org/pub/xemacs/beta/testing/xemacs-21.0-b50-21.0-b51-pre.... to 21.0 pre8 "Corsican" -- GC bug fix from Gunnar Evermann. -- Miscellaneous documentation updates from Adrian Aichner and Michael Sperber. -- Miscellaneous Lisp bug fixes from Jan Vroonhof, Greg Klanderman and John Jones. -- DEC OSF support from Martin Buchholz -- Unitialized builtin variable bug fix from Altrasoft -- Miscellaneous bug fixes from Altrasoft Footnotes: [1] (eq YAG "Yet Another Goat) => t

1 participants
0 comments

Re: no inline mime images :-( 26 years

Jareth Hein

Olivier Galibert <galibert(a)pobox.com> writes: > On Fri, Jul 24, 1998 at 07:29:04PM -0400, Kyle Jones wrote: > > Since XV and ImageMagick display images much more > > reliably than XEmacs, maybe we should be asking John Bradshaw > > and/or the ImageMagick folks where they get their weed. I bet > > it's all custom code, instead of these finicky libraries. > > xv uses libjpeg, libtiff and libpng. Only the gif code is custom. > > This may be considered as good news. It means it is possible to do > something very stable with these libraries. What I think is a bit wierd is that I (obsensibly the one doing most of the maint/meddling of the image code) have not had ANY image related crashes since 20.4. Some image artifacts, yes, and we've managed to clean those up (there is still something wierd about mouse cursors, but I'm not playing with that right now). I use XEmacs quite a bit for image display via image mode, as well as via gnus and email. As I guess I'm the one who's mucked up the image code the most, I will fix any problem that I can reproduce. Send me the broken files or whatever, and try to give me as much info about your environment as you can. I have access to HPUX, Solaris-x86 2.6, Linux and IRIX 6.2/6.3 at the moment, so I can probably duplicate quite a variety of setups. I want this crap stable, dammit! :-/ -- Jareth Hein | jareth(a)camelot.co.jp | ハインジェラス Toolsmith & Program lead | http://www.camelot.co.jp | 開発部チーフ Camelot Software, Ltd. | |（株）キャメロット "It's a sad sign of the times when 'political machine' is redefined to include 'main-line battle tank'" - Ambassador Grossblunder

1 participants
0 comments

Call for proposals on XEmacs architectural changes 26 years

Ben Wing

(Note from Martin: since Ben currently has I/O problems, I am re-posting his message with the aim of making it more readable (and more read!)) Ben sez: I'm in the process of making a web site about the architectural changes to XEmacs that I think should be made both in the near future and further off. I hope to have a preliminary version of this site up within two weeks or so. The intent is to provide a vision of what should be done to XEmacs, how it should be done, and in what order, rather than the current haphazard process which I might characterize as, ``Implement now, think later.'' The contents of the site, of course, will be my own opinion, and many others may not agree with it and may go ahead and implement what they feel like doing regardless of what my suggestions may be. At the very least, however, I hope to provide some guidance and a starting point for discussion. I'm quite interested in proposals from other people about architectural changes, and this is the purpose of this e-mail message. Part of my site will include proposals from other people as well as including the text of the proposals themselves (if the author consents). I will include a link to the canonical home page for the proposal as maintained by the author, if such a page exists. I currently know of two pages containing XEmacs proposals, which are: - Joel Peterson's redisplay rewrite page http://www.geocities.com/SiliconValley/Peaks/3639/new-redisplay.txt - Michael Sperber's Lisp engine changes http://www-pu.informatik.uni-tuebingen.de/users/sperber/xemacs/next-gener... The sort of proposals that I'm looking for should not merely be opinions about what should be done, but rather, detailed proposals concerning specific architectural changes. Possible issues that could be addressed in these proposals are, for example, -- A specification of a change to be made, how the existing code will be changed and what the mechanism behind the new implementation will be. -- An examination of the strengths and weaknesses of different possible implementations designed to solve a specific problem. -- An analysis of what exactly is causing a specific problem to happen (for example, an analysis of profiling data for many common start- up scenarios to determine why XEmacs start-up is so slow). Along with any proposal that advocates a specific architectural change, it would really nice if the following issues were addressed: 1) Why is this change important or necessary? 2) How important or necessary is this change in relation to other architectural changes being considered? 3) What benefit--direct or indirect--will the users of XEmacs see? 4) How much work will it take to make this change? 5) How long do you think it will be before this change is finished and integrated into XEmacs? 6) What other impacts or dependencies will this project have? For example, any change to the Lisp engine that implements any major language changes will have an impact in that a lot of existing Lisp code will have to be rewritten, especially start-up code and other code that is part of the XEmacs base. Additional dependencies for this change would include conversion programs between XEmacs Lisp and whatever the new language is, and emulators probably in both directions, byte code compilers, byte code disassemblers, debuggers, etc. I am happy to provide the canonical home page for peoples' proposals, or to mirror proposals whose home pages are elsewhere, in order to make it easier for somebody who is reading my site. Alternatively, I can just provide links to those pages, and I'll probably do so in the beginning, until I set things up a little better. There are some particular proposals that I would like to see written. These include, for example, -- Steven Turnbull's fixed width buffer changes. -- Olivier Galibert's portable unexec replacement. -- Kyle Jones's portable unexec replacement. -- Some theory behind Kyle Jones's minimal tagbits, aka `gung-ho' implementation. -- Ideas from Kirill and Kyle concerning implementing dialog boxes. (I'm also going to be providing my own proposal for this.) -- Ben Wing

2 participants
1 comments

Re: [PATCH] XEmacs obsolete function 26 years

SL Baur

Colin Rafferty <craffert(a)ms.com> writes in xemacs-beta(a)xemacs.org: ... >> O.K. But look at the more complete patch I sent in which changes all >> the obsolete symbols not just the one Didier changed. > I didn't notice that this was a subset of your original patch. You're right. My mistake. I missed those. > I'll see about incorporating your patch. >> Speaking of backwards compatibility, I don't like the way the XEmacs >> M-TAB binding for `ispell-complete-word' gets overwritten by BBDB 2. > Neither do I, but I didn't notice it until just now. Can you make a switch or something like that? I don't mind BBDB insinuating itself into message mode, but I'd like some choice about what keys it defines. > I think the concept is fine, but I would rather have a pointer to > message-x (or better, a (condition-case nil (require 'message-x) ...)), > and do away with the `define-key' altogether). ? Half of a thought?

1 participants
0 comments

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

XEmacs-Beta July 1998