October 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Jan Vroonhof

Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: > How are patches sent to xemacs-patches handled at the moment? Extremely ad-hoc. AFAICS nobody is applying patches to the packages at the moment. > Is anyone applying the patches sent there by people without cvs-write > access? Andy and Michael have applied most them. Normally Steve applies all that were left out, just before a new beta releases. > We should really make sure we do not lose any patches and that > everything that is applied to 21.1 is also applied to 21.2! Yes. We need some explicit tracker system (that is what xemacs-review is meant for but I am not sure it is working properly). There is a whole lot of patches to the packages that are "in the queue" for two months now. I would love it if there were some system in there somewhere. For instance there is a patch from _February_ about esound support that I still want look at (I didn't have esound at the time). Jan

1 participants
0 comments

applying patches 26 years

Gunnar Evermann

How are patches sent to xemacs-patches handled at the moment? Is anyone applying the patches sent there by people without cvs-write access? We should really make sure we do not lose any patches and that everything that is applied to 21.1 is also applied to 21.2! Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

Re: 21.2.19 crash in ldap on Solaris 2.7 26 years

Gunnar Evermann

Raymond Toy <toy(a)rtp.ericsson.se> writes: > >>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes: > > Raymond> I think this really is due to an invalid bytecode. As a quick test, I > Raymond> removed all of the elc files for eudc and re-did the test. Everything > Raymond> works as expected! > > Raymond> My eudc files were obtained from the 1999-07-29 sumo tarballs. > > Raymond> I'll try recompiling these files with 21.2.19 or perhaps some other > Raymond> version. (Has the byte-compiler changed between 21.1.x and 21.2.19?) > > That was it! I byte-compiled all of the eudc files with 21.1.7, and > everything seems to be working again. OK, could you now try to make it crash again, please? :-) I'd feel much better if we could find out what caused this, i.e. was it just a corrupted sumo-tarball or a real bug in the 21.2.19 bytecompiler... Gunanr

1 participants
0 comments

Re: Completion and partial width windows 26 years

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > A colleague pointed this out. Which version is used? > Split a frame vertically to get two side-by-side windows. Assume that > truncate-lines is T and truncate-partial-width-windows is T, the > defaults values, I think. Do a C-x b TAB to try to complete on a > buffer name. If the number of buffers is very large and the windows > are narrow, many of the buffer names are not visible because the lines > have been truncated. Note that this particularly ugly when using dialog boxes (which uses completion buffers in partial width windows. > There's no way, using the keyboard, to see names > that have scrolled off to the right. There should be. However there was a bug in autoshow mode that caused it not to work. This should be fixed in 21.2-CVS Jan

1 participants
0 comments

Re: 21.2.19 crash in ldap on Solaris 2.7 26 years

Oscar Figueiredo

>>>>> "Raymond" == Raymond Toy <toy(a)rtp.ericsson.se> writes: Raymond> I think this really is due to an invalid bytecode. As a quick test, I Raymond> removed all of the elc files for eudc and re-did the test. Everything Raymond> works as expected! Raymond> My eudc files were obtained from the 1999-07-29 sumo tarballs. Raymond> I'll try recompiling these files with 21.2.19 or perhaps some other Raymond> version. (Has the byte-compiler changed between 21.1.x and 21.2.19?) Raymond> That was it! I byte-compiled all of the eudc files with 21.1.7, and Raymond> everything seems to be working again. Raymond> Ray You mean even with Sun's LDAP libs ? Given the lack of documentation of ldap_set_option for this platform we'd be lucky here ! Oscar

1 participants
0 comments

widget-push-button-value-create broken in latest 21.2 CVS? 26 years

Adrian Aichner

When I evaluate the next line (widget-create 'push-button "Push me!") I get floowing *Backtrace*. I wasn't able to come up with a fix, although I tried. Andy will know, I'm sure :-) Later, Adrian Signaling: (wrong-type-argument listp :descriptor) nth(0 :descriptor) (list (nth 0 (aref gui 1)) (apply (function vector) (list ... ... text))) ) (backquote ((\, ...) [string :data ...])) ) (make-glyph (backquote (... ...))) ) (list (make-glyph (backquote ...)) (make-glyph (backquote ...)) (make-glyph (backquote ...))) ) (setq gui-glyphs (list (make-glyph ...) (make-glyph ...) (make-glyph ...))) ) (let* ((gui-button-shadow-thickness 1) (gui ...)) (setq gui-glyphs (list ... ... ...)) (laxputf widget-push-button-cache tag gui-glyphs)) ) (if gui-glyphs nil (let* (... ...) (setq gui-glyphs ...) (laxputf widget-push-button-cache tag gui-glyphs))) ) (unless gui-glyphs (let* (... ...) (setq gui-glyphs ...) (laxputf widget-push-button-cache tag gui-glyphs))) ) (cond (tag-glyph (widget-glyph-insert widget text tag-glyph)) ((and widget-push-button-gui ...) (unless gui-glyphs ...) (widget-glyph-insert-glyph widget ... ... ...)) (t (insert text))) ) (let* ((tag ...) (tag-glyph ...) (text ...) (gui-glyphs ...)) (cond (tag-glyph ...) (... ... ...) (t ...))) ) widget-push-button-value-create((push-button :value "Push me!" :args nil)) widget-apply((push-button :value "Push me!" :args nil) :value-create) (if (and button-begin (not button-end)) (widget-apply widget :value-create) (setq value-pos (point-marker))) ) (cond ((eq escape ?\%) (insert "%")) ((eq escape ?\[) (setq button-begin ...) (set-marker-insertion-type button-begin nil)) ((eq escape ?\]) (setq button-end ...) (set-marker-insertion-type button-end nil)) ((eq escape ?\{) (setq sample-begin ...)) ((eq escape ?\}) (setq sample-end ...)) ((eq escape ?n) (when ... ... ...)) ((eq escape ?t) (let* ... ...)) ((eq escape ?d) (let ... ...)) ((eq escape ?v) (if ... ... ...)) (t (widget-apply widget :format-handler escape))) ) (let ((escape ...)) (replace-match "" t t) (cond (... ...) (... ... ...) (... ... ...) (... ...) (... ...) (... ...) (... ...) (... ...) (... ...) (t ...))) ) (while (re-search-forward "%\$.\$" nil t) (let (...) (replace-match "" t t) (cond ... ... ... ... ... ... ... ... ... ...))) ) (let ((from ...) button-begin button-end button-glyph sample-begin sample-end doc-begin doc-end value-pos) (insert (widget-get widget :format)) (goto-char from) (while (re-search-forward "%\$.\$" nil t) (let ... ... ...)) (when (and button-begin button-end) (unless button-glyph ... ... ... ... ...) (widget-specify-button widget button-begin button-end) (set-marker button-begin nil) (set-marker button-end nil)) (and sample-begin sample-end (widget-specify-sample widget sample-begin sample-end)) (and doc-begin doc-end (widget-specify-doc widget doc-begin doc-end)) (when value-pos (goto-char value-pos) (widget-apply widget :value-create))) ) (progn (let (... button-begin button-end button-glyph sample-begin sample-end doc-begin doc-end value-pos) (insert ...) (goto-char from) (while ... ...) (when ... ... ... ... ...) (and sample-begin sample-end ...) (and doc-begin doc-end ...) (when value-pos ... ...)) (let (... ...) (set-marker-insertion-type from t) (set-marker-insertion-type to nil) (widget-put widget :from from) (widget-put widget :to to))) ) (prog1 (progn (let ... ... ... ... ... ... ... ...) (let ... ... ... ... ...)) (delete-region (point-min) (1+ ...)) (delete-region (1- ...) (point-max)) (goto-char (point-max))) ) (let ((inhibit-read-only t) before-change-functions after-change-functions) (insert "<>") (narrow-to-region (- ... 2) (point)) (goto-char (1+ ...)) (prog1 (progn ... ...) (delete-region ... ...) (delete-region ... ...) (goto-char ...))) ) (save-restriction (let (... before-change-functions after-change-functions) (insert "<>") (narrow-to-region ... ...) (goto-char ...) (prog1 ... ... ... ...))) ) (widget-specify-insert (let (... button-begin button-end button-glyph sample-begin sample-end doc-begin doc-end value-pos) (insert ...) (goto-char from) (while ... ...) (when ... ... ... ... ...) (and sample-begin sample-end ...) (and doc-begin doc-end ...) (when value-pos ... ...)) (let (... ...) (set-marker-insertion-type from t) (set-marker-insertion-type to nil) (widget-put widget :from from) (widget-put widget :to to))) ) widget-default-create((push-button :value "Push me!" :args nil)) widget-apply((push-button :value "Push me!" :args nil) :create) (let ((widget ...)) (widget-apply widget :create) widget) ) widget-create(push-button "Push me!") eval((widget-create (quote push-button) "Push me!")) eval-interactive((widget-create (quote push-button) "Push me!")) eval-last-sexp(nil) call-interactively(eval-last-sexp)

2 participants
2 comments

Re: [PATCHES] Re: (call-process ...) to return correct exit-statu s on NT 26 years

Adrian Aichner

>>>>> "Bill" == Bill Tutt <billtut(a)microsoft.com> writes: >> From: Adrian Aichner [mailto:aichner＠ecf.teradyne.com] >> >>>>> "Jonathan" == Jonathan Harris <jhar(a)tardis.ed.ac.uk> writes: >> >> I cannot interrupt >> (apply 'call-process "sleep" nil nil nil (list "30")) >> short of using Task Manager to "End Process". >> Bill> Eh? Why not? You can call TerminateProcess() on the process Bill> handle you dig up via OpenProcess() &/or CreateProcess(). Hi Bill! The issue with call-process is this: XEmacs on Unix uses non-blocking read for the child-process, so that the user can keyboard-quit out of it. At the moment int this_read = Lstream_read (XLSTREAM (instream), bufptr + nread, bufsize - nread); around line 482 in callproc.c of 21.2-b19 blocks until the process terminates. On Unix the Lstream implementation uses sys_read_1() for non-blocking reads. Does Windows95/98/NT have non-blocking read()? MSDN for Visual Studio 6.0 does not make me think so. Thanks for any help, Adrian Bill> e.g.: Bill> if (!TerminateProcess(hProcess, (UINT)<forced exit code>)) Bill> { Bill> <insert error handling here> Bill> } Bill> Bill

1 participants
0 comments

laser printer toner advertisement 26 years

art123＠visto.com

BENCHMARK SUPPLY 7540 BRIDGEGATE COURT ATLANTA GA 30350 ***LASER PRINTER TONER CARTRIDGES*** ***FAX AND COPIER TONER*** CHECK OUT OUR NEW CARTRIDGE PRICES : APPLE LASER WRITER PRO 600 OR 16/600 $69 LASER WRITER SELECT 300,310.360 $69 LASER WRITER 300, 320 $54 LASER WRITER LS,NT,2NTX,2F,2G & 2SC $54 LASER WRITER 12/640 $79 HEWLETT PACKARD LASERJET SERIES 2,3 & 3D (95A) $49 LASERJET SERIES 2P AND 3P (75A) $54 LASERJET SERIES 3SI AND 4SI (91A) $75 LASERJET SERIES 4L AND 4P $49 LASERJET SERIES 4, 4M, 5, 5M, 4+ (98A) $59 LASERJET SERIES 4000 HIGH YIELD (27X) $99 LASERJET SERIES 4V $95 LASERJET SERIES 5SI , 8000 $95 LASERJET SERIES 5L AND 6L $49 LASERJET SERIES 5P, 5MP, 6P, 6MP $59 LASERJET SERIES 5000 (29A) $135 LASERJET SERIES 1100 (92A) $49 LASERJET SERIES 2100 (96A) $89 LASERJET SERIES 8100 (82X) $145 HP LASERFAX LASERFAX 500, 700, FX1, $59 LASERFAX 5000, 7000, FX2, $59 LASERFAX FX3 $69 LASERFAX FX4 $79 LEXMARK OPTRA 4019, 4029 HIGH YIELD $135 OPTRA R, 4039, 4049 HIGH YIELD $135 OPTRA S 4059 HIGH YIELD $135 OPTRA E $59 OPTRA N $115 EPSON EPL-7000, 8000 $105 EPL-1000, 1500 $105 CANON LBP-430 $49 LBP-460, 465 $59 LBP-8 II $54 LBP-LX $54 LBP-MX $95 LBP-AX $49 LBP-EX $59 LBP-SX $49 LBP-BX $95 LBP-PX $49 LBP-WX $95 LBP-VX $59 CANON FAX L700 THRU L790 FX1 $59 CANONFAX L5000 L70000 FX2 $59 CANON COPIERS PC 20, 25 ETC.... $89 PC 3, 6RE, 7, 11 (A30) $69 PC 320 THRU 780 (E40) $89 NEC SERIES 2 LASER MODEL 90,95 $105 PLEASE NOTE: 1) ALL OUR CARTRIDGES ARE GENUINE OEM CARTRIDGES. 2) WE DO NOT SEND OUT CATALOGS OR PRICE LISTS 3) WE DO NOT FAX QUOTES OR PRICE LISTS. 4) WE DO NOT SELL TO RESELLERS OR BUY FROM DISTRIBUTERS 5) WE DO NOT CARRY: BROTHER-MINOLTA-KYOSERA-PANASONIC PRODUCTS 6) WE DO NOT CARRY: XEROX-FUJITSU-OKIDATA OR SHARP PRODUCTS 7) WE DO NOT CARRY ANY COLOR PRINTER SUPPLIES 8) WE DO NOT CARRY DESKJET/INKJET OR BUBBLEJET SUPPLIES 9) WE DO NOT BUY FROM OR SELL TO RECYCLERS OR REMANUFACTURERS WE ACCEPT GOVERNMENT, SCHOOL & UNIVERSITY PURCHASE ORDERS JUST LEAVE YOUR PO # WITH CORRECT BILLING & SHIPPING ADDRESS ****OUR ORDER LINE IS 770-399-0953 **** ****OUR CUSTOMER SERVICE LINE IS 800-586-0540**** ****OUR E-MAIL REMOVAL AND COMPLAINT LINE IS 888-532-7170**** ****PLACE YOUR ORDER AS FOLLOWS**** : BY PHONE 770-399-0953 BY FAX: 770-698-9700 BY MAIL: BENCHMARK PRINT SUPPLY 7540 BRIDGEGATE COURT , ATLANTA GA 30350 MAKE SURE YOU INCLUDE THE FOLLOWING INFORMATION IN YOUR ORDER: 1) YOUR PHONE NUMBER 2) COMPANY NAME 3) SHIPPING ADDRESS 4) YOUR NAME 5) ITEMS NEEDED WITH QUANTITIES 6) METHOD OF PAYMENT. (COD OR CREDIT CARD) 7) CREDIT CARD NUMBER WITH EXPIRATION DATE 1) WE SHIP UPS GROUND. ADD $4.5 FOR SHIPPING AND HANDLING. 2) COD CHECK ORDERS ADD $3.5 TO YOUR SHIPPING COST. 2) WE ACCEPT ALL MAJOR CREDIT CARD OR "COD" ORDERS. 3) OUR STANDARD MERCHANDISE REFUND POLICY IS NET 30 DAYS 4) OUR STANDARD MERCHANDISE REPLCAMENT POLICY IS NET 90 DAYS. NOTE NUMBER (1): PLEASE DO NOT CALL OUR ORDER LINE TO REMOVE YOUR E-MAIL ADDRESS OR COMPLAIN. OUR ORDER LINE IS NOT SETUP TO FORWARD YOUR E-MAIL ADDRESS REMOVAL REQUESTS OR PROCESS YOUR COMPLAINTS..IT WOULD BE A WASTED PHONE CALL.YOUR ADDRESS WOULD NOT BE REMOVED AND YOUR COMPLAINTS WOULD NOT BE HANDLED.PLEASE CALL OUR TOLL FREE E-MAIL REMOVAL AND COMPLAINT LINE TO DO THAT. NOTE NUMBER (2): OUR E-MAIL RETURN ADDRESS IS NOT SETUP TO ANSWER ANY QUESTIONS YOU MIGHT HAVE REGARDING OUR PRODUCTS. OUR E-MAIL RETURN ADDRESS IS ALSO NOT SETUP TO TAKE ANY ORDERS AT THIS TIME. PLEASE CALL THE ORDER LINE TO PLACE YOUR ORDER OR HAVE ANY QUESTIONS ANSWERED. OTHERWISE PLEASE CALL OUR CUSTOMER SERCICE LINE. NOTE NUMBER (3): OWNERS OF ANY OF THE DOMAINS THAT APPEAR IN THE HEADER OF THIS MESSAGE,ARE IN NO WAY ASSOCIATED WITH, PROMOTING, DISTRIBUTING OR ENDORSING ANY OF THE PRODUCTS ADVERTISED HEREIN AND ARE NOT LIABLE TO ANY CLAIMS THAT MAY ARISE THEREOF.

