January 2001 - XEmacs-Beta - XEmacs Mailing List Archives

Bad Link to mail archives 23 years, 10 months

Vin Shelton

When I go to: http://www.xemacs.org/Lists/Archive/index.cgi and click on the xemacs-patches the links, I get: The requested URL /xemacs-patches was not found on this server. So far, each of the links behaves similarly. - vin

1 participants
0 comments

Re: 21.1.14 This Weekend 23 years, 10 months

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Vin> I intend to release 21.1.14 this weekend. I hope to release Vin> 21.1.14 as it now exists in CVS, so get your bug reports in Vin> ASAP. Hello Vin, can you please review this for 21.1.14. Yoshiki, can you please comment? From: Adrian.Aichner(a)t-online.de (Adrian Aichner) Subject: Re: XEmacs 21.1.9 "Canyonlands" has been Released To: xemacs-beta(a)xemacs.org Cc: Yoshiki Hayashi <yoshiki(a)xemacs.org> Date: 21 Jan 2001 23:55:57 +0100 References: <m2900oaaoh.fsf(a)zion.ne.mediaone.net> Organization: The XEmacs Project Message-ID: <uk87owm4i.fsf(a)rapier.ecf.teradyne.com> Best regards, Adrian Vin> - vin -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
1 comments

[ANN] ViaVoice module, version 0.5.0 23 years, 10 months

Jerry James

I am dictating this announcement using the ViaVoice for XEmacs module (with some hand corrections, obviously). It is far from perfect, not least because I have a cold right now. However, it works well enough for me to be having fun doing this! Come on over to the web page for the project, and have a look. I guess I will have to type the URL by hand: <URL:http://www.ittc.ku.edu/~james/computer/viavoice.html>. Right now it only works for Linux (ViaVoice doesn't know that word either). A port to Microsoft Windows should be quite easy, but I don't have access to the ViaVoice SDK for Windows. The implementation isn't complete, has some dumb hacks that need to be removed, etc. I am interested in any feedback you might have for me. Since this is my first time writing C for XEmacs, I would appreciate any comments on style. Thanks, -- Jerry James

4 participants
3 comments

Re: [ANN] ViaVoice module, version 0.5.0 23 years, 10 months

Jerry James

