March 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Accelerator usage 24 years, 8 months

Hrvoje Niksic

torkel(a)hpc2n.umu.se (Björn Torkelsson) writes: > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > torkel(a)hpc2n.umu.se (Björn Torkelsson) writes: > > > > > Hrvoje Niksic <hniksic(a)iskon.hr> writes: > > > > > > > [1 <text/plain>] > > > > First, thanks to Ben for acceleratorizing the menu bar. I like the > > > > change a lot. However, the obvious question comes up: how do I use > > > > the accelerators? Neither M-f nor A-f appear to work. > > > > > > You have to turn it on in Options->Menubars->Alt/Meta Selects Menu > > > Items > > > > Thanks for the tip -- I've tried it and it works. > > > > I don't like the "Alt/Meta" wording, but I think I understand why it's > > there. I have both Meta and Alt (both detected by Emacs), and I'd > > expect accelerators to be invoked by Alt, leaving Meta free for > > commands. Instead, Meta is used for accelerators by default. > > You should be able to change it to Alt by setting > menu-accelerator-modifiers. I know that. What I'm talking about is that I expected the right thing (Alt chosen for prefix) to happen by default.

2 participants
1 comments

Re: nasty crash 24 years, 8 months

Jan Vroonhof

Ben Wing <ben(a)666.com> writes: > Looking at unbind_to_hairy(), I think I see a logic error. If so, it's > amazing we are able to run ok at all. There are other people seeing very weird crashes involving very deep traces (see for instance the eudc thread). Jan P.S. Most of these crashes involve deep levels of bytecode execution. I am wondering whether this (or a related) change triggered it. 1999-01-30 Martin Buchholz <martin(a)xemacs.org> * bytecode.c (funcall_compiled_function): Call UNBIND_TO_GCPRO instead of UNBIND_TO_GCPRO_VARIABLES_ONLY.

1 participants
0 comments

[Failure] XEmacs 21.2-b31 "Iris", i586-pc-win32, USE_PORTABLE_DUMPER=1 24 years, 8 months

Adrian Aichner

Portable Dumper for native NT probably needs adjustment now that -subsystem:windows is used. I don't know how :-( Adrian config.inc: USE_PORTABLE_DUMPER=1 INSTALL_DIR=c:\XEmacs\XEmacs-$(XEMACS_VERSION_STRING) PACKAGE_PREFIX=c:\XEmacs HAVE_XPM=1 HAVE_PNG=1 HAVE_TIFF=1 HAVE_JPEG=1 HAVE_XFACE=1 DEBUG_XEMACS=1 GUNG_HO=1 MAKEINFO=d:\tmp\texinfo-4.0\makeinfo\makeinfo.exe COMPFACE_DIR=d:\tmp\libs4xemacs\compface JPEG_DIR=d:\tmp\libs4xemacs\jpeg-6b TIFF_DIR=d:\tmp\libs4xemacs\tiff-v3.4 ZLIB_DIR=d:\tmp\libs4xemacs\zlib PNG_DIR=d:\tmp\libs4xemacs\libpng-1.0.2 XPM_DIR=d:\tmp\libs4xemacs\xpm-3.4k # USE_CRTDLL=1 # USE_SYSTEM_MALLOC=1 > XEmacs Build Report as generated with > M-x build-report RET > by build-report-version $Revision: 1.3 $ follows: > Contents of d:\tmp\21.2\xemacs\Installation: > (Output from most recent run of ./configure) OS: Windows_NT XEmacs 21.2-b31 \"Iris\" configured for `i586-pc-win32'. Building XEmacs in \"d:\\tmp\\21.2\\xemacs\\nt\". Using compiler \"cl -nologo -W3 -Od -Zi -MDd\". Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b31\". Package path is \"~\\.xemacs;;c:\\XEmacs\\site-packages;c:\\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 TIFF images. Compiling in support for JPEG images. Compiling in support for X-Face message headers. 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. Using minimal tagbits. Using indexed lrecord implementation. Using portable dumper. Using system malloc. Using DLL version of C runtime library Compiling in extra debug checks. XEmacs will be slow! > Contents of d:\tmp\21.2\xemacs\nt\xemacs-make-all.err > keeping lines matching > "^--\[\[\|\]\]$\|^$cd\|n?make$\s-\|errors?\|warnings?\|pure.*$space\|size$\|hides\b\|strange\|shadowings\|^Compil$ing\s-+in\|ation$\|^Using\|not\s-+found\|^While\s-+compiling.*$ \s-+.+$*\|^Note:\|Installing\|[Ff]ile(s) copied\|\s-+tests\s-+" > and then deleting lines matching > "confl.*with.*auto-inlining\|^Formatting:" cd d:\tmp\21.2\xemacs\nt\ nmake /f xemacs.mak all Compilation started at Tue Mar 14 00:28:05 2000 +0100 (W. Europe Standard Time) Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b31\". 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. ..\src\alloc.c(5096) : warning C4090: 'function' : different 'const' qualifiers ..\src\alloc.c(5096) : warning C4022: 'memcpy' : pointer mismatch for actual parameter 1 ..\src\nt.c(1411) : warning C4273: 'fstat' : inconsistent dll linkage. dllexport assumed. ..\src\nt.c(1446) : warning C4273: 'stat' : inconsistent dll linkage. dllexport assumed. ..\src\nt.c(1735) : warning C4113: 'void (__cdecl *)()' differs in parameter lists from 'void (__cdecl *)(int )' ..\src\process-nt.c(447) : warning C4028: formal parameter 2 different from declaration ..\src\process-nt.c(447) : warning C4024: 'EnumWindows' : different types for formal and actual parameter 1 msvcrtd.lib(crtexew.obj) : error LNK2001: unresolved external symbol _WinMain＠16 ..\src\temacs.exe : fatal error LNK1120: 1 unresolved externals NMAKE : fatal error U1077: 'link.exe' : return code '0x460' Compilation exited abnormally with code 2 at Tue Mar 14 00:32:26

