June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [Success ?] XEmacs 21.0b46 and a new beta tester ... 25 years, 10 months

Neal D. Becker

>>>>> "Didier" == Didier Verna <verna(a)inf.enst.fr> writes: Didier> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> Quick intro: download the binary packages you're interested in, untar >> them somewhere, and configure with --package-path=PACKAGE-DIRECTORY, >> where PACKAGE-DIRECTORY is the directory where you untarred the >> packages. >> >> That appears to work for me. Didier> Let me add that if you don't specify any --package-path at configure Didier> time, a default value of ${prefix}/lib/xemacs/packages will be used. Does that still work if you don't install, just run in place? I tried a couple of betas back to do this, and if I recall, it didn't pick up the packages in /usr/local/lib/xemacs/packages.

1 participants
0 comments

Re: [Success ?] XEmacs 21.0b46 and a new beta tester ... 25 years, 10 months

Didier Verna

Hrvoje Niksic <hniksic(a)srce.hr> writes: > Quick intro: download the binary packages you're interested in, untar > them somewhere, and configure with --package-path=PACKAGE-DIRECTORY, > where PACKAGE-DIRECTORY is the directory where you untarred the > packages. > > That appears to work for me. Let me add that if you don't specify any --package-path at configure time, a default value of ${prefix}/lib/xemacs/packages will be used. --Didier

1 participants
0 comments

Re: ANNOUNCE: I am speaking about XEmacs, July 1 25 years, 10 months

Didier Verna

Remek Trzaska <remek(a)npac.syr.edu> writes: > Didier> Is there a chance that it could be multicasted ? > > http://www.svlug.org/meetings.shtml sez: > > The meeting will be electronically televised via the Internet > Multicast Backbone (MBONE). It can be viewed at multicast-capable > sites on the Internet. Great! I already have sdr opened :-) However, countrary to their screenshots on the web page, I don't seem to get the session announcement yet. I'll ask them whether it'll private or not. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C214 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 80 72 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

2 participants
1 comments

Re: [Success ?] XEmacs 21.0b46 and a new beta tester ... 25 years, 10 months

Hrvoje Niksic

