April 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Several assertions failed for XEmacs 21.4-b1 "Copyleft", i586-pc-win32 23 years

Nickolay Pakoulin

> XEmacs Build Report generated by emacs-version > 21.4 (beta1) "Copyleft" XEmacs Lucid > with system-configuration > i586-pc-win32 > follows: > Contents of c:\SRC\xemacs-21.4\Installation: > (Output from most recent run of ./configure) OS: Windows_NT XEmacs 21.4-b1 \"Copyleft\" configured for `i586-pc-win32'. Building XEmacs in \"C:\\SRC\\xemacs-21.4\\nt\". Using compiler \"cl -nologo -W3 -Od -Zi -ML\". Installing XEmacs in \"c:\\Program Files\\XEmacs\\XEmacs-21.4-b1\". Package path is \"~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\xemacs-packages\". Compiling in support for Microsoft Windows native GUI. Compiling in support for XPM images. Compiling in support for GIF images. Compiling in support for PNG images. Compiling in support for JPEG images. Compiling in support for toolbars. Compiling in support for dialogs. Compiling in support for widgets. Compiling in support for native sounds. Compiling in fast dired implementation. Compiling in extra debug checks. XEmacs will be slow! ------------------------------------------------------------------------------- When running tests from lisp-test.el the following failures occured: FAIL: Assertion failed: (string= (format "%e" 100) "1.000000e+02") FAIL: Assertion failed: (string= (format "%E" 100) "1.000000E+02") FAIL: Assertion failed: (string= (format "%g" 1e-006) "1e-06") FAIL: Assertion failed: (string= (format "%G" 1e-006) "1E-06") FAIL: Assertion failed: (string= (format "%#e" 100) "1.000000e+02") FAIL: Assertion failed: (string= (format "%#E" 100) "1.000000E+02") FAIL: Assertion failed: (string= (format "%#g" 1e-006) "1.00000e-06") FAIL: Assertion failed: (string= (format "%#G" 1e-006) "1.00000E-06") FAIL: Assertion failed: (string= (format "%e" 100) "1.000000e+02") FAIL: Assertion failed: (string= (format "%E" 100) "1.000000E+02") FAIL: Assertion failed: (string= (format "%g" 1e-006) "1e-06") FAIL: Assertion failed: (string= (format "%G" 1e-006) "1E-06") FAIL: Assertion failed: (string= (format "%#e" 100) "1.000000e+02") FAIL: Assertion failed: (string= (format "%#E" 100) "1.000000E+02") FAIL: Assertion failed: (string= (format "%#g" 1e-006) "1.00000e-06") FAIL: Assertion failed: (string= (format "%#G" 1e-006) "1.00000E-06")

1 participants
0 comments

Re: [Sylvain Pasche <sypasche@yahoo.com>] Bug#94623: xemacs hangs when playing .au audio file 23 years

Jan Vroonhof

James LewisMoss <jimdres(a)mindspring.com> writes: > This is a bug reported by a Debian user. Any ideas what's wrong? My guess would be... > This initialization error calls perror(), a macro which expands to > message(). Then xemacs hangs in the bytecount_to_charcount() function > after some function calls. ... that this function is called with the latin1 string Succès, .. > > #0 0x8100ef4 in bytecount_to_charcount (ptr=0x4054381f "Succès", len=6) > at insdel.c:364 .. but expects the string to be in internal mule encoding. I am not sure there is an easy fix here, apart from defining perror as empty or fprintf(stderr,..) which would probably be a good idea anyway. Jan P.S. Is Sylvain running in an locale with French "error" messages?

2 participants
1 comments

Re: configure panic 23 years

Tyler Colbert

Several ways... I am still fairly new to the configure scene, so I'm not sure what's acceptable.. heres some ideas: Display wine version # (requires wine to be in path... ick) wine -v Default configuration assumes this file exists (can be changed at configure time) /usr/local/etc/wine.conf Ah-ha! here we go... this lib has to be installed.. libwine.so Let me know if I can help out (without spending much time at it :).. Tyler Colbert Senior Software Engineer Saffire Corporation -- Wishing I had email under XEmacs setup...:) Then my build-report with this information in it would have gone out correctly...

3 participants
2 comments

Re: configure panic 23 years

Tyler Colbert

Well, the Wine one can be resolved by attempting to link with libwine.so if that succeeds, then wine is installed (in the search path anyway). An additional search for the .so file might be prudent. But then again, as I said before, I'm far from experienced with configure. I have no experience with mingw32 however. Does mingw32 supply versions of most windows libraries? Perhaps changing configure to watch for a different windows library (instead of libgdi32) would resolve the issue with it? Or is there some way to detect it? As Stephen put it (but substitute mingw32 for Wine): Stephen J. Turnbull wrote: Is there an easy way to detect Wine? Ie, a unique library or header file, or some uniquely strange behavior in a more "generic" context (preferably identifiable in two or three lines of shell script or C code)? Tyler Colbert Senior Software Engineer Saffire Corporation -- beginning to hate sedit for email.

