October 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: *** PANIC *** The C compiler can no longer build working executables. 26 years

Vin Shelton

>>>>> On 20 Oct 1999 14:56:16 -0400, Vin Shelton <acs(a)xemacs.org> said: Andy wrote: >> So I don't understand why you are having this problem. Certainly >> no-one else has reported it. Vin> I have to admit I didn't report it, but I had this problem until I Vin> fiddled with my libXaw3d libraries. I had to create a link. I'll Vin> check what I did when I get home. I'm configuring with the following option: --with-widgets=athena3d In order to make this work, I had to make this link: lrwxrwxrwx 1 root root 15 Oct 1 21:09 /usr/X11R6/lib/libXaw3d.so -> libXaw3d.so.6.1 I could be wrong, but I think this used to 'just work' before Martin(?)'s recent configuration changes. HTH, vin

1 participants
0 comments

Why (call-process ...) cannot be keyboard-quit on native NT 26 years

Adrian Aichner

Hello All, perhaps someone could help me with this: (apply 'call-process "sleep" nil nil nil (list "30")) cannot be interrupted within 30 seconds. The C-g is only accepted when sleep returns after 30 seconds. The reason for this is that on Windows NT read_allowing_quit() used to read from the XEmacs stdin Lstream connected to the child-process calls int sys_read_1 (int fildes, void *buf, size_t nbyte, int allow_quit) { int rtnval; /* No harm in looping regardless of the INTERRUPTIBLE_IO setting. */ while ((rtnval = read (fildes, buf, nbyte)) == -1 && (errno == EINTR)) { if (allow_quit) REALLY_QUIT; } return rtnval; } Problem is that on NT the read() call in sys_read_1(...) is not interruptible by C-g. Therfor the "if (allow_quit) { ... }" test is only done after the child process completes. Any ideas what I could do to make (call-process ...) interruptible on Windows NT native? Is there a way to make read(...) interruptible on Windows NT? Best regards, Adrian

1 participants
0 comments

Re: *** PANIC *** The C compiler can no longer build working executables. 26 years

Vin Shelton

Andy wrote: > So I don't understand why you are having this problem. Certainly > no-one else has reported it. I have to admit I didn't report it, but I had this problem until I fiddled with my libXaw3d libraries. I had to create a link. I'll check what I did when I get home. - vin

1 participants
0 comments

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

Adrian Aichner

>>>>> "Katsumi" == Katsumi Yamaoka <yamaoka(a)jpl.org> writes: Katsumi> May I bother you? How do I create widget buttons in Katsumi> latest 21.2 CVS? Hello Yamaoka San, this code works for me in latest 21.2 CVS after applying Andy's recent patch: Subject: Re: widget-push-button-value-create broken in latest 21.2 CVS? To: Adrian Aichner <aichner(a)ecf.teradyne.com>, XEmacs Beta List <xemacs-beta(a)xemacs.org>, xemacs-patches(a)xemacs.org Date: Tue, 19 Oct 1999 08:09:01 +0100 Message-Id: <3.0.5.32.19991019080901.009ae290(a)london.beasys.com> HTH, Adrian Katsumi> (widget-create 'push-button Katsumi> :tag "Hello" Katsumi> :action (lambda (&rest args) (message "Hello"))) Katsumi> No button appears in *scratch* buffer with this code. :-<

2 participants
1 comments

Re: replace-match: GNU vs XEmacs 26 years

Hrvoje Niksic