Holger Schauer <schauer(a)coling.uni-freiburg.de> writes: > So far, so good. Oh, one minor: although I used > --with-dialogs=lucid, configure opted for Motif dialog boxes. That's because Lucid dialog boxes don't work. > Well, and now for the big problem: I don't understand the package > system. Point. Anybody want to give me a hand ? Quick intro: download the binary packages you're interested in, untar them somewhere, and configure with --package-path=PACKAGE-DIRECTORY, where PACKAGE-DIRECTORY is the directory where you untarred the packages. That appears to work for me. > (1) `read-kbd-macro' requires an explicit (require 'edmacro) > which it didn't before. Not for me. > One final note: I believe that 21.0 needs a LOT of documentation, > especially on the package stuff. Yes, I found etc/PACKAGES. But this > explains absolutely nothing. Especially new XEmacs users will never > know what they need or don't need. Couldn't agree more. > [2] I can imagine that all this package stuff has been explained and > discussed all over. Fine. But I cannot read the whole beta-ml > archive just to find out what I have to do in order to get a working > XEmacs (instead a clear instruction is all I need). Well, I've been on xemacs-beta for almost two years now, and yet I don't understand the package stuff. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Mix 2 table spoons sugar with 1 spoon salt. Put it in a bottle and stick a fuse into it. Say "Shit!" when it doesn't detonate.

2 participants
1 comments

Odd change to VM behaviour in XEmacs 21.0? 25 years, 10 months

Cameron Owen

I have noticed a change in the way VM 6.51 behaves on XEmacs 20.4 and 21.0, but haven't been able to understand why. It has to do with VM's toolbar, which it positions by default on the left side of the frame. VM uses set-specifier to set left-toolbar-width. In 20.4 this appears to trigger a resizing of the frame to increase the frame's width by left-toolbar-width. In 21.1, a resize seems to not get triggered. This generally leads to 72-column-wide windows in that frame, but occasionally results in the VM toolbar overlaying 80-column-wide windows, and display competition between the text in the windows and the toolbar buttons. Any ideas why this is happening? Cameron

1 participants
0 comments

crash using 21.0 b46 25 years, 10 months

Fabrice POPINEAU

Hi, I'm running native 21.0-b46 under NT 4sp3. It was compiled with options : USE_UNION_TYPE=1 USE_MINIMAL_TAGBITS=1 USE_INDEXED_LRECORD_IMPLEMENTATION=1 It has *crashed* in alloc.c, at the following point with an invalid 'string' value. I insist : this was not an assertion failure, but a crash due to a bad memory reference in from_s_chars->string : ============================================================================ /* If the string_chars struct is marked as free (i.e. the STRING pointer is 0xFFFFFFFF) then this is an unused chunk of string storage. This happens under Mule when a string's size changes in such a way that its fullsize changes. (Strings can change size because a different-length character can be substituted for another character.) In this case, after the bogus string pointer is the "fullsize" of this entry, i.e. how many bytes to skip. */ if (FREE_STRUCT_P (from_s_chars)) { fullsize = ((struct unused_string_chars *) from_s_chars)->fullsize; from_pos += fullsize; continue; } string = from_s_chars->string; => assert (!(FREE_STRUCT_P (string))); size = string_length (string); fullsize = STRING_FULLSIZE (size); if (BIG_STRING_FULLSIZE_P (fullsize)) abort (); /* Just skip it if it isn't marked. */ #ifdef LRECORD_STRING if (! MARKED_RECORD_HEADER_P (&(string->lheader))) #else if (!XMARKBIT (string->plist)) #endif { from_pos += fullsize; continue; } Call Stack: =========== compact_string_chars() line 4046 + 3 bytes gc_sweep() line 4251 garbage_collect_1() line 4558 funcall_recording_as(Lisp_Object {...}, int 2, Lisp_Object * 0x0082d230) line 3116 Ffuncall(int 2, Lisp_Object * 0x0082d230) line 3238 + 19 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 416 + 16 bytes funcall_lambda(Lisp_Object {...}, int 3, Lisp_Object * 0x0082d998) line 3599 + 38 bytes funcall_recording_as(Lisp_Object {...}, int 3, Lisp_Object * 0x0082d994) line 3200 + 20 bytes Ffuncall(int 4, Lisp_Object * 0x0082d994) line 3238 + 19 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 416 + 16 bytes Feval(Lisp_Object {...}) line 3063 + 153 bytes condition_case_1(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x01052ce3 Feval(Lisp_Object), Lisp_Object {...}, Lisp_Object (Lisp_Object, Lisp_Object)* 0x0105084e run_condition_case_handlers(Lisp_Object, Lisp_Object), Lisp_Object {...}) line 1653 + 7 bytes condition_case_3(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 1718 + 27 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 576 + 19 bytes funcall_lambda(Lisp_Object {...}, int 5, Lisp_Object * 0x0082e67c) line 3599 + 38 bytes funcall_recording_as(Lisp_Object {...}, int 5, Lisp_Object * 0x0082e678) line 3200 + 20 bytes Ffuncall(int 6, Lisp_Object * 0x0082e678) line 3238 + 19 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 416 + 16 bytes funcall_lambda(Lisp_Object {...}, int 2, Lisp_Object * 0x0082f0e0) line 3599 + 38 bytes funcall_recording_as(Lisp_Object {...}, int 2, Lisp_Object * 0x0082f0dc) line 3200 + 20 bytes Ffuncall(int 3, Lisp_Object * 0x0082f0dc) line 3238 + 19 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 416 + 16 bytes funcall_lambda(Lisp_Object {...}, int 5, Lisp_Object * 0x0082f410) line 3599 + 38 bytes funcall_recording_as(Lisp_Object {...}, int 5, Lisp_Object * 0x0082f40c) line 3200 + 20 bytes Ffuncall(int 6, Lisp_Object * 0x0082f40c) line 3238 + 19 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 416 + 16 bytes funcall_lambda(Lisp_Object {...}, int 5, Lisp_Object * 0x0082f838) line 3599 + 38 bytes funcall_recording_as(Lisp_Object {...}, int 5, Lisp_Object * 0x0082f834) line 3200 + 20 bytes Ffuncall(int 6, Lisp_Object * 0x0082f834) line 3238 + 19 bytes Fbyte_code(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 416 + 16 bytes funcall_lambda(Lisp_Object {...}, int 1, Lisp_Object * 0x0082fa68) line 3599 + 38 bytes funcall_recording_as(Lisp_Object {...}, int 1, Lisp_Object * 0x0082fa64) line 3200 + 20 bytes Ffuncall(int 2, Lisp_Object * 0x0082fa64) line 3238 + 19 bytes Fcall_interactively(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 935 + 22 bytes Fcommand_execute(Lisp_Object {...}, Lisp_Object {...}, Lisp_Object {...}) line 2584 + 17 bytes execute_command_event(command_builder * 0x01c9a8c0, Lisp_Object {...}) line 4346 + 25 bytes Fdispatch_event(Lisp_Object {...}) line 4645 + 71 bytes Fcommand_loop_1() line 579 + 9 bytes command_loop_1(Lisp_Object {...}) line 495 condition_case_1(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x010350c2 command_loop_1(Lisp_Object), Lisp_Object {...}, Lisp_Object (Lisp_Object, Lisp_Object)* 0x01034b4f cmd_error(Lisp_Object, Lisp_Object), Lisp_Object {...}) line 1653 + 7 bytes command_loop_3() line 256 + 35 bytes command_loop_2(Lisp_Object {...}) line 268 internal_catch(Lisp_Object {...}, Lisp_Object (Lisp_Object)* 0x01034cba command_loop_2(Lisp_Object), Lisp_Object {...}, int * 0x00000000) line 1328 + 7 bytes initial_command_loop(Lisp_Object {...}) line 305 + 25 bytes STACK_TRACE_EYE_CATCHER(int 1, char * * 0x01c2bc80, char * * 0x01c30000, int 0) line 1702 + 9 bytes main(int 1, char * * 0x01c2bc80, char * * 0x01c30000) line 2119 + 21 bytes variables: ========== - from_s_chars 0x021d95b8 + string 0x70756f72 + chars 0x021d95bc "* {nntp:news.ese-metz.fr} (Group PenDel PC)----Top------------------------------------ "

1 participants
0 comments

[Success ?] XEmacs 21.0b46 and a new beta tester ... 25 years, 10 months

Holger Schauer

Hi Folks ! Okay, today I had the chance of rolling the ball and give the latest beta a try. Before anyone barfs at me: yes, this was my first try to build a beta, but I have been happily compiling non-betas since 19.12. So, first Installation: uname -a: SunOS noblues.coling.uni-freiburg.de 5.6 Generic sun4u sparc SUNW,Ultra-1 ./configure 'sparc-sun-solaris2.6' '--cflags=-O6' '--prefix=/home/schauer/misc' '--with-dialogs=lucid' '--site-includes=/home/schauer/misc/include' '--site-libraries=/home/schauer/misc/lib' '--with-jpeg' XEmacs 21.0 "Toggenburg" configured for `sparc-sun-solaris2.6'. Where should the build process find the source code? /home/schauer/misc/src/packages/xemacs/xemacs-21.0-b46 What installation prefix should install use? /home/schauer/misc What operating system and machine description files should XEmacs use? `s/sol2.h' and `m/sparc.h' What compiler should XEmacs be built with? gcc -O6 Should XEmacs use the GNU version of malloc? yes Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? x11 Where do we find X Windows header files? /usr/dt/include /usr/openwin/include Where do we find X Windows libraries? /usr/dt/lib /usr/openwin/lib Additional header files: /home/schauer/misc/include Additional libraries: /home/schauer/misc/lib Runtime library search path: /usr/dt/lib:/usr/openwin/lib Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for X-Face message headers. Compiling in support for JPEG image conversion. Compiling in native sound support. Compiling in support for GNU DBM. Compiling in support for CDE. Compiling in support for ToolTalk. Compiling in EXPERIMENTAL support for Drag'n'Drop ( CDE ). Compiling in support for proper session-management. Using Lucid menubars. Using Lucid scrollbars. Using Motif dialog boxes. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. So far, so good. Oh, one minor: although I used --with-dialogs=lucid, configure opted for Motif dialog boxes. The first problem I encountered was that I haven't read the etc/BETA not carefully enough, and was bitten when I just issued 'make'. Make (correctly) complained that it couldn't find makeinfo and just stopped. I then searched the Makefile a little to discover that 'make beta' wouldn't try to build with info-files. But anyway, what about some switch --with-info ? Next step: test src/xemacs. Works, but the icons (i.e. the toolbar looks really worse) since the background won't match the frame appearance anymore. Okay, been here, done that. 'make install' - same procedure as last year, james, no info files, no install. Okay, copied the files/directories by hand. Well, and now for the big problem: I don't understand the package system. Point. Anybody want to give me a hand ? Okay, what did I do ? I installed everything from 21.0/packages/binary-packages that looked useful to me (to bad there is no Sumo-tar-ball yet). My .emacs [1] now loads nearly correctly (even without my understanding ;-) up to just following minor glitches: (1) `read-kbd-macro' requires an explicit (require 'edmacro) which it didn't before. (2) In mail-abbrevs.el I found the following comment: ";; - Add an autoload of define-mail-alias to loaddefs.el." This hasn't happend yet, obviously. Perhaps the comment should also apply to `read-kbd-macro' ? (3) #'vm and #'gnus neither seem to be defined there, i.e. I have to load(-library, of course) vm and gnus by hand (haven't checked require up to now. (I somewhere remember somebody asking why vm needs to be dumped - wait a minute, need I install all packages in advance before building XEmacs ? Naa, that can not be true) (4) ilisp just eats up allegro cl. This is, it failed (I once get an error about an undefined symbol 'turn-on-fast-lock', which I haven't used in my .emacs) but stays quiet. Another M-x allegro just does nothing. No hang, no error, no message, just nothing. After that I wanted to make sure, that I haven't overlooked anything stupid and check the info files. Hmm, no "dir"-File installed. Info-auto-generate-directory has value 'if-missing, but won't do anything. Copied the file from the source tree. Okay, now info works, but of course the package-info-files are not shown. Thanks for reading all this and sending me "hey, start looking at <there>, before you proove yourself to be entirely stupid." [1] My .emacs is not trivial, but not awfully overloaded either. A lot of package configurations (AucTeX, prolog, ilisp, calendar, Gnu and XEmacs versions with different major/minors, sigh ...) separated on a bunch of files. One final note: I believe that 21.0 needs a LOT of documentation, especially on the package stuff. Yes, I found etc/PACKAGES. But this explains absolutely nothing. Especially new XEmacs users will never know what they need or don't need. And if some packages need to be available before compiling XEmacs, please state that LOUD and CLEAR in the INSTALL file (or at least in the etc/BETA file [2]). Holger [2] I can imagine that all this package stuff has been explained and discussed all over. Fine. But I cannot read the whole beta-ml archive just to find out what I have to do in order to get a working XEmacs (instead a clear instruction is all I need). -- --- http://www.coling.uni-freiburg.de/~schauer --- Why people hate using Lisp: "Are people suffering from parenthophobia-by-proxy, mistaking `parens' for `parents'?" - Erik Naggum in comp.emacs.xemacs

