August 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Can Not Build Packages From CVS 24 years, 3 months

Andreas Jaeger

>>>>> Vin Shelton writes: > I just tried to build the packages from CVS and I got the following > errors. I build without MULE, in case that matters. > 'make' yields the following errors: > xemacs -no-autoloads -batch -eval "(push (expand-file-name \"mew\") load-path)" -l ./poe.el -l /usr/local/build/xemacs-packages-2000-08-05/package-compile.el -- mew -- mew/auto-autoloads.el > ^G > xemacs exiting.Cannot open load file: ./poe.el > make[2]: *** [mew/auto-autoloads.elc] Error 255 > ... I can't reproduce this one. > Loading /usr/local/xemacs/lib/xemacs-21.1.12/lisp/auto-autoloads... > Loading /usr/local/build/xemacs-packages-2000-08-05/libs/xemacs-base/auto-autoloads... > Compiling /usr/local/build/xemacs-packages-2000-08-05/os/os-utils/crypt.el... > While compiling toplevel forms in file /usr/local/build/xemacs-packages-2000-08-05/os/os-utils/crypt.el: > !! End of stream ((#<buffer " *Compiler Input*">)) > Done A missing closing brace, I've fixed this now and all other problems I noticed. I'm now running make clean;make again to search for remaining problems. Andreas -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de http://www.suse.de/~aj

1 participants
0 comments

Re: JDE doesn't build 24 years, 3 months

Andreas Jaeger

>>>>> Andreas Jaeger writes: > Michael, > do you know what's wrong? Does this work for you? I'm using XEmacs > 21.1.10 with Mule (will switch to 21.1.12 now): I've fixed this now - if this worked for anybody, you had a really broken setup. To everybody: If you add a new package, please add it to package-compile and check where you put your lisp dirs. Andreas 2000-08-16 Andreas Jaeger <aj(a)suse.de> * package-compile.el (package-directory-map): Add semantic. (package-name-to-directory): Handle jde special. Index: package-compile.el =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-packages/package-compile.el,v retrieving revision 1.19 diff -u -r1.19 package-compile.el --- package-compile.el 2000/08/16 08:33:34 1.19 +++ package-compile.el 2000/08/16 10:38:25 ＠＠ -89,6 +89,7 ＠＠ ("pcl-cvs" . "prog") ("prog-modes" . "prog") ("scheme" . "prog") + ("semantic" . "prog") ("sh-script" . "prog") ("vc" . "prog") ("vc-cc" . "prog") ＠＠ -161,7 +162,7 ＠＠ (expand-file-name "gnus/lisp" (file-name-as-directory dir))) ((equal package "pgnus") (expand-file-name "gnus/lisp" (file-name-as-directory dir))) - ((or (equal package "w3") (equal package "bbdb")) + ((or (equal package "w3") (equal package "bbdb") (equal package "jde")) (expand-file-name "lisp" (file-name-as-directory dir))) ((equal package "mew") (expand-file-name "mew" (file-name-as-directory dir))) -- Andreas Jaeger SuSE Labs aj(a)suse.de private aj(a)arthur.inka.de http://www.suse.de/~aj

1 participants
0 comments

face_cachels size limit? 24 years, 3 months

Ilya N. Golubev

Important property of any cache is limited capacity. If it grows too large, searches in it will take too much time and cache will slow down work rather than accelerating it. Does xemacs put any limit on size of `face_cachels' in `struct window'? <URL:info:internals> says: > the computer science theories of how to efficiently handle redisplay > are not well-developed. So it is nearly impossible to decide that particular performance test of redisplay shows that something is wrong. We have no estimates, how much resources should be used by current algorithm in which cases. We can not say: this (mis-) performance is inevitable unless we invent a considerably better algorithm; and this is apparently a bug / leak.

1 participants
0 comments

[ANN] New Package Checked into CVS 24 years, 3 months

Steve Youngs

