October 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Andy Piper

This is more Motif friendly so may fix some problems we've been seeing. I'll apply andy -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Re: Patches Applied for 21.1.8 [includes essential pathc] 26 years

Jan Vroonhof

Vin Shelton <acs(a)xemacs.org> writes: > I have applied the first set of patches to CVS in preparation for > 21.1.8. Here is a list of them: If you are not already doing so, could you please make sure all patches are also in 21.2 where appropriate. Normally this should already be the case. This is just an assurance that nothing gets lost. [Yes I know half of the missing ones are mine] > I hope to release 21.1.8 either Sunday night or early next week, so > get those patches in soon if you want to see them in. It should not be released without this one (the script junk is really embarrassing, how did that get in anyway?) Could you please proof read my English? Jan 1999-10-21 Jan Vroonhof <vroonhof(a)math.ethz.ch> * xemacs-20/INSTALL: Make disk space requirements more realistic. Add note about stack size requirements. Update and add more weight to the package section. * xemacs-20/README: Add reference to README.packages * xemacs-20/INSTALL: Remove junk from install.sh Index: INSTALL =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/INSTALL,v retrieving revision 1.25 diff -u -u -r1.25 INSTALL --- INSTALL 1999/09/20 02:20:39 1.25 +++ INSTALL 1999/10/21 11:09:07 ＠＠ -1,242 +1,6 ＠＠ -#!/bin/sh -# -# install - install a program, script, or datafile -# This comes from X11R5. -# -# $XConsortium: install.sh,v 1.2 89/12/18 14:47:22 jim Exp $ -# -# This script is compatible with the BSD install script, but was written -# from scratch. -# - - -# set DOITPROG to echo to test this script - -# Don't use :- since 4.3BSD and earlier shells don't like it. -doit="${DOITPROG-}" - - -# put in absolute paths if you don't have them in your path; or use env. vars. - -mvprog="${MVPROG-mv}" -cpprog="${CPPROG-cp}" -chmodprog="${CHMODPROG-chmod}" -chownprog="${CHOWNPROG-chown}" -chgrpprog="${CHGRPPROG-chgrp}" -stripprog="${STRIPPROG-strip}" -rmprog="${RMPROG-rm}" -mkdirprog="${MKDIRPROG-mkdir}" - -tranformbasename="" -transform_arg="" -instcmd="$mvprog" -chmodcmd="$chmodprog 0755" -chowncmd="" -chgrpcmd="" -stripcmd="" -rmcmd="$rmprog -f" -mvcmd="$mvprog" -src="" -dst="" -dir_arg="" - -while [ x"$1" != x ]; do - case $1 in - -c) instcmd="$cpprog" - shift - continue;; - - -d) dir_arg=true - shift - continue;; - - -m) chmodcmd="$chmodprog $2" - shift - shift - continue;; - - -o) chowncmd="$chownprog $2" - shift - shift - continue;; - - -g) chgrpcmd="$chgrpprog $2" - shift - shift - continue;; - - -s) stripcmd="$stripprog" - shift - continue;; - - -t=*) transformarg=`echo $1 | sed 's/-t=//'` - shift - continue;; - - -b=*) transformbasename=`echo $1 | sed 's/-b=//'` - shift - continue;; - - *) if [ x"$src" = x ] - then - src=$1 - else - # this colon is to work around a 386BSD /bin/sh bug - : - dst=$1 - fi - shift - continue;; - esac -done - -if [ x"$src" = x ] -then - echo "install: no input file specified" - exit 1 -else - true -fi - -if [ x"$dir_arg" != x ]; then - dst=$src - src="" - - if [ -d $dst ]; then - instcmd=: - else - instcmd=mkdir - fi -else - -# Waiting for this to be detected by the "$instcmd $src $dsttmp" command -# might cause directories to be created, which would be especially bad -# if $src (and thus $dsttmp) contains '*'. - - if [ -f $src -o -d $src ] - then - true - else - echo "install: $src does not exist" - exit 1 - fi - - if [ x"$dst" = x ] - then - echo "install: no destination specified" - exit 1 - else - true - fi - -# If destination is a directory, append the input filename; if your system -# does not like double slashes in filenames, you may need to add some logic - - if [ -d $dst ] - then - dst="$dst"/`basename $src` - else - true - fi -fi - -## this sed command emulates the dirname command -dstdir=`echo $dst | sed -e 's,[^/]*$,,;s,/$,,;s,^$,.,'` - -# Make sure that the destination directory exists. -# this part is taken from Noah Friedman's mkinstalldirs script - -# Skip lots of stat calls in the usual case. -if [ ! -d "$dstdir" ]; then -defaultIFS=' -' -IFS="${IFS-${defaultIFS}}" - -oIFS="${IFS}" -# Some sh's can't handle IFS=/ for some reason. -IFS='%' -set - `echo ${dstdir} | sed -e 's＠/＠%＠g' -e 's＠^%＠/＠'` -IFS="${oIFS}" - -pathcomp='' - -while [ $# -ne 0 ] ; do - pathcomp="${pathcomp}${1}" - shift - - if [ ! -d "${pathcomp}" ] ; - then - $mkdirprog "${pathcomp}" - else - true - fi - - pathcomp="${pathcomp}/" -done -fi - -if [ x"$dir_arg" != x ] -then - $doit $instcmd $dst && - - if [ x"$chowncmd" != x ]; then $doit $chowncmd $dst; else true ; fi && - if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dst; else true ; fi && - if [ x"$stripcmd" != x ]; then $doit $stripcmd $dst; else true ; fi && - if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dst; else true ; fi -else - -# If we're going to rename the final executable, determine the name now. - - if [ x"$transformarg" = x ] - then - dstfile=`basename $dst` - else - dstfile=`basename $dst $transformbasename | - sed $transformarg`$transformbasename - fi - -# don't allow the sed command to completely eliminate the filename - - if [ x"$dstfile" = x ] - then - dstfile=`basename $dst` - else - true - fi - -# Make a temp file name in the proper directory. - - dsttmp=$dstdir/#inst.$$# - -# Move or copy the file name to the temp name - - $doit $instcmd $src $dsttmp && - - trap "rm -f ${dsttmp}" 0 && - -# and set any options; do chmod last to preserve setuid bits - -# If any of these fail, we abort the whole thing. If we want to -# ignore errors from any of these, just make sure not to ignore -# errors from the above "$doit $instcmd $src $dsttmp" command. - - if [ x"$chowncmd" != x ]; then $doit $chowncmd $dsttmp; else true;fi && - if [ x"$chgrpcmd" != x ]; then $doit $chgrpcmd $dsttmp; else true;fi && - if [ x"$stripcmd" != x ]; then $doit $stripcmd $dsttmp; else true;fi && - if [ x"$chmodcmd" != x ]; then $doit $chmodcmd $dsttmp; else true;fi && - -# Now rename the file to the real destination. - - $doit $rmcmd -f $dstdir/$dstfile && - $doit $mvcmd $dsttmp $dstdir/$dstfile - -fi && - - -exit 0 XEmacs Installation Guide Copyright (c) 1994, 1995, 1996 Board of Trustees, University of Illinois -Copyright (c) 1994 Free Software Foundation, Inc. +Copyright (c) 1994-1999 Free Software Foundation, Inc. Synched up with: FSF 19.30. ＠＠ -259,20 +23,22 ＠＠ 1) Make sure your system has enough swapping space allocated to handle a program whose pure code is 900k bytes and whose data area is at - least 400k and can reach 8Mb or more. If the swapping space is + least 400k and can reach 8Mb or more. Note that a typical XEmacs + build is much bigger. If the swapping space is insufficient, you will get an error in the command `temacs -batch -l loadup dump', found in `./src/Makefile.in.in', or possibly when running the final dumped XEmacs. -Building XEmacs requires about 41 Mb of disk space (including the -XEmacs sources). Once installed, XEmacs occupies about 16 Mb in the -file system where it is installed; this includes the executable files, -Lisp libraries, miscellaneous data files, and on-line documentation. -The amount of storage of the Lisp directories may be reduced by -compressing the .el files. If the building and installation take place -in different directories, then the installation procedure temporarily -requires 41+16 Mb. Adjust this value upwards depending upon what -additional Lisp support is installed. + Verify that your users have a high enough stack limit. On some + systems such as OpenBSD and OSF/Tru64 the default is 2MB which is + too low. See 'PROBLEMS' for details. + +Building XEmacs requires about 100 Mb of disk space (including the +XEmacs sources). Once installed, XEmacs occupies between 20 and 100 Mb +in the file system where it is installed; this includes the executable files, +Lisp libraries, miscellaneous data files, and on-line documentation. The +exact amount depends greatly on the number of extra lisp packages that are +installed XEmacs requires an ANSI C compiler, such as GCC. If you wish to build the documentation yourself, you will need at least version 1.68 of ＠＠ -301,21 +67,30 ＠＠ XEmacs to allow configure to find the external software packages. If you link with dynamic (``.so'') external package libraries, which is not recommended, you will also need to add the library directories -to the --site-runtime-libraries option. - +to the --site-runtime-libraries option. For your convenience these can +be set together by using the --with-site-prefix command. This will set +these variables as needed assuming your libraries are organised as a +typical /usr tree. + +3) [N.B. Most of this section can be done during or after the +compilation of the core source code, but is present early to catch +your attention.] -3) Decide what Initial Lisp you need with XEmacs. XEmacs is -distributed separately from most of its runtime environment. This is +Decide what Initial Lisp you need with XEmacs. XEmacs is +distributed separately from most of its runtime environment. This is done to make it easier for administrators to tune an installation for -what the local users need. See the file etc/PACKAGES for an overview -of what is available and which packages need to be installed prior to -building XEmacs. At this point you only need a minimum to get started -at which point you may install what you wish without further changes -to the XEmacs binary. A sample minimum configuration for a Linux -system using Mule and Wnn6 from OMRON corporation would be the -packages `mule-base' and `egg-its'. By default, packages will be -searched for in the path +what the local users need. Note that while XEmacs will compile and +install without any packages present at least some additional lisp +packages are needed to bring XEmacs up to "normal" editor +functionality. Installation and upgrading of the packages can be done +almost automatically when from inside XEmacs when it has been compiled +and installed. +More information and suggestions for which packages to install see the +file README.packages. + +By default, packages will be searched for in the path + ~/.xemacs::$prefix/lib/xemacs-${version}/mule-packages:$prefix/lib/xemacs/mule-packages:$prefix/lib/xemacs-${version}/xemacs-packages:$prefix/lib/xemacs/xemacs-packages This may be changed by specifying a different value with the ＠＠ -323,6 +98,8 ＠＠ IMPORTANT NOTE: In a future version of XEmacs, the user-specific package hierarchy will move from ~/.xemacs to ~/.xemacs/packages. + + 4) In the top level directory of the XEmacs distribution, run the program `configure' as follows: Index: README =================================================================== RCS file: /usr/CVSroot/XEmacs/xemacs-20/README,v retrieving revision 1.11 diff -u -u -r1.11 README --- README 1999/05/13 16:14:05 1.11 +++ README 1999/10/21 11:09:07 ＠＠ -16,6 +16,9 ＠＠ See the file `nt/README' for instructions on building XEmacs for Microsoft Windows. +The file 'README.packages' will guide you in the installation of +(essential) add on packages. + Reports of bugs in XEmacs should be posted to the newsgroup comp.emacs.xemacs or sent to the mailing list xemacs(a)xemacs.org. See the "Bugs" section of the XEmacs manual for more information on how to