1 participants
0 comments

Re: package-get-base props 25 years, 10 months

Pete Ware

There isn't anything in mind for allowing temacs to redump. I have no idea why vm must be dumped. Is it an error? --pete

1 participants
0 comments

Re: func-menu.el fix for LaTeX modes 25 years, 10 months

Didier Verna

Anthony Rossini <arossini(a)biostat.washington.edu> writes: > Solution: > in the function "fume-find-next-latex-section-name", in each call > to concat, make sure that integers > (called fume-tex-$chapter\|\(sub$*section\)) > are wrapped by (int-to-string). > > I'm guessing that you can't mix integers and strings/chars in the concat > function anymore, but you could in betas 39 and earlier. Does this > theory sound correct? That's it, exactly. I'll submit a patch for you. --Didier

1 participants
0 comments

func-menu.el fix for LaTeX modes 25 years, 10 months

A.J. Rossini

Sorry, I can't send a patch (until Monday -- really screwy email, connecting via W/NT, but working on a non-networked Linux box). Solution: in the function "fume-find-next-latex-section-name", in each call to concat, make sure that integers (called fume-tex-$chapter\|\(sub$*section\)) are wrapped by (int-to-string). I'm guessing that you can't mix integers and strings/chars in the concat function anymore, but you could in betas 39 and earlier. Does this theory sound correct? best, -tony -- Anthony Rossini UW Biostatistics, Center for AIDS Research Manifold Graphics, Inc. Epimetrics Corp.

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 June 1998