3 participants
5 comments

Re: `scroll-up-command' still broken in 21.2 under AIX 24 years, 8 months

Markus Alt

Sorry for the delayed answer - had to do some "real work" yesterday. ;-) vroonhof(a)math.ethz.ch wrote: > Now we only need to find out the real problem :-). Could you put a > breakpoint in this code from window.c > > if (INTP (Vwindow_pixel_scroll_increment)) > fheight = XINT (Vwindow_pixel_scroll_increment); > else if (!NILP (Vwindow_pixel_scroll_increment)) > default_face_height_and_width (window, &fheight, &fwidth); > > [I am particularly interested in the value of fheight at this point. I > have a feeling it might be 0 (which is really bad, in that case please > single step in to default_face_height_and_width to see where the 0 is > coming from)] You had the right feeling ...! After loading a file larger than the visible buffer and pressing the PgDown key, it stops at the breakpoint in the "else" branch (line 4107) and fheight has indeed a value of 0. But where does the 0 come from? Good question. I must admit that single stepping through default_face_height_and_width didn't make this clear to me. In other words: If I set a second breakpoint at the next line, i.e. if (Dynarr_length (dla) >= 1) modeline = Dynarr_atp (dla, 0)->modeline; dl = Dynarr_atp (dla, modeline); then fheight already has a value of 14 (which is my current default font size and thus correct), so it seems like default_face_height_and_width returns the correct value after its first pass. But pressing PgDown a second time still does not scroll, although one should think that fheight is non-zero now. In fact, my debugger shows a value of +804392872 when stopping again at the first breakpoint (overflow?). Continue to the 2nd breakpoint and fheight == 14 again. Don't know if this is of great help; let me know what I can do to provide any further information. > if (value > 0) > { > /* Go for partial display line scrolling. This just means bumping > the clip by a reasonable amount and redisplaying, everything else > remains unchanged. */ > if (!NILP (Vwindow_pixel_scroll_increment) > && > Dynarr_length (dla) >= (1 + modeline) > && > (dl->ascent - dl->top_clip) - fheight * value > 0) > { > WINDOW_TEXT_TOP_CLIP (w) += value * fheight; > MARK_WINDOWS_CHANGED (w); > > [Your XEmacs is probably not scrolling because this if statement is > true. Could you please find out why (fheight == 0 is the only > reason I can think of).] Looks like that ... Markus

1 participants
0 comments

Re: EUDC crash with 21.2.31 on Solaris 2.7 24 years, 8 months

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > Jan> That would at least make some sense as that is basically the only > Jan> special thing eudc does.. What happens if you explicitly load > Jan> "eudc.el" (i.e. the uncompiled file)? > > It works just fine. (See also my reply to Oscar.) OK.. It seems like you are on to some race condition in the new optimized byte code stuff. You need to go on hunting. Homework for today 1. Add a (debug-on-entry 'eudc-set-server) to the top your options file. Single step until you get the crash (it might be you don't get it anymore) :-( 2. Start stripping stuff from eudc-set-server until the crash disappears. Repeat for the offending functions it calls. Jan P.S. Are you compiling with any special options (pdump ?)

1 participants
0 comments

Re: read-file-name loading cl-macs 24 years, 8 months

Hrvoje Niksic

Jeff Miller <jmiller(a)smart.net> writes: > Hrvoje> Now the recent messages buffer shows "Loading cl-macs". > > I see the cl-macs message in the xterm i start xemacs from long > before the emacs frame even pops on the screen. > > And I have been seeing this for a long time. I'm reasonably sure I > know why too. I believe it's calendar. Then calendar has the same problem. Note that I've just sent out a patch that fixes the problem for find-file; it can probably be fixed for calendar as well.

2 participants
1 comments

failure under XFree86 4.0 24 years, 8 months

Michael Harnois

The configure test for X11/Intrinsic.h fails with the above installed. I haven't a clue what's wrong; the file is right there where it belongs. I get X11 compilation variables: x_libraries = '/usr/X11R6/lib' x_includes = '/usr/X11R6/include' X_CFLAGS = ' -I/usr/X11R6/include' X_LIBS = ' -L/usr/X11R6/lib' X_PRE_LIBS = ' -lSM -lICE' X_EXTRA_LIBS = '' Defining BITMAPDIR = "/usr/X11R6/include/X11/bitmaps:/usr/X11R6/include/bitmaps" checking for X defines extracted by xmkmf Defining NARROWPROTO Defining linux Defining __i386__ Defining _POSIX_SOURCE Defining _XOPEN_SOURCE Defining _BSD_SOURCE Defining _SVID_SOURCE checking for X11/Intrinsic.h... no configure: error: Unable to find X11 header files. config.log says configure:5791: checking for X defines extracted by xmkmf configure:5823: checking for X11/Intrinsic.h configure:5831: gcc -E -I/usr/X11R6/include conftest.c >/dev/null 2>conft est.out In file included from configure:5826: confdefs.h:56: warning: `_XOPEN_SOURCE' redefined confdefs.h:14: warning: this is the location of the previous definition configure: failed program was: #line 5826 "configure" #include "confdefs.h" #include <X11/Intrinsic.h> if that helps. -- Michael D. Harnois, Redeemer Lutheran Church, Washburn, IA mdharnois(a)home.com aa0bt(a)aa0bt.ampr.org Physics is like sex: sure, it may give some practical results, but that's not why we do it. -- Richard Feynman