1 participants
0 comments

Re: (no subject) 23 years

Latchezar M. Dimitrov

If it's so horrible why is it in 21.1.14? >From: "Stephen J. Turnbull" <turnbull(a)sk.tsukuba.ac.jp> >MIME-Version: 1.0 >Content-Transfer-Encoding: 7bit >Date: Mon, 23 Apr 2001 15:43:54 +0900 >To: Steve Youngs <youngs(a)xemacs.org> >Cc: XEmacs Beta <xemacs-beta(a)xemacs.org> >Subject: Re: (no subject) >X-BeenThere: xemacs-beta(a)xemacs.org >X-Mailman-Version: 2.0.3 >List-Help: <mailto:xemacs-beta-request＠xemacs.org?subject=help> >List-Post: <mailto:xemacs-beta＠xemacs.org> >List-Subscribe: <http://lists.xemacs.org/lists/listinfo/xemacs-beta>, <mailto:xemacs-beta-request＠xemacs.org?subject=subscribe> >List-Id: XEmacs Beta Testers <xemacs-beta.xemacs.org> >List-Unsubscribe: <http://lists.xemacs.org/lists/listinfo/xemacs-beta>, <mailto:xemacs-beta-request＠xemacs.org?subject=unsubscribe> > >>>>>> "SY" == Steve Youngs <youngs(a)xemacs.org> writes: > > SY> OK. Is that on anybody's todo list? I think this should be > SY> taken care of _before_ this release goes public. > >image-mode is in the packages, right? image-mode problems are >unrelated to the release. Show me that it's fixed, and I'll consider >a patch to format-alist. > >In any case, we have _no_ labor committed to doing the things that >"should" be done, and we have a strong consensus for release. So I >did. The release _is_ "public"; I'm not going to take it back now. > >The criterion for promotion from "gamma" to "stable" is exactly that: >don't crash, don't destroy data. "Working image-mode" is a feature, >and IMHO lack of it should not delay promotion to stable. (But that's >mostly Vin's decision.) > > SY> IMO, this kind of customization would be beyond the newbie > SY> user. Especially seeing as though it doesn't seem to be > SY> documented anywhere. > >Something should be done about that, but there are far more important >things on my personal todo list, like teaching custom about Mule fonts >or at least documenting how to break one leg of `custom-set-faces'. >In any case, AFAIK the image-mode functions autoload, so just do M-x >image-mode. > > SY> In case anyone is interested, I've been 'autodetecting images' > SY> since about 21.2.30-something with no image-mode problems. > >Sure. But that mode allows a lot more than just detect and display, >and it was silently trashing some files or something. It wasn't just >randomly removed from that alist. It assaulted somebody and was sent >to Coventry for its crime because nobody was willing to fix it >properly. > >If you want to add it to 21.5 and see what happens, fine with me[1]. >Eventually I'll look at the file(s) and look up the threads. But for >21.4, paranoia rules. > > >Footnotes: >[1] But some people object to adding stuff to format-alist on general >principles. > >-- >University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN >Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 >_________________ _________________ _________________ _________________ >What are those straight lines for? "XEmacs rules." > Latchezar (Lucho) Dimitrov Wake Forest University, Winston-Salem, NC home: (336) 794-2094 grad.lab: (336) 758-4954 mailto:dimil01g＠wfu.edu or http://www.wfu.edu/~dimil01g/ lmdimi(a)mthcsc.wfu.edu lmdimi(a)pilot.mthcsc.wfu.edu ... Type fast, think slow. ... "Hippocratic Oath For Software Engineers"

3 participants
2 comments

Pressing ^C^C in bash shell buffer locks XEmacs-Cygwin 23 years

Karr, David

I reported this with report-emacs-bug, but I can't read newsgroups during the day (and I'm not aware of a mailing list that gets these), and I wanted to know if this was a known problem (I didn't see it in the bug list). After installing the beta (XEmacs-Cygwin) on 4/19, using the setup.exe installer, many things are quite a bit nicer than the released version. However, a very annoying symptom is if I press ^C^C in a shell buffer, it locks XEmacs. Every time. I have to kill the process. Ironically, the lack of the ability to kill simple "tail -f" scripts in NTEmacs was one of the main reasons I decided to try XEmacs-Cygwin.

1 participants
0 comments

glyphs are sort of broken in 21.4.1 (and later) 23 years

John H Palmieri

XEmacs 21.4.1 (same for 21.5.0) isn't backwards compatible in how it treats glyphs. On the other hand, 21.2.47 "worked". Suppose I paste this into the *scratch* buffer: (let ((glyph (make-glyph (vector 'xpm :file "~/alpha.xpm")))) (make-annotation glyph nil 'text (get-buffer (current-buffer))) (insert "TEXT\n") (make-annotation glyph nil 'text (get-buffer (current-buffer))) (insert "TEXT\n")) Then I go the end of this expression and hit C-x C-e. With 21.2.47, I get [picture]TEXT [picture]TEXT With 21.4.1, I get TEXT TEXT [picture][picture] Glancing at the documentation for make-annotation and the info page for "Annotation Basics", I think the old behavior is correct -- I think this is what the 'text layout is supposed to do -- but I'm not positive. -- J. H. Palmieri Dept of Mathematics, Box 354350 mailto:palmieri＠math.washington.edu University of Washington http://www.math.washington.edu/~palmieri/ Seattle, WA 98195-4350

1 participants
0 comments

[comp.emacs.xemacs] Netinstaller for 21.4 23 years

Adrian Aichner

Anybody want to take up this issue? Andy? See http://list-archive.xemacs.org/xemacs-patches/200104/msg00088.html and http://list-archive.xemacs.org/xemacs-patches/200104/msg00089.html for information on how I have documented the updating of the website setup.{exe,ini} from the ftp site. It's not automatic. You have to run make in Download/win32, then checkin the new files. Best regards, Adrian -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-115 D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

2 participants
4 comments

pictures to go along with my about.el changes 23 years

Ben Wing

-- ben I'm sometimes slow in getting around to reading my mail, so if you want to reach me faster, call 520-661-6661. See http://www.666.com/ben/chronic-pain/ for the hell I've been through.

1 participants
0 comments

[c.e.x] Re: Change in kill-region in 21.4? 23 years

Gunnar Evermann

This seems to explain some of the marking oddities we have seen recently. Any comments by whoever implemented the shifted-key stuff? Gunnar "James A. Crippen" <james(a)UnLambda.COM> writes: > On Fri, 20 Apr 2001, James A. Crippen wrote: > > > I just upgraded from 21.2.14 to 21.4.1. I'm really happy with the > > improvements in the new version, particularly with the increased speed and > > with the new interface magic (like gutters and their buffer tabs and the > > progress meter, both of which I think are wonderful). > > > > I've long had a set of keys bound for use with zmacs-regions, having spent > > some time actually using ZWEI/Zmacs and being spoiled with the visual > > feedback. <select> does `set-mark-command', then either <copy> does > > `copy-region-as-kill' or <cut> does `kill-region'. They've worked > > flawlessly since I bound them up until now. > > > > Now when I press <select>, move somewhere, and press either <copy> or > > <cut> instead of the zmacs-region going away it persists with the mark > > still set in the same place I originally set it with <select>. I can > > cancel the mark with C-g without a problem, and the selected text is > > either copied or killed to the kill ring and is perfectly yankable. > > > > I spent a few minutes looking at the source for `kill-region' and I can't > > see anything particularly obvious that would cause the mark to remain > > persistent. > > > > I tried manually setting the mark with C-space and then doing either of > > M-x copy-region-as-kill and M-x kill-region. Done this way they work > > properly and the zmacs-region goes away after the command. > > > > Here's the extract from my file of key defs. I can't see anything > > obviously wrong with them. > > > > (define-key (current-global-map) [(kp-home)] 'copy-region-as-kill) > > (define-key (current-global-map) [(kp-end)] 'kill-region) > > (define-key (current-global-map) [(kp-delete)] 'yank) > > (define-key (current-global-map) [(select)] 'set-mark-command) ;select is set to kp_5 with xmodmap > > (define-key (current-global-map) [(control select)] 'keyboard-quit) ;cancel a selection > > > > Either I'd like to know if this is a bug or if a workaround for the new > > functionality can be found. I can't tell what's wrong. > > After spending some quality time hunting around in simple.el and examining > all the various places where `zmacs-region-stays' is set to `t', I found > that the problem is due to the introduction of shifted motion > keys. Particularly, the shifted motion key support is done in terms of > *keys* and not in terms of the functions bound to them. This is so > Sh-left will extend the region but C-F (which is Sh-C-f) won't because > it's a different concept of motion key. The shifted motion effect is only > bound to keys which are explicitly motion keys, and usually don't serve > another purpose. Thus home, pgup, left, kp_end, etc are all considered > motion keys in this sense. > > The shifted motion support naturally requires that `zmacs-region-stays' be > set `t' for any shifted motion since otherwise the region wouldn't be > extended. Thus the region was being *extended* nowhere in particular > because my binding on kp-home for instance wasn't actually moving point > anywhere (it's just calling `copy-region-as-kill') but > `zmacs-region-stays' was being set anyway. Some work with Customize fixed > this problem and now my bindings are back to normal operation. I could > disable all the shifted region stuff and that'd probably fix the problem > too, but I haven't tried it. > > Thought people should know... > > 'james > > -- > James A. Crippen <james(a)unlambda.com> ,-./-. Anchorage, Alaska, > Lambda Unlimited: Recursion 'R' Us | |/ | USA, 61.2069 N, 149.766 W, > Y = \f.(\x.f(xx)) (\x.f(xx)) | |\ | Earth, Sol System, > Y(F) = F(Y(F)) \_,-_/ Milky Way. >

3 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 April 2001