wmperry(a)aventail.com (William M. Perry) wrote: > That is awesome! I've been meaning to write this for a while, but haven't > had the time. :( I'll grab this and comment on the code when I have some > free time tonight. Did you actually hook into the event stream like the > new version of the GPM support does? That's one of my gripes, actually. It doesn't look like there is any way of unhooking the event stream, right? If there were, I could provide an "unload this module" function which would completely clean up, unbind variables and functions, etc. But I can't unhook the event stream (unless I'm missing something). > Just checked the code - you do. Cool. It would be an interesting test of > this to run in linux console and try to turn on GPM and ViaVoice at the > same time. :) Just to verify our technique works in the arbitrary case. I > don't see why it wouldn't but.... Right. They shouldn't clash, but we certainly ought to check. It'll get more interesting when I put in support for command and control. Then I'll be faking menu events. Can I make those fake keyboard events instead of fake mouse events? I've got to read the menu code this weekend... > This puts us a step closer to getting M-x doctor and M-x yow talking > between two computers. M-x psychoanalyze-pinhead that you can listen to! > I forget who originally hatched that idea when I mentioned doing this work > originally, but if you pull it off, I want a recording. :) Too bad I haven't got two computers with microphones in the same room, anywhere. I'll have to see what I can do about that. > With a decent headset and boom mic, viavoice & emacspeak - this would be > great for annoying people on airplanes. 'That big scary man is talking to > his computer, and it doesn't even look like it is turned on'.... hehehehhe. Oh now, that's just evil. :-) -- Jerry James

1 participants
0 comments

Re: XEmacs' pathname canonicalization versus Red Hat Linux 7's realpath() 23 years, 10 months

Ulrich Drepper

Martin Buchholz <martin(a)xemacs.org> writes: > I think 20 is too low. I worked in an environment years ago we had a > real problem with the limit of 20, that required reengineering the way > the project was organized. There can be good reasons for using > symlinks, for example imagine many trees of sparsely populated > symlinks pointing at other such trees. > > I recommend at least bumping the limit to 32, which is XEmacs' > hardcoded limit. Nope. If 20 isn't enough you are in big trouble. As I've said, 20 is not an arbitrary choice, it is what others do. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------

3 participants
2 comments

Re: XEmacs 21.1.9 "Canyonlands" has been Released 23 years, 10 months

Adrian Aichner

>>>>> "Vin" == Vin Shelton <acs(a)xemacs.org> writes: Hi Vin, I think From: Adrian Aichner <aichner(a)ecf.teradyne.com> Subject: Re: [21.1.8, 21.2-b20] *Hyper Help* to find symbol to customize ... X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00046.html got reverted. The bug seems to be back in 21.1.13. This is the likely suspect: 2000-01-05 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * hyper-apropos.el (hyper-apropos-this-symbol): Don't always get symbol at point-min. Yoshiki, please comment. Best regards, Adrian Vin> XEmacs-21.1.9 "Canyonlands" is available from ftp.xemacs.org. Get it from: Vin> ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.1/xemacs-21.1.9.tar.gz Vin> ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.1/xemacs-21.1.9-elc.tar.gz Vin> ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.1/xemacs-21.1.9-info.tar.gz Vin> A patch to upgrade from 21.1.8 is also available: Vin> ftp://ftp.xemacs.org/pub/xemacs/xemacs-21.1/xemacs-21.1.8-21.1.9.patch.gz Vin> [The patch tarball only includes patches from Vin> xemacs-21.1.8.tar.gz to xemacs-21.1.9.tar.gz; you will still Vin> need to retrieve the elc and info tarballs. After applying Vin> the patch, please run the command 'touch configure' in order Vin> to make sure 'configure' is newer than 'configure.in'.] Vin> XEmacs-21.1 is the stable branch of XEmacs. As such, only bugfix Vin> submissions are allowed into these releases. This release fixes a Vin> fairly large number of bugs; here are the relevant URLS: Vin> From: Jason R Mastaler <jason(a)mastaler.com> Vin> Subject: Re: [21.1.8, 21.2.19] etc/FTP: mirror site updates Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00023.html Vin> From: Jason R Mastaler <jason(a)mastaler.com> Vin> Subject: Re: [21.1.8, 21.2.19] etc/MAILINGLISTS: subscription info updates Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00024.html Vin> From: Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> Vin> Subject: Re: The last patch (hopefully) for (insert 8000) problem Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00040.html Vin> From: Jason R Mastaler <jason(a)mastaler.com> Vin> Subject: Re: [21.2.19] lisp/package-get.el: package-get-download-sites fixes Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00036.html Vin> From: Andy Piper <andyp(a)beasys.com> Vin> Subject: Re: "Forked child base mismatch" using MKS Toolkit shell Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-nt/9910/msg00107.html Vin> From: rpluim(a)bigfoot.com Vin> Subject: Give people with crashes more of a clue Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00011.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: Re: [21.1.8, 21.2-b20] *Hyper Help* to find symbol to customize ... Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00046.html Vin> From: Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> Vin> Subject: [21.1] list-character-set Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00049.html Vin> From: Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> Vin> Subject: [21.1] describe-coding-system Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00072.html Vin> From: Eric Darve <darve(a)ctr-sgi1.stanford.edu> Vin> Subject: abbrev.c : patch suggestion Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00072.html Vin> From: John Buchholz <martin(a)xemacs.org> Vin> Subject: Re: Autocorrect trivial spelling errors in flyspell-mode Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00084.html Vin> From: Mike Alexander <mta(a)arbortext.com> Vin> Subject: directory-sep-char in Windows native version Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9911/msg00086.html Vin> From: Jan Vroonhof <vroonhof(a)math.ethz.ch> Vin> Subject: Guard nr args in call-process-internal. Fix (PR#1003) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9912/msg00005.html Vin> From: Alexandre Oliva <oliva(a)lsd.ic.unicamp.br> Vin> Subject: unexelf.c is broken on IRIX 6 Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9912/msg00006.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: Re: Broken makeinfo? [was: Re: Fix this] Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9912/msg00030.html Vin> From: Kyle Jones <kyle_jones(a)wonderworks.com> Vin> Subject: [PATCH] fix for busted idle itimers Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9912/msg00033.html Vin> From: Kazuyuki IENAGA <ienaga(a)jsys.co.jp> Vin> Subject: input-method-xlib.c/emacs.c/symsinit.h (for 21.1.8) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9912/msg00034.html Vin> From: Vin Shelton <acs(a)xemacs.org> Vin> Subject: Re: [21.1] popup menus still offset (PR#1123) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00032.html Vin> From: Andreas Jaeger <aj(a)suse.de> Vin> Subject: Re: pstogif tidy up Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199911/msg00111.html Vin> From: Jan Vroonhof <vroonhof(a)math.ethz.ch> Vin> Subject: Fix detection of two char comments. Solves (PR#1039) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00036.html Vin> From: Gunnar Evermann <ge204(a)eng.cam.ac.uk> Vin> Subject: Re: Bug in documentation Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00042.html Vin> From: Jan Vroonhof <vroonhof(a)math.ethz.ch> Vin> Subject: [patch] Re: Cannot "list and install" with Xemacs 21.1 on RedHat 6.1 (linux) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00043.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: [21.1.8 Patch] Fix auto-autoloads.el rule in xemacs.mak Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00058.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: [21.1.8 Patch] Encapsulate fstat on native NT, use warn_when_safe Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00059.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: [21.1.8 Patch] directory-sep-char in Windows native version Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00060.html Vin> From: Gunnar Evermann <ge204(a)eng.cam.ac.uk> Vin> Subject: Re: check process state before accessing coding_stream (fix PR#1061) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00176.html Vin> From: Gunnar Evermann <ge204(a)eng.cam.ac.uk> Vin> Subject: typo Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00067.html Vin> From: Jeff Miller <jmiller(a)smart.net> Vin> Subject: package-get patch for 21.1.x Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00069.html Vin> From: Charles G Waldman <cgw(a)fnal.gov> Vin> Subject: fix for gnuserv.el bug Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00078.html Vin> From: Katsumi Yamaoka <yamaoka(a)jpl.org> Vin> Subject: src/buffer.c (Re: xemacs-packages/mule/egg-its/egg.el) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00087.html Vin> From: Scott Blachowicz <Scott.Blachowicz(a)seaslug.org> Vin> Subject: 21.2.24: nt/minitar.c - add explicit exit(0) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00094.html Vin> From: Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> Vin> Subject: Boring README cleanup Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00100.html Vin> From: Yoshiki Hayashi <t90553(a)m.ecc.u-tokyo.ac.jp> Vin> Subject: Re: hyper-apropos-mouse-get-doc Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00015.html Vin> From: Stef Epardaud <stef(a)lunatech.com> Vin> Subject: more javadoc fixes Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/199912/msg00109.html Vin> From: Didier Verna <didier(a)xemacs.org> Vin> Subject: [PATCH] misc typo fixes in the info files Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00013.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: README.packages update Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00028.html Vin> From: Andy Piper <andy(a)xemacs.org> Vin> Subject: Patch for non-starting problem (was RE: help) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00055.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: [approval request] lisp\about.el Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00083.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: [approval request] lisp\autoload.el Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00082.html Vin> From: Adrian Aichner <aichner(a)ecf.teradyne.com> Vin> Subject: [approval request] lisp\minibuf.el Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00087.html Vin> From: Hrvoje Niksic <hniksic(a)iskon.hr> Vin> Subject: Customize Info-directory-list ... NOT! Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00091.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: typo fix Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00093.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: Fbacktrace() Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00108.html Vin> From: Mark Thomas <mthomas(a)jprc.com> Vin> Subject: XEmacs 21.1.8/21.2.b27 Info patch: trim-versions-without-asking Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00147.html Vin> From: Kyle Jones <kyle_jones(a)wonderworks.com> Vin> Subject: itimer.el bug fix Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00164.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: Re: simultaneously build with and without --srcdir Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00167.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: lread.c (read_bit_vector): Fix memory leak reading literal bit vectors. Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00200.html Vin> From: Hrvoje Niksic <hniksic(a)iskon.hr> Vin> Subject: Fix for home dir annoyances under NT Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00205.html Vin> From: Andreas Jaeger <aj(a)suse.de> Vin> Subject: Re: font-menu-ignore-scaled-fonts in 21.1. and 21.2 Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-beta/200001/msg00673.html Vin> From: Andy Piper <andy(a)xemacs.org> Vin> Subject: 21.1 - shell execute Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00025.html Vin> From: Yoshiki Hayashi <yoshiki(a)xemacs.org> Vin> Subject: about.el Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00124.html Vin> From: Kazuyuki IENAGA <ienaga(a)jsys.co.jp> Vin> Subject: Re: input-method-xlib.c/emacs.c/symsinit.h (revised for HEAD) Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/9910/msg00045.html Vin> From: Kazuyuki IENAGA <kazz(a)imasy.or.jp> Vin> Subject: Re: [patch] Ienaga's address change Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00035.html Vin> From: Andreas Jaeger <aj(a)suse.de> Vin> Subject: Patch for about.el Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200001/msg00027.html Vin> From: Marcus Thiessel <marcus(a)xemacs.org> Vin> Subject: patch to PROBLEMS/ windowed ancestor bug on HP-UX 11.0 Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00042.html Vin> From: Martin Buchholz <martin(a)xemacs.org> Vin> Subject: Detecting Berkeley DB Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00048.html Vin> From: Stef Epardaud <stef(a)lunatech.com> Vin> Subject: Re: more javadoc fixes Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00050.html Vin> From: Andy Piper <andy(a)xemacs.org> Vin> Subject: [21.1.9] emergency mswindows-shell-execute fix Vin> X-archive-URL: http://www.xemacs.org/list-archives/xemacs-patches/200002/msg00053.html Vin> The 21.1.x series of releases is being named for US National Parks. Vin> Canyonlands is located in southern Utah near a bunch of other parks. Vin> Why not take a trip out there to see them? For more information see: Vin> http://www.nps.gov/cany. Vin> Vin Shelton -- Adrian Aichner mailto:adrian＠xemacs.org http://www.xemacs.org/

2 participants
1 comments

Re: XEmacs' pathname canonicalization versus Red Hat Linux 7's realpath() 23 years, 10 months

Ulrich Drepper

Alexandre Oliva <aoliva(a)redhat.com> writes: > Uli, is this a known problem? (Red Hat Linux 7's glibc 2.2-12) Any > chance of bumping up the maximum number of soft-links realpath() > follows (or whatever condition it uses to decide that it's got an > ELOOP), so that I don't have to rework my *apparently* insane > soft-link maze? :-) I guess this can be done. I've looked around a bit and found that other systems have a limit of 20. So I bumped it. But this does not excuse you from cleaning up your mess. -- ---------------. ,-. 1325 Chesapeake Terrace Ulrich Drepper \ ,-------------------' \ Sunnyvale, CA 94089 USA Red Hat `--' drepper at redhat.com `------------------------

3 participants
2 comments

[CORE] current CVS, enter a group in gnus 23 years, 10 months

Norbert Koch

Hi! I was in Gnus, stepped out of a group and re-entered it, and have been rewarded with the following core. No Lisp-Backtrace ... #0 0x185563d0 in kill () from /usr/lib/libc.so.3 #1 0x80c58b3 in fatal_error_signal (sig=6) at emacs.c:535 #2 0xbfbfdfdc in ?? () #3 0x80c89fa in assert_failed (file=0x829f47f "alloc.c", line=2245, expr=0x829fd60 "! MARKED_RECORD_HEADER_P (lheader)") at emacs.c:3214 #4 0x808e173 in allocate_managed_lcrecord (lcrecord_list={gu = { type = Lisp_Type_Record, val = 35405760}, s = {bits = 0, val = 70811520}, u = {bits = 0, val = 70811520}, ui = 141623040, i = 141623040, v = 0x870ff00, cv = 0x870ff00}) at alloc.c:2245 #5 0x81a5a5f in Lstream_new (imp=0x83243c0, mode=0x82ee36a "r") at lstream.c:245 #6 0x81a76b5 in make_fixed_buffer_input_stream (buf=0xbfbfa2a8, size=63) at lstream.c:1267 #7 0x8098256 in dfc_convert_to_external_format (source_type=DFC_TYPE_DATA, source=0xbfbfa2a0, coding_system={gu = {type = Lisp_Type_Record, val = 35003808}, s = {bits = 0, val = 70007616}, u = {bits = 0, val = 70007616}, ui = 140015232, i = 140015232, v = 0x8587680, cv = 0x8587680}, sink_type=DFC_TYPE_DATA, sink=0xbfbfa298) at buffer.c:1890 #8 0x81b0754 in std_handle_out_va (stream=0x832e118, fmt=0x82b3b00 "Fatal error: assertion failed, file %s, line %d, %s\n", args=0xbfbfc2d4 "'O+\b]\a") at print.c:186 #9 0x81b0852 in stderr_out ( fmt=0x82b3b00 "Fatal error: assertion failed, file %s, line %d, %s\n") at print.c:208 #10 0x80c89f2 in assert_failed (file=0x82b4f27 "eval.c", line=1885, expr=0x82b4a88 "abort()") at emacs.c:3208 #11 0x80cb485 in signal_1 (sig={gu = {type = Lisp_Type_Record, val = 34449089}, s = {bits = 0, val = 68898178}, u = {bits = 0, val = 68898178}, ui = 137796356, i = 137796356, v = 0x8369b04, cv = 0x8369b04}, data={gu = {type = Lisp_Type_Record, val = 38119923}, s = {bits = 0, val = 76239846}, u = {bits = 0, val = 76239846}, ui = 152479692, i = 152479692, v = 0x916a7cc, cv = 0x916a7cc}) at eval.c:1885 #12 0x80d509e in Fsignal (error_symbol={gu = {type = Lisp_Type_Record, val = 34449089}, s = {bits = 0, val = 68898178}, u = {bits = 0, val = 68898178}, ui = 137796356, i = 137796356, v = 0x8369b04, cv = 0x8369b04}, data={gu = {type = Lisp_Type_Record, val = 38119923}, s = {bits = 0, val = 76239846}, u = {bits = 0, val = 76239846}, ui = 152479692, i = 152479692, v = 0x916a7cc, cv = 0x916a7cc}) at eval.c:2052 #13 0x8195d48 in barf_if_buffer_read_only (buf=0x8daca00, from=1, to=1) at insdel.c:3061 #14 0x8191e05 in prepare_to_modify_buffer (buf=0x8daca00, start=1, end=1, lockit=1) at insdel.c:2317 #15 0x8192197 in buffer_insert_string_1 (buf=0x8daca00, pos=1, nonreloc=0x9139400 "e: /usr/users/support/nk/mail/bsd-cvs/10041\n17841: 3517: Jan 26 04:08:26 2001: 6: File: /usr/users/support/nk/mail/bsd-cvs/10122\n17841: 3518: Jan 26 04:08:26 2001: 6: File: /usr/users/support/nk/mail/"..., reloc={ gu = {type = Lisp_Type_Record, val = 34448897}, s = {bits = 0, val = 68897794}, u = {bits = 0, val = 68897794}, ui = 137795588, i = 137795588, v = 0x8369804, cv = 0x8369804}, offset=0, length=512, flags=0) at insdel.c:2455 #16 0x8195a2d in buffer_insert_raw_string_1 (buf=0x8daca00, pos=1, nonreloc=0x9139400 "e: /usr/users/support/nk/mail/bsd-cvs/10041\n17841: 3517: Jan 26 04:08:26 2001: 6: File: /usr/users/support/nk/mail/bsd-cvs/10122\n17841: 3518: Jan 26 04:08:26 2001: 6: File: /usr/users/support/nk/mail/"..., length=512, flags=0) at insdel.c:2585 norbert. -- After THIS, let's go to PHILADELPHIA and have TRIPLETS!!

2 participants
4 comments

Re: Alpha/Linux configure fix -- avoid /usr/shlib 23 years, 10 months

Martin Buchholz

>>>>> "AO" == Alexandre Oliva <aoliva(a)redhat.com> writes: AO> The only problem I encountered with 21.1.13 was on Solaris 7/x86. AO> Dumping xemacs crashes using unexsol2-6.c (the default), but it works AO> with unexelf.c. You may want to change that for the next release. AO> The compiler I use is GCC 2.95.2. Unfortunately, I don't have access AO> to `cc' on this platform, so I can't tell whether it would have AO> worked. I have access to i386-pc-solaris2.8 and sparc-sun-solaris2.7, and there are no dumping problems on these platforms (with gcc or cc). I don't think anyone has reported problems on i386-pc-solaris2.7, so I am inclined not to change something that has worked for many years. As usual, if I can get access to your machine, I'll take a look at how your xemacs build is different from mine, and debug the problem. AO> Hope this helps. Thanks for letting us know. AO> Sorry about the long delay in answering. All good free software hackers eventually become guilty of this.

2 participants
5 comments

Re: Final version of dumper fixes patch 23 years, 10 months

Stephen J. Turnbull

Why is this discussion happening on -review? [To those viewers who have just joined us, Martin and Olivier are seriously messing around with the pdumper. Olivier assures me that even if the code Martin is writing has "accidental" bugs, it is much more maintainable, so The Release Manager has approved it for the upcoming release as "contributing to stability in expectation". However, the thread has degenerated into a design discussion....] >>>>> "mb" == Martin Buchholz <martin(a)xemacs.org> writes: OG> Please, let's stay realist here :-) mb> OK, I'll confess. I'm secretly pining for an xemacs that has mb> 63-bit lisp ints on a 32-bit system. Let's not go there. Why stop at 63? Anyway with that many bits, I'm going to demand ISO 100646 characters, which require 63 bits. You only get 62 ;-) Please, implement bignums instead. mb> I actually don't like the assumption mb> sizeof (EMACS_INT) == sizeof (void *) I like it a lot. The kinds of things that real people do with XEmacs work fine with the current structure; 32 bits is enough for almost any daily-life task. The few things that real people do that require more (computing the number of salt molecules in a mole of yoghurt, for example) generally don't require efficient calculation. The main example I can think of is Hrvoje's sysadmin with humongous logs. However, neither humans nor the programs they write to deal with them normally need random access; with sensible buffering strategies it will normally be possible to deal with these things using normal XEmacs techniques. mb> Removing that assumption will take some work, though... Work which will never appear in an XEmacs I release.... Nyaah, nyaah, nyaah. :-P -- 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."

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 January 2001