1 participants
0 comments

Re: replace-match: GNU vs XEmacs 26 years

Hrvoje Niksic

Darryl Okahata <darrylo(a)sr.hp.com> writes: > The best solution is would be to shift the XEmacs-specific option > over once place (make it the sixth option), Would it really be the best solution? XEmacs accepted that option long before FSF introduced their own extension. The extension existed, and people would have used it. By removing it or tossing it around, I'm afraid we send a "fuck you" note to those of our users who actually care to use our extensions. >From a different point of view, XEmacs is already full of the BUFFER arguments to various functions, where appropriate and otherwise. Those arguments are mostly harmless, but they only work well when they come last. This makes such functions harder to extend, as witnessed by this change. > An ugly, kludgy solution would be to test the type of the fifth > parameter; That's what I did for `buffer-string'; however, I did it only because the FSF version really made more sense. And yet, even with the compatibility fix, my solution broke in some cases and had to be fixed by wmperry.

2 participants
1 comments

Re: bad widget! 26 years

Michael Harnois

I'm not very bright, but if you tell me exactly what you'd like me to try I'd be happy to do it. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mharnois(a)willinet.net aa0bt(a)aa0bt.ampr.org God shows his contempt for wealth by the kind of person He selects to receive it. -- Austin O'Malley

1 participants
0 comments

2025

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 October 1999