April 2006 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Bug: 21.4.18] gnus 5.10.7 not rendering Latin-1 headers 18 years, 8 months

Mike Kupfer

>>>>> "Reiner" == Reiner Steib <reinersteib+gmane(a)imap.cc> writes: Reiner> I don't see any reason not to improve compatibility in `mm*.el' Reiner> for XEmacs (MULE or non-MULE). But since most of the currently Reiner> active Gnus developers don't use XEmacs, I'm afraid this won't Reiner> happen unless you (i.e. XEmacs developers and users) contribute Reiner> patches or concrete proposals. I'm willing to help as best I can, but I could use some clues, either from the gnus or XEmacs folks. mm-coding-system-p appears to be trying to figure out what coding system interface to use, with the choices being find-coding-system, coding-system-p, and mm-get-coding-system-list. Are any of these standard Emacs or XEmacs interfaces? The docstring for mm-coding-system-p says it returns "a coding system object in XEmacs". The XEmacs Lisp reference talks about coding systems, under MULE. Does that mean that coding system objects only exist in MULE XEmacs? What should (mm-coding-system-p 'iso-8859-1) return in non-MULE XEmacs? mike

6 participants
10 comments

Re: Bignum support still broken on powerpc (ping: Jerry James) 18 years, 8 months

robert delius royar

Mon, 10 Apr 2006 (16:35 -0600 UTC) Jerry James wrote: > robert delius royar <xemacs(a)frinabulax.org> wrote: >> OK, I simply removed the 'if (__GMP_ULONG_MAX <= GMP_NUMB_MASK)' from line >> 1595 of gmp.h. That stopped the warnings. Now, my loadup/dump fails with the >> same type error >> Requiring disp-table.el...*** Error in XEmacs initialization >> (wrong-type-argument integer-or-char-p 225) > > I wonder if you are triggering a similar bug to the icc bug that bit me. > Let's see. I am attaching the test case I sent Intel a couple of years > ago. You'll have to edit the Makefile a bit, but try it out and see if > the test program reports that you are getting bignum results. You > shouldn't be. I cannot try the icc compile because I have a PowerPC, but I did the gcc compilation. If I understand the main() function, I should have seen "a bignum" at some point. Here is a copy of the warnings and the output from the program itself: gcc -Wall -Wextra -I/opt/local/include -Os -mcpu=970 -mtune=970 -mpim-altivec -mpowerpc-gpopt -g3 test.c -L/opt/local/lib -lgmp -lm -o test-gcc test.c: In function 'bignum_hash': test.c:780: warning: control may reach end of non-void function '__gmpz_get_ui' being inlined test.c: At top level: test.c:1000: warning: 'gc_count_num_float_in_use' defined but not used test.c:1000: warning: 'gc_count_num_float_freelist' defined but not used test.c:1019: warning: 'init_bignum_alloc' defined but not used test.c:1019: warning: 'gc_count_num_bignum_in_use' defined but not used test.c:1019: warning: 'gc_count_num_bignum_freelist' defined but not used grendel% ./test-gcc If I add 1 to 0, I get 1. If I add 1 to 1, I get 2. If I add 1 to 2, I get 3. If I add 1 to 3, I get 4. If I add 1 to 4, I get 5. If I add 1 to 5, I get 6. If I add 1 to 6, I get 7. If I add 1 to 7, I get 8. If I add 1 to 8, I get 9. If I add 1 to 9, I get 10. If I add 1 to 10, I get 11. If I add 1 to 11, I get 12. If I add 1 to 12, I get 13. If I add 1 to 13, I get 14. If I add 1 to 14, I get 15. If I add 1 to 15, I get 16. If I add 1 to 16, I get 17. If I add 1 to 17, I get 18. If I add 1 to 18, I get 19. If I add 1 to 19, I get 20. -- Dr. Robert Delius Royar Associate Professor of English Morehead State University Morehead, Kentucky

1 participants
0 comments

XEmacs 2.5.26/RHEL4: ALSA compilation problems 18 years, 8 months

Stefan Becker

Hi, the latest configure automatic detects ALSA headers on the system. But it seems the code requires a specific version of ALSA: gcc -c -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wunused-parameter -g -O3 -Demacs -I. -I/workarea/rpm/SOURCES/xemacs-21.5.26/src -DHAVE_CONFIG_H -I/usr/X11R6/include /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c: In function `set_volume': /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:231: error: void value not ignored as it ought to be /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:254: error: `SND_MIXER_SCHN_REAR_CENTER' undeclared (first use in this function) /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:254: error: (Each undeclared identifier is reported only once /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:254: error: for each function it appears in.) /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:262: error: `SND_MIXER_SCHN_SIDE_LEFT' undeclared (first use in this function) /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:266: error: `SND_MIXER_SCHN_SIDE_RIGHT' undeclared (first use in this function) /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c: In function `reset_volume': /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:298: error: `SND_MIXER_SCHN_REAR_CENTER' undeclared (first use in this function) /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:306: error: `SND_MIXER_SCHN_SIDE_LEFT' undeclared (first use in this function) /workarea/rpm/SOURCES/xemacs-21.5.26/src/alsaplay.c:310: error: `SND_MIXER_SCHN_SIDE_RIGHT' undeclared (first use in this function) make[1]: *** [alsaplay.o] Error 1 I'm trying to compile it on RHEL4u3 which has ALSA 1.0.6: $ rpm -q alsa-lib-devel alsa-lib-devel-1.0.6-5.RHEL4 $ fgrep SND_MIXER_SCH /usr/include/alsa/* /usr/include/alsa/mixer.h: SND_MIXER_SCHN_UNKNOWN = -1, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_FRONT_LEFT = 0, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_FRONT_RIGHT, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_FRONT_CENTER, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_REAR_LEFT, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_REAR_RIGHT, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_WOOFER, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_LAST = 31, /usr/include/alsa/mixer.h: SND_MIXER_SCHN_MONO = SND_MIXER_SCHN_FRONT_LEFT I guess the ALSA autoconfig check needs to check for a minimum version. Regards, Stefan --- Stefan Becker E-Mail: Stefan.Becker(a)nokia.com

2 participants
1 comments

Re: [R21.4] [AC] Re: [PATCH] Increasing the number of regex failure points. 18 years, 8 months

Adrian Aichner

Malcolm Purvis <malcolmp(a)xemacs.org> writes: > RECOMMEND 21.4 APPROVE COMMIT > >>>>>> "Malcolm" == Malcolm Purvis <malcolmp(a)xemacs.org> writes: > > Malcolm> This patch changes the maximum number of regex failure points to the > Malcolm> values currently found in GNU Emacs. Hi Malcolm! With this patch I still see the problem. I can reproduce the problem with put into M-x compilation-minor-mode by executing C-x ` (next-error) I use (setq compilation-error-regexp-systems-list 'all) and get following Best regards, Adrian NB: MFT of original is broken. I repaired it manually. > > This patch has been committed. > > I forgot to mention in the original post that this patch may also be of use > for 21.4 > > Malcolm -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
1 comments

Bignum support still broken on powerpc (ping: Jerry James) 18 years, 8 months

robert delius royar

Now that Jerry James is back, I wanted to report again that big number support appears to break something about the byte compiler when linking (on powerpc Mac) during the first pass at creating an XEmacs executable. The breakage first began some months ago, and I reported it then. I tried to build today with -enable-bignum=gmp. I got the same breakage. My system is Mac OS X 10.4.6 (both a G4 and a G5). I compile with gcc4.01. The error is *** Error in XEmacs initialization (wrong-type-argument sequencep 34) *** Backtrace really-early-error-handler((wrong-type-argument sequencep 34)) define-key(#<keymap global-map size 6 0x250f> 34 self-insert-command) # bind (n) Right after the console says (I mean the lines below fall immediately before the block above) Loading /Users/royar/src/xemacs/lisp/simple.elc... Loading /Users/royar/src/xemacs/lisp/newcomment.elc... Loading /Users/royar/src/xemacs/lisp/keydefs.elc... There must be some character alignment issue because the error string switches the console xterm to what looks to be "line-drawing mode." And the console has to be reset. The error is early in linking. The linking commands run right before the excerpt above are gcc -Wall -Wno-switch -Wundef -Wsign-compare -Wno-char-subscripts -Wpacked -Wpointer-arith -Wunused-parameter -g -Os -pipe -mcpu=970 -mtune=970 -mpim-altivec -Os -pipe -mcpu=970 -mtune=970 -mpim-altivec -mpowerpc-gpopt -L/opt/local/lib -L/usr/X11R6/lib -L/usr/lib -L/usr/X11R6/lib -o temacs abbrev.o alloc.o alloca.o balloon_help.o balloon-x.o blocktype.o buffer.o bytecode.o callint.o casefiddle.o casetab.o chartab.o filelock.o cmdloop.o cmds.o console.o console-stream.o data.o database.o device.o dired.o doc.o doprnt.o dynarr.o editfns.o elhash.o emacs.o emodules.o eval.o events.o event-stream.o event-unixoid.o dumper.o inline.o esd.o miscplay.o terminfo.o extents.o faces.o file-coding.o fileio.o filemode.o floatfns.o fns.o font-lock.o frame.o gc.o general.o dgif_lib.o gif_io.o glyphs.o glyphs-eimage.o glyphs-shared.o glyphs-widget.o gui.o menubar.o scrollbar.o dialog.o toolbar.o gutter.o hash.o imgproc.o indent.o insdel.o intl.o keymap.o line-number.o lread.o lstream.o macros.o marker.o md5.o minibuf.o mule-ccl.o mule-charset.o mule-coding.o number-gmp.o number.o objects.o opaque.o print.o process.o process-unix.o profile.o rangetab.o realpath.o redisplay.o redisplay-output.o regex.o search.o select.o sysdll.o signal.o sound.o specifier.o strftime.o symbols.o syntax.o sysdep.o text.o console-tty.o device-tty.o event-tty.o frame-tty.o objects-tty.o redisplay-tty.o cm.o undo.o unicode.o console-x.o device-x.o event-Xt.o frame-x.o glyphs-x.o objects-x.o redisplay-x.o select-x.o xgccache.o intl-x.o gui-x.o menubar-x.o scrollbar-x.o dialog-x.o toolbar-x.o toolbar-common.o widget.o window.o lastfile.o EmacsFrame.o EmacsShell.o TopLevelEmacsShell.o TransientEmacsShell.o EmacsManager.o ExternalShell.o extw-Xt-nonshared.o extw-Xlib-nonshared.o dump-id.o dump-data.o ../lwlib/liblw.a -lXaw3d -ltiff -lpng -ljpeg -lz -lXpm -lXmu -lXt -lXext -lX11 -lSM -lICE -lgmp -ldb -lgdbm -lncurses -L/opt/local/lib -lesd -laudiofile -lm -lintl ./temacs -nd -no-packages -batch -l /Users/royar/src/xemacs/src/../lisp/update-elc.el Loading /Users/royar/src/xemacs/src/../lisp/update-elc.el... Loading find-paths.el... Loading packages.el... Loading setup-paths.el... Loading /Users/royar/src/xemacs/lisp/dumped-lisp.el... Wrote /Users/royar/src/xemacs/src/REBUILD_AUTOLOADS if true ; then \ ./temacs -nd -no-packages -batch -l /Users/royar/src/xemacs/src/../lisp/make-docfile.el -- \ -o ../lib-src/DOC -d /Users/royar/src/xemacs/src -i ../lib-src/../site-packages \ abbrev.c alloc.c alloca.c balloon_help.c balloon-x.c blocktype.c buffer.c bytecode.c callint.c casefiddle.c casetab.c chartab.c filelock.c cmdloop.c cmds.c console.c console-stream.c data.c database.c device.c dired.c doc.c doprnt.c dynarr.c editfns.c elhash.c emacs.c emodules.c eval.c events.c event-stream.c event-unixoid.c dumper.c inline.c esd.c miscplay.c terminfo.c extents.c faces.c file-coding.c fileio.c filemode.c floatfns.c fns.c font-lock.c frame.c gc.c general.c dgif_lib.c gif_io.c glyphs.c glyphs-eimage.c glyphs-shared.c glyphs-widget.c gui.c menubar.c scrollbar.c dialog.c toolbar.c gutter.c hash.c imgproc.c indent.c insdel.c intl.c keymap.c line-number.c lread.c lstream.c macros.c marker.c md5.c minibuf.c mule-ccl.c mule-charset.c mule-coding.c number-gmp.c number.c objects.c opaque.c print.c process.c process-unix.c profile.c rangetab.c realpath.c redisplay.c redisplay-output.c regex.c search.c select.c sysdll.c signal.c sound.c specifier.c strftime.c symbols.c syntax.c sysdep.c text.c console-tty.c device-tty.c event-tty.c frame-tty.c objects-tty.c redisplay-tty.c cm.c undo.c unicode.c console-x.c device-x.c event-Xt.c frame-x.c glyphs-x.c objects-x.c redisplay-x.c select-x.c xgccache.c intl-x.c gui-x.c menubar-x.c scrollbar-x.c dialog-x.c toolbar-x.c toolbar-common.c widget.c window.c \ ; fi Loading /Users/royar/src/xemacs/src/../lisp/make-docfile.el... Loading find-paths.el... Loading packages.el... Loading setup-paths.el... Loading raw-process.el... Requiring custom... Requiring widget... Loading process... Loading /Users/royar/src/xemacs/lisp/dumped-lisp.el... Spawning make-docfile ... Spawning make-docfile ...done ./temacs -nd -no-packages -batch -l /Users/royar/src/xemacs/src/../lisp/loadup.el dump Loading /Users/royar/src/xemacs/src/../lisp/loadup.el... Using load-path (/Users/royar/src/xemacs/lisp/) Using module-load-path (/Users/royar/src/xemacs/modules) In compiling I see a few of these gmp-related warnings: data.c: In function 'Flsh': data.c:2412: warning: control may reach end of non-void function '__gmpz_get_ui' being inlined floatfns.c: In function 'Fexpt': floatfns.c:505: warning: control may reach end of non-void function '__gmpz_get_ui' being inlined number.c: In function 'bignum_hash': number.c:70: warning: control may reach end of non-void function '__gmpz_get_ui' being inlined I have tried with no optimization, no union type, and many simple configurations. The outcome is always the same. -- Dr. Robert Delius Royar Associate Professor of English Morehead State University Morehead, Kentucky

5 participants
11 comments

RE: README.wav/README.au crash xemacs 18 years, 8 months

Rodney Sparapani

21.4.19 -----Original Message----- From: Aidan Kehoe [mailto:kehoea＠parhasard.net] Sent: Sun 4/9/2006 3:40 AM To: Rodney Sparapani Cc: xemacs-beta(a)xemacs.org Subject: Re: README.wav/README.au crash xemacs Ar an t-aonú lá is triochad de mí Eanair, scríobh Rodney Sparapani>: > There are two files in xemacs-packages/etc/sounds that will crash xemacs. > They are really text files, but they are named like sound files which tempts > the user into playing them and crashing their xemacs. Maybe they should be > renamed to README.wav.txt and README.au.txt? Maybe--but I can't reproduce that crash. Whate version of XEmacs did you use? > Lisp backtrace follows: > > play-sound-file("/usr/local/lib/xemacs/xemacs-packages/etc/sounds/README.au") > eval((play-sound-file > "/usr/local/lib/xemacs/xemacs-packages/etc/sounds/README.au")) # bind (expr) > eval-interactive((play-sound-file > "/usr/local/lib/xemacs/xemacs-packages/etc/sounds/README.au")) > # bind (standard-output opoint ignore-quotes eval-last-sexp-arg-internal) > eval-last-sexp(t) > # bind (standard-output) > #<compiled-function nil "...(13)" [standard-output terpri eval-last-sexp t] 2 > 1019499 nil>() > call-interactively(eval-print-last-sexp) > # (condition-case ... . error) > # (catch top-level ...) > > [2] + segmentation fault xemacs -geometry 100x40 -f viper-mode > -- In the beginning God created the heavens and the earth. And God was a bug-eyed, hexagonal smurf with a head of electrified hair; and God said: "Si, mi chiamano Mimi..."

1 participants
0 comments

Status of new unsupported vc package (was: Re: [PATCH] packages: Avoid losing locally-added CVS files on vc-next-action-on-file) 18 years, 8 months

Ville Skyttä

On Sun, 2006-04-09 at 16:07 +0200, Adrian Aichner wrote: > Hi Ville, > > what is the status of > packages/unsupported/scop/vc/ > ? > > Do you plan to release that soon? No plans until the unsupported-vc-crashes-21.4 issue for which I've asked for help every now and then for a looooong time, last time in http://list-archive.xemacs.org/xemacs-beta/200602/msg00214.html , is resolved. The last request received an ack from Stephen and I've nagged him a couple of times in PM (per his permission), but I guess he hasn't found time for it yet. In the meantime, I managed to lose the test case I had in the above mail, they're online again now at http://koti.welho.com/vskytta/xemacs/new-vc/ I've also reverted to compiling with gcc 3.2.x due to a bunch of issues with gcc 4.1, and can currently not reproduce the *crash*, but the random error messages are still there, and everything is still fixed by removing vc/auto-autoloads.elc (only the bytecompiled one).

1 participants
0 comments

Re: [AC] Fixing next-error in 21.5. 18 years, 8 months

Adrian Aichner

Malcolm Purvis <malcolmp(a)xemacs.org> writes: > APPROVE COMMIT > >>>>>> "Malcolm" == Malcolm Purvis <malcolmp(a)xemacs.org> writes: > > Malcolm> This patch renames the clashing functions > > This patch has been committed. This fixes the problem for me. Thanks Malcolm! Adrian > > Malcolm -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

1 participants
0 comments

README.wav/README.au crash xemacs 18 years, 9 months

Rodney Sparapani

There are two files in xemacs-packages/etc/sounds that will crash xemacs. They are really text files, but they are named like sound files which tempts the user into playing them and crashing their xemacs. Maybe they should be renamed to README.wav.txt and README.au.txt? Lisp backtrace follows: play-sound-file("/usr/local/lib/xemacs/xemacs-packages/etc/sounds/README.au") eval((play-sound-file "/usr/local/lib/xemacs/xemacs-packages/etc/sounds/README.au")) # bind (expr) eval-interactive((play-sound-file "/usr/local/lib/xemacs/xemacs-packages/etc/sounds/README.au")) # bind (standard-output opoint ignore-quotes eval-last-sexp-arg-internal) eval-last-sexp(t) # bind (standard-output) #<compiled-function nil "...(13)" [standard-output terpri eval-last-sexp t] 2 1019499 nil>() call-interactively(eval-print-last-sexp) # (condition-case ... . error) # (catch top-level ...) [2] + segmentation fault xemacs -geometry 100x40 -f viper-mode

2 participants
1 comments

another UTF8 Problem in 21.4.17 18 years, 9 months

Uwe Brauer

Hello the following symbol ✉ is correctly decoded in GNU emasc 21.4 (but not displayed!, it is a mail envelope) in Xemacs 21.4.17 it is decoded, incorrectly, as ? is the situation better in 21.5 Uwe Brauer

6 participants
12 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 2006