Darryl Okahata <darrylo(a)sr.hp.com> writes: > > 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. > > Well, I suggested that on the theory that we want to keep XEmacs as > compatible as possible. Yes, this has often be the way we did things. But I'm not sure if it's a good idea, really. Smart people have said before: the more we try to emulate FSFmacs, the more we suffer. I'm guilty of that sin myself. I will not force redemption on anyone, though. If you take responsibility over the code, it's mostly up to your best judgement. The review board can still veto your decision, but I don't think that's likely to happen. > I understand that XEmacs is already incompatible in a number of > areas, but this parameter seemed almost like a > inadvertent/gratuitous incompatibility (perhaps I'm wrong, but that > was my first impression). It is my impression too, but the point is that Stallman doesn't seem to care about compatibility, so it's always up to us to make incompatible changes. How much more of that are we going to cater to? > > 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. > > Well, I'm willing to implement either (or some other) solution. I > just want to know what to do. Decide for yourself. If you want to implement the change, the buffer-string solution would do, I guess. :-(

2 participants
1 comments

Tabs still flickering madly 26 years

Darryl Okahata

Well, the flickering tab problem is still with us, but in a somewhat different form. I did a cvs update of 21.2 around 4PM PST (2300GMT), October 18. Here's the test case for reproducing the problem: * Use these X resources (I don't know if these are really necessary to reproduce the bug, but I'm listing them anyway): Emacs*EmacsFrame.default.attributeBackground: black Emacs*EmacsFrame.default.attributeForeground: white Emacs*EmacsFrame.geometry: 177x55+6+20 Emacs*cursorColor: green Emacs.default.attributeFont: -*-Fixed-Medium-O-*-*-*-130-*-*-*-*-*-* * Use the attached .emacs file (called "bad.emacs" -- rename it to .emacs). * cd to XEmacs's src subdirectory, and run: ./xemacs * Use M-< to move the cursor to the beginning of the scratch buffer. At this point, the XEmacs windows looks like the attached "good.gif" (I resized the window to make the .gif file nice and small). * Do: C-x 3 # Split window vertically. At this point, the window looks like "bad.gif". Note the alignment of the right-hand window: the top of the text is cut off. Also note the top position of the right-hand window's vertical scroll bar. Based upon what's been discussed earlier, I suspect that this is a problem that's eventually causing some of the flickering. [ Hmmm. Looking some more at the gif file, there also seems to be a minor redisplay problem in the left-hand window. Look at the "intersection" where the horizontal and vertical scroll bars meet; there appears to be some "left-over text" from before the window split. ] * Do: C-x C-o # Move cursor to the other window. At this point, the window looks like "bad2.gif". Note that the bottom of the tab line has been totally erased. * Do: C-x C-o # Move cursor to the other window. At this point, the entire tab area has been erased, and is black. If you move the mouse into the tab area, the mouse cursor starts flickering badly. The truncated, top part of the text in the right-hand window is also flickering. I guess something is being continuously erased, or drawn and erased. (I've also attached a copy of my "Installation" file.) -- Darryl Okahata darrylo(a)sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.

2 participants
1 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: Completion and partial width windows 26 years

Raymond Toy

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Raymond Toy <toy(a)rtp.ericsson.se> writes: >> A colleague pointed this out. Jan> Which version is used? He was using 21.1.7 I believe. The same happens in 21.2.19, too. >> There's no way, using the keyboard, to see names >> that have scrolled off to the right. Jan> There should be. However there was a bug in autoshow mode that caused Jan> it not to work. This should be fixed in 21.2-CVS Agreed. CVS access is not possible from work, so I'll just have to wait for b20. Ray

1 participants
0 comments

Re: 21.2.19 crash in ldap on Solaris 2.7 26 years

Raymond Toy

>>>>> "Gunnar" == Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: >> That was it! I byte-compiled all of the eudc files with 21.1.7, and >> everything seems to be working again. Gunnar> OK, could you now try to make it crash again, please? :-) Sure, I saved the original elc's. Gunnar> I'd feel much better if we could find out what caused this, i.e. was Gunnar> it just a corrupted sumo-tarball or a real bug in the 21.2.19 Gunnar> bytecompiler... I sent the traceback from the original crash. If you want more info about this, I'll need a little guidance. I don't know anything about the bytecode compiler or bytecode interpreter. Ray

1 participants
0 comments

Re: 21.2.19 crash in ldap on Solaris 2.7 26 years

Raymond Toy

>>>>> "Oscar" == Oscar Figueiredo <Oscar.Figueiredo(a)di.epfl.ch> writes: Oscar> You mean even with Sun's LDAP libs ? Given the lack of documentation of Oscar> ldap_set_option for this platform we'd be lucky here ! No, I'm using the UMICH LDAP libs. Recall that if I setq use-dialog-box that it didn't crash on the dialog box, but then it crashed in ldap_set_option. I think our conclusion NOT to use Sun's ldap libs still holds. Ray

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