3 participants
2 comments

Re: Patches Applied for 21.1.8 26 years

Gunnar Evermann

Vin Shelton <acs(a)xemacs.org> writes: > I have applied the first set of patches to CVS in preparation for > 21.1.8. what about: http://www.xemacs.org/list-archives/xemacs-patches/9910/msg00007.html 1999-10-06 Yoshiki Hayashi <t90553(a)mail.ecc.u-tokyo.ac.jp> * apropos.el (apropos-documentation): Use insert instead of princ. > Please try out the latest XEmacs-21.1 from CVS and let me know if it > works or doesn't work for you. I particularly need mule users to > check this out. works for me, but I don't really use the mule stuff much. Gunnar -- Gunnar Evermann Speech, Vision & Robotics Group Engineering Department Cambridge University

1 participants
0 comments

Re: Patches Applied for 21.1.8 26 years

Adrian Aichner

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> At 11:02 PM 10/20/99 -0400, Vin Shelton wrote: >> I have applied the first set of patches to CVS in preparation for >> 21.1.8. Here is a list of them: Andy> It would be nice if the NT process fixes could go in but it Andy> doesn't look like they are complete enough yet. It works nicely on NT, but 95/98 needs investigation. I'll try to work this out with Craig Lanning. Adrian Andy> andy Andy> -------------------------------------------------------------- Andy> Dr Andy Piper Andy> Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Patches Applied for 21.1.8 26 years

