November 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Broken makeinfo? [was: Re: Fix this] 24 years, 12 months

William M. Perry

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > > > Or maybe we don't care, because we don't care if people can build > > their own info docs or nobody ever does? > > If we ship the pre-built info docs with the source tarballs (as GNU > programs normally do), then people's ability to build their own docs > with obsolete makeinfo's is not of paramount importance. > > If we do not distribute the pre-built infos, we should at least try to > make sure people can build them with the versions of makeinfo that are > generally available. Depending on the latest-and-greatest versions of > software in order to build XEmacs is permissible, but annoying. > > > Or maybe we should think about abandoning (!) Texinfo in favor of a > > real DTD not defined by an implementation? > > Please please not that discussion again. Texinfo serves nicely for what > we want to do. Unless a LOT of the SGML display engine was done in C, which we want to avoid right now I think :) -bp

1 participants
0 comments

Re: LDAP extended and revamped 24 years, 12 months

William M. Perry

Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: > >>>>> "Robert" == Robert Pluim <rpluim(a)bigfoot.com> writes: > > Robert> Hrvoje Niksic writes: > >> Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: > >> > >> > *** IMPORTANT NOTE *** > >> > Due to the function renaming, this patch introduces an > incompatible > >> > change that breaks the packages using the current LDAP API, most > >> > notably EUDC and W3. > >> > >> Renaming doesn't necessarily entail breaking backward > compatibility. > >> If you want to be kind to your users, define functions with old > names > >> that do nothing except call the new functions. > > Robert> Wouldn't define-{obsolete,compatible}-function-alias be better > here? > Robert> Or are they intended only for 'core' emacs functions? > > Of course I've been concerned by this problem. But I don't know what to > do for the particular case of ldap-search. Currently ldap-search is the > name of the high-level search function (vs. ldap-search-internal which is > the low-level function). But according to the recent discussion on the > subject, what we want is the low-level function to be called ldap-search > and the high-level one called something else (my patch proposes > ldap-search-entries). In this particular case I don't know how to rename > backward compatible. That's the reason why I didn't provide > compatibility aliases at all, compatibility will be broken anyway... :-(( > > I am not satisfied by this but I've seen no workaround. I don't know how > many packages are currently using the LDAP API. I know of two: EUDC > which I maintain myself and W3. As I said, I can provide a compatible > version of EUDC as soon as necessary and I guess Bill is responsive > enough these days to do the same. Yup, if this gets approved, I'll hack up url-ldap.el to deal with it. I'll try to make it work with both interfaces if I can find a nice clean way. -bp

1 participants
0 comments

Re: LDAP extended and revamped 24 years, 12 months

Hrvoje Niksic

Robert Pluim <rpluim(a)bigfoot.com> writes: > > Renaming doesn't necessarily entail breaking backward > > compatibility. If you want to be kind to your users, define > > functions with old names that do nothing except call the new > > functions. > > Wouldn't define-{obsolete,compatible}-function-alias be better here? Yes, good point -- except when the calling conventions differ, and the compatibility functions have to do trivial processing to retrofit old arguments into new ones.

1 participants
0 comments

Re: xemacs 21.1.8 & hm--html--menus 1.12 24 years, 12 months

Jan Vroonhof

john s jacobs anderson <jacobs(a)xemacs.org> writes: > Pedro> directory, then i downloaded efs and xemacs-base. Now I'm > Pedro> trying to get hm--html--menus 1.12(as listed in the Manage > Pedro> Package menu) Except it says that it couldn't find it. I went > Pedro> searching for the file in the packages directory and there is > Pedro> no file that starts with an 'h'. It is indeed missing. It is part of the Sumo tarball.. > (Martin and/or Steve and/or Vinnie -- could somebody please get this > taken care of?) Andreas is working to finally get a new package release out of the door that should also fix this problem. Jan

1 participants
0 comments

Re: zero size widget crashes continue 24 years, 12 months

Michael Harnois

On Sat, 27 Nov 1999 20:18:54 -0800 (PST), Martin Buchholz <martin(a)xemacs.org> said: > Try disabling Andy's gutters like this in .emacs: That does seem to work around the problem for the time being, thanks. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mharnois(a)willinet.net aa0bt(a)aa0bt.ampr.org "Waiter, there's no fly in my soup!" - Kermit the Frog

4 participants
3 comments

Re: Broken makeinfo? [was: Re: Fix this] 24 years, 12 months

Hrvoje Niksic

"Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> writes: > Or maybe we don't care, because we don't care if people can build > their own info docs or nobody ever does? If we ship the pre-built info docs with the source tarballs (as GNU programs normally do), then people's ability to build their own docs with obsolete makeinfo's is not of paramount importance. If we do not distribute the pre-built infos, we should at least try to make sure people can build them with the versions of makeinfo that are generally available. Depending on the latest-and-greatest versions of software in order to build XEmacs is permissible, but annoying. > Or maybe we should think about abandoning (!) Texinfo in favor of a > real DTD not defined by an implementation? Please please not that discussion again. Texinfo serves nicely for what we want to do.

1 participants
0 comments

Re: LDAP extended and revamped 24 years, 12 months

Hrvoje Niksic

Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: > *** IMPORTANT NOTE *** > Due to the function renaming, this patch introduces an incompatible > change that breaks the packages using the current LDAP API, most > notably EUDC and W3. Renaming doesn't necessarily entail breaking backward compatibility. If you want to be kind to your users, define functions with old names that do nothing except call the new functions.

2 participants
1 comments

XEmacs Build Report for XEmacs-21.2.22 24 years, 12 months

XEmacs Build 'Bot

Good evening XEmacs beta testers. I am in the process of building XEmacs-21.2.22 for distribution. I have tested the attached configuration. Have a great day! Sincerely, The XEmacs Build 'Bot (revision 2) -- uname -a: SunOS miho 5.6 Generic_105181-05 sun4u sparc ./configure '--prefix=/usr/local/devel/xemacs-builds' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.2-b22 "Mercedes" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /usr/local/devel/xemacs-builds/xemacs-21.2 What installation prefix should install use? /usr/local/devel/xemacs-builds What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -O Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? none Runtime library search path: /usr/local/qt/lib:/usr/local/lib:/usr/local/X11R6/lib Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in support for Canna on Mule. Compiling in DSO module support. movemail will use "dot-locking" for locking mail spool files.

1 participants
0 comments

Re: xemacs 21.1.8 & hm--html--menus 1.12 25 years

John S. J. Anderson

>>>>> "Pedro" == Pedro Sam <p2sam(a)undergrad.math.uwaterloo.ca> writes: Pedro> Hi, I installed the big 3 xemacs tgz files from the xemacs21.1 Pedro> directory, then i downloaded efs and xemacs-base. Now I'm Pedro> trying to get hm--html--menus 1.12(as listed in the Manage Pedro> Package menu) Except it says that it couldn't find it. I went Pedro> searching for the file in the packages directory and there is Pedro> no file that starts with an 'h'. Thanks; I'll pass word on to the appropriate people to let them know that one of the packages has gone missing. (Martin and/or Steve and/or Vinnie -- could somebody please get this taken care of?) Thanks, john. -- ------------------------------------------------------------------------ John S Jacobs Anderson \ <URL:http://www.xemacs.org> You'll have to pry my Emacs from my cold \ jacobs(a)xemacs.org dead oversized control-pressing left pinky finger. -- Randal L. Schwartz

1 participants
0 comments

mule broken? 25 years

Jeff Miller

I have attempted to build a mule xemacs after a long time of not doing so..... I get the following error during the dump Loading /cvs/xemacs/xemacs/lisp/mule/mule-cmds.elc... Loading /cvs/xemacs/xemacs/lisp/mule/arabic.elc... Loading /cvs/xemacs/xemacs/lisp/mule/chinese.elc...*** Error in XEmacs initialization (void-variable ccl-encode-big5-font) *** Backtrace really-early-error-handler((void-variable ccl-encode-big5-font)) byte-code("..." [set-language-info-alist "Chinese-GB" ((setup-function . setup-chinese-gb-environment-internal) (charset chinese-gb2312 sisheng) (coding-system cn-gb-2312 iso-2022-7bit hz-gb-2312) (coding-priority cn-gb-2312 big5 iso-2022-7bit) (input-method . "chinese-py-punct") (features china-util) (sample-text . "Chinese (ESC$AVPNDESC(B,ESC$AFUM(;0ESC(B,ESC$A::SoESC(B) ESC$ADc:CESC(B") (documentation . "Support for Chinese GB2312 character set.")) ("Chinese") make-coding-system big5 "Coding-system of BIG5." (mnemonic "Zh/Big5") define-coding-system-alias cn-big5 define-ccl-program ccl-encode-big5-font 0 (r2 = (... - ?\!)) if r0 == charset-id chinese-big5-2 ((r2 += 6280)) ((r1 = ...) (r2 %= 157) (if ... ... ...)) "CCL program to encode a Big5 code to code point of Big5 font." set-charset-ccl-program chinese-big5-1 "Chinese-BIG5" ((charset chinese-big5-1 chinese-big5-2) (coding-system big5 iso-2022-7bit) (coding-priority big5 cn-gb-2312: this is from a cvs update today. I believe I also have the latest mule-base. Jeff

2 participants
2 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 November 1999