1 participants
0 comments

Re: xemacs 21.9 advice and dired 24 years, 8 months

Jan Vroonhof

Uwe Brauer <oub(a)eucmos.sim.ucm.es> writes: > come per default but has to be loaded down as a package, so far so > good but even advice was not included and for me it is not clear where > to find it. Could someone please tell me where to find advice? The advice is in README.packages (includes a minimal recommended set). dired is in the dired package! > Could one discuss maybe the politics of what a minimal > xemacs must include? IMHO auctex, reftex etc not but dired yes. One can. However it would be more productive to make a special xemacs-<version>-all release that includes everything as in previous releases. Something like that is likely to happen before 21.2 comes out. Would that satisfy your needs? Jan

1 participants
0 comments

Re: `scroll-up-command' still broken in 21.2 under AIX 24 years, 8 months

Jan Vroonhof

Andy Piper <andy(a)xemacs.org> writes: > >Bingo! This fixes it! As well on the Motif as on the Motif-less XEmacs > >which I built following Michael's recommendation. Thanks a lot! > > So why does this only fail on AIX???? It probably has a bug that makes it think the default face has height 0 or something weird like that. Jan

1 participants
0 comments

Re: EUDC crash with 21.2.31 on Solaris 2.7 24 years, 8 months

Jan Vroonhof

Raymond Toy <toy(a)rtp.ericsson.se> writes: > Note that if I try any of the above suggestions (except > eudc-set-server) WITH an .eudc-options file, I get a crash. > > Hope this helps, Then it must be somehow related to the pack that the settings get evaluated during a load of eudc. That would at least make some sense as that is basically the only special thing eudc does.. What happens if you explicitly load "eudc.el" (i.e. the uncompiled file)? Jan

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 March 2000