I've just checked a new package into CVS. It's called 'eicq', it's an ICQ client for XEmacs. It doesn't have an awful lot of bells and whistles of ICQ clients like licq, but it does do the job pretty well. ,----[ Some features... ] | eicq uses version 5 protocol | send message/url to single or multi users or group | authorize, search, query and update meta user info | receive contact list transfer | register new user, change password | play sounds for different events | interactive customization through XEmacs Custom widgets | key binding, "scripting" in elisp | send/receive multi-lingual languages (with Emacs MULE) | a clickety click toolbar for the mouse impaired | | eicq cannot yet transfer files, chat, or anything that needs a | direct TCP connection. `---- I develop and test eicq on Linux x86 so consequently that's the only platform that I support right now. (sorry, Adrian, it won't run on NT yet :-( ) Please test and send me your questions/comments/queries/complaints. -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---| | It's a funny thing about life; if you refuse to accept | | anything but the best, you very often get it | |-----------------------------<mailto:youngs_s＠ozlinx.com.au>---|

1 participants
0 comments

Re: A New Package 24 years, 3 months

Steve Youngs

* simon <simon(a)josefsson.org> writes: > What's wrong with the UDP support already present in XEmacs? > `open-network-stream' is a compiled Lisp function > ... > Fifth argument PROTOCOL is a network protocol. Currently 'tcp > (Transmission Control Protocol) and 'udp (User Datagram Protocol) are > supported. When omitted, 'tcp is assumed. I haven't looked too closely into that, but I don't think it would work for me. I think I'd run into the same sorts of problems as with zenirc's dcc sends... ,----[ from zenirc-dcc.el ] | ; DCC `send' isn't yet implemented because emacs does not provide server | ; sockets. One way to get around this would be to write a small C or perl | ; program to do the listening and interface it with emacs. `---- -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---| | It's a funny thing about life; if you refuse to accept | | anything but the best, you very often get it | |-----------------------------<mailto:youngs_s＠ozlinx.com.au>---|

1 participants
0 comments

Re: A New Package 24 years, 3 months

Steve Youngs

* Stephen J Turnbull <turnbull(a)sk.tsukuba.ac.jp> writes: >>>>>> "Steve" == Steve Youngs <youngs_s(a)ozlinx.com.au> writes: Steve> It is free software, so, in your eyes it's not a dilemma? > Right. If you have the resources to provide more than one port, > great! If not, it's not your responsibility. The only thing that > we'd like is a polite response to the occasional inquiry about when > you plan to port to Platform X. :-) That response can be a flat > "never" and still be polite :-) Yep, I can handle that. I promise not to raise my voice once while replying to requests of ports. :-) And I won't even use a canned form letter :-) Seriously, I hold XEmacs [1] in very high regard, it's a fantastic piece of software that is very well respected in the community. I wouldn't dream of doing anything to harm it's image. Steve> Should I just submit the package as is and mark the Steve> description "For Linux x86 only - please port me"? > Yes, but I would phrase that as "developed and tested on Linux x86; > only supported on that platform" (you do plan to support it with the > occasional bugfix and coordinating 3rd party contribs, right?) Definitely. I've already spent a great deal of time on this I'm not about to waste it by not maintaining it. Footnotes: [1] that includes all the developers, beta testers and anybody else who helps make XEmacs what it is. -- |---<Regards, Steve Youngs>-----------[GnuPG KeyID: EFD82ED2]---| | It's a funny thing about life; if you refuse to accept | | anything but the best, you very often get it | |-----------------------------<mailto:youngs_s＠ozlinx.com.au>---|

1 participants
0 comments