Vin Shelton

2 participants
1 comments

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

Adrian Aichner

>>>>> "Andy" == Andy Piper <andy(a)xemacs.org> writes: Andy> Does this fix satisfactorily? Andy> andy Yes, highly! Thanks for the patch. I used customize-browse, customize-variable, and a package of mine for building XEmacs from within, which uses a few (widget-create 'push-button (widget-create 'choice and saw no problems anymore. Regards, Adrian Andy> 1999-10-18 Andy Piper <andy(a)xemacs.org> Andy> * gui.el (make-gui-button): be more precise about how Andy> we call Andy> callbacks. Andy> * wid-edit.el (widget-push-button-value-create): Use Andy> the new form Andy> of native gui-button.

2 participants
2 comments

Footnotes + undo 26 years

Gleb Arshinov

In XEmacs 21.1 (patch 3) "Acadia" [Lucid] (sparc-sun-solaris2.6) of Tue Aug 3 1999 on fsui02 configured using `configure sparc-sun-solaris2.6 --prefix=/usr/local --bindir=/usr/local/bin/sparc-sun-solaris2.6 --site-prefixes=/usr/scratch/sect4/cgw/local' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: C-c ! a -- footnote #1 is inserted C-x u -- any mention of footnotes in the text disappears C-c ! a -- footnote #2 is inserted (while footnote #1 is expected). Undo should probably probably decrement footnote counter in this case. Gleb

1 participants
0 comments

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

SL Baur

Andy Piper <andy(a)xemacs.org> writes in xemacs-beta(a)xemacs.org: > At 04:42 PM 10/20/99 +0900, SL Baur wrote: >> From a cvs update; make clean; ./config.status --recheck; make a few >> minutes ago: >> I have XawXPM installed as libXaw.so. Um, shouldn't configure check >> for whether -lXaw3d exists before using it? > Yes it should and I think it does: > dnl Autodetect -lXaw3d > AC_CHECK_LIB(Xaw3d, XawScrollbarSetThumb, have_xaw3d=yes, have_xaw3d=no) > So I don't understand why you are having this problem. Certainly no-one > else has reported it. What is your configuration? Are you specifiying > athena3d? Does the attached patch make any difference (you need to rerun > autoconf)? I am specifying athena3d and your patch works, thanks.

1 participants
0 comments

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

Bill Tutt

> From: Adrian Aichner [mailto:aichner＠ecf.teradyne.com] > > 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? Nope, read() is non-blocking on Win9x, but that shouldn't stop us from devising interesting alternatives to get things working. :) Sockets are the only thing on Win32 that have non-blocking reads like Unix does. Win 9x doesn't really support asynchronous I/O for files or pipes, and NT supports overlapped I/O and I/O completion ports like a champ on files, pipes, etc... So given those annoying constraints, we can't use overlapped I/O and we can't use non-blocking I/O since it doesn't exist... :( We can however approximate non-blocking reads on pipes on NT and Win9x by making use of PeekNamedPipe(). something like the following should help lead the way: int non_blocking_pipe_read //----------------------------------------------------------- // return EWOULDBLOCK if the pipe doesn't contain any readable data // ( HANDLE hPipe, // [in] handle to the pipe UINT cbBuffer, // [in] number of bytes in the buffer UINT *pcbRead, // [in,out] number of bytes that were actually read into the buffer BYTE *pbBuffer // [in,out] buffer to copy data into ) { UINT cbAvailable = 0; if (!PeekNamedPipe(hPipe, NULL, 0, NULL, &cbAvailable, NULL)) { <error handling> } if (cbAvailable > 0) { if (cbAvailable > cbBuffer) { <error handling> } if (!ReadFile(hPipe, pbBuffer, cbAvailable, pcbRead, NULL) { <error handling> } return 0; } else { return EWOULDBLOCK; } } NOTE: This only works on pipes, you can't use it on normal files. I don't know whether or not this is an issue with the XEmacs internals are not, I wouldn't be surprised if it was. Bill

1 participants
0 comments

Crash... 26 years

Georg Nikodym

For the umpteenth time, the bus has crashed... Lisp backtrace follows: resize-subwindow(#<image-instance (widget) on #<x-device on ":0.0" 0x1bf6> (#<face default "default face">)Buffers 92x21 on #<x-frame > 0x1753800 0x133b8> 609 nil) # bind (inst locale frame-or-buffer) update-tab-in-gutter(#<x-frame "emacs" 0x13282>) # bind (frame-being-created) make-frame(nil) # bind (params types) vm-goto-new-frame(folder) apply(vm-goto-new-frame folder) # bind (w types) vm-goto-new-folder-frame-maybe(folder) # (unwind-protect ...) # bind (vm-sbe-buffer layout) vm-mime-display-internal-message/rfc822(#<extent *(1800, 1871) H vm-mime-function vm-mime-layout balloon-help keymap local-map 0x1814c64 in buffer INBOX Presentation>) # (unwind-protect ...) # bind (layout) #<compiled-function (layout) "...(6)" [vm-mime-display-internal-message/rfc822 layout] 2>(#<extent *(1800, 1871) H vm-mime-function vm-mime-layout balloon-help keymap local-map 0x1814c64 in buffer INBOX Presentation>) # bind (e event) vm-mouse-popup-or-select(#<buttondown-event button2>) # bind (event) vm-mouse-button-2(#<buttondown-event button2>) # bind (command-debug-status) call-interactively(vm-mouse-button-2) # (condition-case ... . error) # (catch top-level ...) [2] + Bus Error(coredump) xemacs & Current function is fatal_error_signal 276 kill (getpid (), fatal_error_code); (verve:dbx) 1$ where [1] _libc_kill(0x0, 0xa, 0x0, 0x0, 0x211e0, 0x13b6ac), at 0xfeb9f6e4 =>[2] fatal_error_signal(sig = 10), line 276 in "emacs.c" [3] sigacthandler(0xa, 0x0, 0xffbeb710, 0x1753800, 0xffbeba80, 0x2), at 0xfeb9e788 ---- called from signal handler with signal 10 (SIGBUS) ------ [4] CallSetValues(0xfef69c6c, 0x65, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f930 [5] CallSetValues(0xfef69c6c, 0x178a400, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [6] CallSetValues(0xfef69c6c, 0x178a500, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [7] CallSetValues(0xfef69c6c, 0x178a300, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [8] CallSetValues(0xfef69c6c, 0x178a900, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [9] CallSetValues(0xfef69c6c, 0x178aa00, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [10] CallSetValues(0xfef69c6c, 0x178a700, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [11] CallSetValues(0xfef69c6c, 0x178ae00, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [12] CallSetValues(0xfef69c6c, 0x178af00, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [13] CallSetValues(0xfef69c6c, 0x178ad00, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [14] CallSetValues(0xfef69c6c, 0x178a000, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [15] CallSetValues(0xfef69c6c, 0x178ac00, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [16] CallSetValues(0xfef69c6c, 0x1446e00, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [17] CallSetValues(0xfef69c6c, 0x1753300, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [18] CallSetValues(0xfef69c6c, 0x1753800, 0x0, 0x1753800, 0xffbec848, 0x2), at 0xfef1f8c8 [19] XtSetValues(0xffbec4b0, 0xffbec848, 0xfef69c70, 0xfef69c6c, 0x1753200, 0xffbec4b0), at 0xfef1f084 [20] x_resize_subwindow(ii = 0x14ca300, w = 609, h = 21), line 2297 in "glyphs-x.c" [21] Fresize_subwindow(subwindow = UNION, width = UNION, height = UNION), line 4158 in "glyphs.c" [22] Ffuncall(nargs = 4, args = 0xffbeca54), line 3178 in "eval.c" [23] execute_optimized_program(program = 0x961110 "\xc0^I!\xad^B^I^Z\xc3^L\n"\xad+^M\xac^D\xc6 \x88\xc7\xc8!\xad \xc9^M\xc0^I!\xad^D\xca^I!"^^^K\xcc^N^K\xcd\xce\xcf\n"#\x88\xd0^N^K\xd1 \xcf#))\x87", stack_depth = 6, constants_data = 0x80f190), line 743 in "bytecode.c" [24] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbece7c), line 519 in "bytecode.c" [25] Ffuncall(nargs = 2, args = 0xffbece78), line 3210 in "eval.c" [26] run_hook_with_args_in_buffer(buf = 0x148ba00, nargs = 2, args = 0xffbece78, cond = RUN_HOOKS_TO_COMPLETION), line 3661 in "eval.c" [27] run_hook_with_args(nargs = 2, args = 0xffbece78, cond = RUN_HOOKS_TO_COMPLETION), line 3674 in "eval.c" [28] va_run_hook_with_args(hook_var = UNION, nargs = 1, ...), line 3745 in "eval.c" [29] Fmake_frame(props = UNION, device = UNION), line 510 in "frame.c" [30] Ffuncall(nargs = 2, args = 0xffbed0f0), line 3178 in "eval.c" [31] execute_optimized_program(program = 0xd30690 "\xc0^Y\n\xab^Q^I\xac^N\n＠^K\xb7A＠^Q\nA\x89^R\xac\xf1\xc4\xc5!\xab^I\xc6\xc5^I!!\x88\xaa^Y\xc4\xc7!\xab^I\xc8\xc7^I!!\x88\xaa^L\xc4\xc9!\xab^G\xc8\xc9^I!!\x88\xca\xcb !\x88^N^L\xad^E\xcd\xcb !)\x87", stack_depth = 4, constants_data = 0xb68b90), line 743 in "bytecode.c" [32] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbed5b4), line 519 in "bytecode.c" [33] Ffuncall(nargs = 2, args = 0xffbed5b0), line 3210 in "eval.c" [34] Fapply(nargs = 2, args = 0xffbed5b0), line 3388 in "eval.c" [35] Ffuncall(nargs = 3, args = 0xffbed5ac), line 3196 in "eval.c" [36] execute_optimized_program(program = 0xd30710 "^H\xad<^I\xad9\xc2 \xad5\xc3p!\xae^O^L\xab^F\xc3^L!\xae^G^M\xad^D\xc3^M!\x89^^^F\xac^K\xc7\xc8^N^I"\x88\xca \xaa^R\x8a\xcb^N^F!\x88^N^L\xad^G\xcd\xce^N^F!!))\x87", stack_depth = 4, constants_data = 0xb68a90), line 743 in "bytecode.c" [37] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbed8b8), line 519 in "bytecode.c" [38] Ffuncall(nargs = 2, args = 0xffbed8b4), line 3210 in "eval.c" [39] execute_optimized_program(program = 0x173c110 "\xc0^I!\xabF`\xc2^[^\^M\xab^X^N^F^^^G\xc8\x8e\xc9\xc2!\x88\xca\xcb^I!＠!\x88\xccc\x88*\xaa^K\xca\xcb^I!＠!\x88\xccc\x88\x8a^Lb\x88\xcd\xc2^N^N^N^O#\x88)\x8c^L`}\x88\xd0 \x88)\xd1^I!\x88*\xaaX\xd2^I!b\x88\xd3^I\xd4"^Q\xd5\xd6\xd7\xd8^N^Y!^N^Z＠\xdbH\xdcH#!q\x88^M\xab^E\xc9\xc2!\x88^N^]^V^^\xdf^I\xc2"\x88\xe0\xc2!\x88p^^!\xe2\x8e\xe3\xe4!\x88\xe5 \x88\xe6 \xab^G\xe7 \x88\xe8 \x88*\xc2^V)\xea^N+\xae^Bp\xec^N-C\xee$\x88\xec\x87o", stack_depth = 6, constants_data = 0xd8da10), line 743 in "bytecode.c" [40] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbedbc8), line 519 in "bytecode.c" [41] Ffuncall(nargs = 2, args = 0xffbedbc4), line 3210 in "eval.c" [42] execute_optimized_program(program = 0x159c0d0 "\x8a\xc0^I!)\x87\xcb", stack_depth = 2, constants_data = 0xd8ccd0), line 743 in "bytecode.c" [43] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbedec8), line 519 in "bytecode.c" [44] Ffuncall(nargs = 2, args = 0xffbedec4), line 3210 in "eval.c" [45] execute_optimized_program(program = 0x14b7a10 "\xc0 \xab\\xc1\xc2\xc3^L!!!q\x88\xc5\xc3^L!!b\x88\xc6\x89^^^G^^^H\xc9`!\x89^V^H\xab4^N^G\xac0\xca^N^H＠\xcb"\xab\n\xcc^V^G\xcd^L!\x88\xaa^W\xca^N^H＠\xce"\xab^O\xcc^V^G\xca^N^H＠\xce"^N^H＠!\x88^N^HA\x89^V^H\xac\xce^N^G?\xad^D\xcf^L!*\x87\xd0 \xad9\xc1\xd1^L!!q\x88\xd2^L!\xab^F\xd2^L!b\x88\xc6^^^S\xd4`p\xcb#\xab^F\xcd^L!\xaa^X\xd4`\xc6\xce#\x89^V^S\xab^K\xd5^N^S\xce"^N^S!\xaa^D\xcf^L!)\x87", stack_depth = 5, constants_data = 0x9b7110), line 743 in "bytecode.c" [46] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbee1d0), line 519 in "bytecode.c" [47] Ffuncall(nargs = 2, args = 0xffbee1cc), line 3210 in "eval.c" [48] execute_optimized_program(program = 0x1739910 "\xc0 \xab^T\xc1\xc2^K!!q\x88\xc4^K!\xab^\\xc4^K!b\x88\xaa^U\xc5 \xab^Q\xc1\xc6\xc7^K!!!q\x88\xc8\xc7^K!!b\x88^N^I\xcaa\xab^X\xcb^K!\x88\xccy\x88\xcd^^^N\xce )?\xad^Q\xcf^V^P\xd1\xcf!\x87^N^I\xd2s\xad^D\xd3^K!\x87^V\xa0", stack_depth = 4, constants_data = 0x9b7610), line 743 in "bytecode.c" [49] funcall_compiled_function(fun = UNION, nargs = 1, args = 0xffbee4d4), line 519 in "bytecode.c" [50] Ffuncall(nargs = 2, args = 0xffbee4d0), line 3210 in "eval.c" [51] Fcall_interactively(function = UNION, record_flag = UNION, keys = UNION), line 946 in "callint.c" [52] Fcommand_execute(cmd = UNION, record = UNION, keys = UNION), line 2613 in "eval.c" [53] execute_command_event(command_builder = 0x876680, event = UNION), line 4343 in "event-stream.c" [54] Fdispatch_event(event = UNION), line 4642 in "event-stream.c" [55] Fcommand_loop_1(), line 575 in "cmdloop.c" [56] command_loop_1(dummy = UNION), line 490 in "cmdloop.c" [57] condition_case_1(handlers = UNION, bfun = 0xe22a0 = &`xemacs`cmdloop.c`command_loop_1(Lisp_Object dummy), barg = UNION, hfun = 0xe1000 = &`xemacs`cmdloop.c`cmd_error(Lisp_Object data, Lisp_Object dummy), harg = UNION), line 1630 in "eval.c" [58] command_loop_3(), line 252 in "cmdloop.c" [59] command_loop_2(dummy = UNION), line 263 in "cmdloop.c" [60] internal_catch(tag = UNION, func = 0xe1338 = &`xemacs`cmdloop.c`command_loop_2(Lisp_Object dummy), arg = UNION, threw = (nil)), line 1305 in "eval.c" [61] initial_command_loop(load_me = UNION), line 301 in "cmdloop.c" [62] xemacs_21_2_b19_sparc_sun_solaris2_8(argc = 1, argv = 0xffbeed64, envp = 0xffbeed6c, restart = 0), line 1869 in "emacs.c" [63] main(argc = 1, argv = 0xffbeed64, envp = 0xffbeed6c), line 2294 in "emacs.c" (verve:dbx) 2$

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