Re: [PATCH] psgml-fs.el, psgml-html.el, psgml-info.el to provide themselves, autoload `html-quote-region' 24 years, 3 months

Adrian Aichner

>>>>> "Jerry" == Jerry James <james(a)eecs.ukans.edu> writes: Jerry> Andreas Jaeger <aj(a)suse.de> wrote: >> I'm not sure - the last integration was done by Jerry and our version >> is AFAIK still different from the upstream version. But I prefer to >> have the discrepancies as small as different. Jerry> Yes, the XEmacs version is still different from the Jerry> upstream version. I have sent email to Lennart many times Jerry> with patches that reduce the difference and offers of help Jerry> for eliminating the rest. I have yet to receive a reply Jerry> from him. Meanwhile, I have seen him post to Usenet on a Jerry> couple of occasions, so he is still around. Draw your own Jerry> conclusions. -- Jerry James I'll wait for a reply from Lennart for a few days. If I don't get any, I suggest I commit the change if you don't find anything technically wrong with it. What's your thought on this? Best regards, Adrian -- Adrian Aichner <adrian(a)xemacs.org>

1 participants
0 comments

Re: Two questions re. PSGML validation issues 24 years, 3 months

Adrian Aichner

>>>>> "Jerry" == Jerry James <james(a)eecs.ukans.edu> writes: Jerry> Adrian Aichner <aichner(a)ecf.teradyne.com> wrote: >> While implementing HTML document validation for our next-generation >> XEmacs website I have some questions about PSGML: >> >> 1. How can I access the DTD doctype of buffer after validating it >> (i.e. it has been parsed and all information should be available >> via sgml-dtd-info)? Jerry> If you just want the generic type (like "HTML"), then Jerry> (sgml-dtd-doctype sgml-dtd-info) should do the trick. If Jerry> you want the name of the file containing the DTD, use Jerry> (sgml-declaration). If you want the public identifier of Jerry> the DTD, then I'm afraid that you are out of luck. As far Jerry> as I can see, that information is discarded after the Jerry> public identifier is mapped to a file. The file name is Jerry> probably better anyway, since multiple forms of an Jerry> identifier can be mapped to the same file. Here's what I came up with[1]: (format "<!DOCTYPE HTML PUBLIC \"%s\">\n" (sgml-entity-text (sgml-lookup-entity "HTML.Version" (sgml-dtd-parameters sgml-dtd-info)))) I'm afraid this would not work from XML DTDs. Given the above, do you have a suggestion to make this work both for HTML and XML? Does XEmacs PSGML package 1.18 come with full XML support? I can't seem to find a full XML DTD in it? How would one use it to create XML documents? >> 2. How can I access the error message reported by >> (sgml-next-trouble-spot)? Jerry> Those messages are generated with (message ...), so Jerry> (current-message) should get the most recent one. I think. Jerry> But what you wrote next makes me think I misinterpreted Jerry> your question. Did I misunderstand you? I would like to generate an error message parsable by compilation-mode to jump to those errors via next-error. My current solution is to redefine sgml-log-warning: ;; APA: Encapsulate sgml-log-warning to capture batch-psgml-last-warning. (defun batch-psgml-validate-log-warning (format &rest things) (setq batch-psgml-last-warning (apply 'format format things)) (when sgml-throw-on-warning (throw sgml-throw-on-warning t))) (fset 'sgml-log-warning 'batch-psgml-validate-log-warning) I'll give your suggestion to use (current-message) a shot. Best regards, Adrian >> I tried using >> (if sgml-last-element >> (setq context (sgml-element-context-string sgml-last-element))) >> but sgml-last-element is nil even though an error occured. To be >> honest, it worked in a debugging session of XEmacs, but not in a >> freshly started one. Jerry> Regards, Jerry> -- Jerry> Jerry James Jerry> Email: james(a)eecs.ukans.edu Jerry> WWW: http://www.eecs.ukans.edu/~james/ Footnotes: [1] See http://xemacs.sourceforge.net/batch-psgml-validate.el for the whole file used for XEmacs website validation.

1 participants
0 comments

Re: Two questions re. PSGML validation issues 24 years, 3 months

Jerry James

Adrian Aichner <aichner(a)ecf.teradyne.com> wrote: > While implementing HTML document validation for our next-generation > XEmacs website I have some questions about PSGML: > > 1. How can I access the DTD doctype of buffer after validating it > (i.e. it has been parsed and all information should be available > via sgml-dtd-info)? If you just want the generic type (like "HTML"), then (sgml-dtd-doctype sgml-dtd-info) should do the trick. If you want the name of the file containing the DTD, use (sgml-declaration). If you want the public identifier of the DTD, then I'm afraid that you are out of luck. As far as I can see, that information is discarded after the public identifier is mapped to a file. The file name is probably better anyway, since multiple forms of an identifier can be mapped to the same file. > 2. How can I access the error message reported by > (sgml-next-trouble-spot)? Those messages are generated with (message ...), so (current-message) should get the most recent one. I think. But what you wrote next makes me think I misinterpreted your question. Did I misunderstand you? > I tried using > (if sgml-last-element > (setq context (sgml-element-context-string sgml-last-element))) > but sgml-last-element is nil even though an error occured. To be > honest, it worked in a debugging session of XEmacs, but not in a > freshly started one. Regards, -- Jerry James Email: james(a)eecs.ukans.edu WWW: http://www.eecs.ukans.edu/~james/

1 participants
0 comments

Re: [PATCH] psgml-fs.el, psgml-html.el, psgml-info.el to provide themselves, autoload `html-quote-region' 24 years, 3 months

Jerry James

Andreas Jaeger <aj(a)suse.de> wrote: > I'm not sure - the last integration was done by Jerry and our version > is AFAIK still different from the upstream version. But I prefer to > have the discrepancies as small as different. Yes, the XEmacs version is still different from the upstream version. I have sent email to Lennart many times with patches that reduce the difference and offers of help for eliminating the rest. I have yet to receive a reply from him. Meanwhile, I have seen him post to Usenet on a couple of occasions, so he is still around. Draw your own conclusions. -- Jerry James

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 August 2000