May 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: Bookmake file handling 25 years, 6 months

Adrian Aichner

>>>>> "Meino" == Meino Christian Cramer <root(a)solfire.ludwigsburg.netsurf.de> writes: Meino> Hi! Meino> A few days ago I updated from XEmacs-20.4 to XEmacs-21.0(.67). Meino> With the previous version, my bookmarksfile (~/.emacs.bmk) Meino> was automatically loaded on startup of XEmacs. Meino> XEmacs 21.0 ignores this file and don't load it automgically Meino> until I save anything to it. Meino> How can I avoid this "feature"? Hello Meino, according to the docs of `bookmark-load' you are right -- XEmacs should load your bookmark-default-file for you. I can confirm for 1.0b67 that not bookmarks are available until I load the file manually via Edit->Bookmarks->Load a bookmark file. bookmark.el is now part of the edit-utils package, which is maintained by Author version: 21.0b63 1999-02-18: XEmacs Development Team <xemacs-beta(a)xemacs.org> You may, however, (bookmark-load bookmark-default-file) in your .emacs file. Regards, Adrian Meino> Thank you for any heklp in advance! Meino> KEEP HACKING! Meino> Meino -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

Re: Lisp, siod and LyX 25 years, 6 months

Karl M. Hegbloom

>>>>> "Uwe" == Uwe Brauer <oub(a)eucmos.sim.ucm.es> writes: Uwe> I am writing so to speak as a mediator between the maintainer Uwe> of the LyX program and the xemacs maintainers. Uwe> 1. LyX is written in C++ (I don't know any details) and now Uwe> the maintainer is looking for an extension language Uwe> available as a library! I think that `Guile' might be a good choice; they have it in mind to make it be Emacs lisp compatible, it's a modern Scheme, it's got _threads_, _objects_, _modules_, and is a _library_ made for embedding. There is a partly working(?) compiler for it that produces human readable C. It can perform dynamic linking to .so library code. The .so can define a module namespace of its own. You can find it via anon CVS, http, and ftp. <URL:http://www.red-bean.com/guile/> Please help it evolve! `siod' has a way to dump a heap image you can put a she-bang line on and run; Guile doesn't have that... There's a `tguile' (guile undump or some such) that will dump, like emacs does. I've had it working before; it improves start up time. It would be nice if it could save state to a "band" like MIT-Scheme does, without exiting, so you could have persistant state.

1 participants
0 comments

Bookmake file handling 25 years, 6 months

Meino Christian Cramer

Hi! A few days ago I updated from XEmacs-20.4 to XEmacs-21.0(.67). With the previous version, my bookmarksfile (~/.emacs.bmk) was automatically loaded on startup of XEmacs. XEmacs 21.0 ignores this file and don't load it automgically until I save anything to it. How can I avoid this "feature"? Thank you for any heklp in advance! KEEP HACKING! Meino

1 participants
0 comments

info 25 years, 6 months

ljp

Hello- I just started using xemacs 21.2 for win32 on win98. The info file doesn't seem to work. Whenever I try to browse the info manual, I get this error- No such node: Any help would be great. Everything else seems to work, with the exception of a few things. Coming from GNUemacs, theres a few differences in lisp interpretation that I am getting used to. LP

1 participants
0 comments

viper and gnus in 21.0-b67 25 years, 6 months

tvaughan＠aventail.com

I have just installed xemacs 21.0-b67, and a sumo tarball dated 1999-03-12 on Solaris 1.5.1 (sparc) and RH GNU/Linux 5.2 (i686). Compilation, installation, and start-up all went great. On both platforms, after loading viper, I am told: Symbol's function definition is void: vc-backend whenever I try to save a file via: ESC : [w|x] RET I am able to save a file via: C-x C-s Also, when I `M-x gnus' on the GNU/Linux box (the Solaris box does not have access to the mail spool), gnus 5.6.45 (included in the sumo tarball mentioned above) and pgnus 0.83 (latest gnus beta from www.gnus.org), I am told: movemail: Permission denied for /var/spool/mail/Ea12407--see source file lib-src/ Ea12407 is not the name of the mail spool. I am unable to load gnus at this point. I have not defined my own movemail program. gnus and pgnus work fine in xemacs 20.4. I don't know lisp, otherwise I would have hoped to included a patch as well. Thanks, Tom -- Tom Vaughan <tvaughan at aventail dot com>

4 participants
10 comments

[Failure] PAST XEmacs 21.2-b13 "Demeter", i586-pc-win32 25 years, 6 months

Adrian Aichner

Hello Everybody, updated from CVS a few minutes ago, applied Norbert Koch's patch xemacs.mak.diff from a few days ago: --- xemacs.mak Tue May 4 07:31:30 1999 +++ xemacs.nk Tue May 4 11:58:43 1999 ... Now I get as far as ..\src\toolbar-msw.c(212) : error C2088: '+' : illegal for union Regards, Adrian > XEmacs Build Report as generated with > M-x build-report RET > by build-report-version $Revision: 1.1.1.1 $ follows: > Contents of d:\export\home\tmp\21.2\xemacs\nt\Installation: > (Output from most recent run of ./configure) OS: Windows_NT XEmacs 21.2-b13 \"Demeter\" configured for `i586-pc-win32'. Building XEmacs in \"d:\\export\\home\\tmp\\21.2\\xemacs\\nt\". Using compiler \"cl -nologo -W3 -O2 -G5\". Installing XEmacs in \"c:\\Program Files\\XEmacs\\XEmacs-21.2-b13\". Package path is \"~\\.xemacs;;c:\\Program Files\\XEmacs\\site-packages;c:\\Program Files\\XEmacs\\mule-packages;c:\\Program Files\\XEmacs\\xemacs-packages\". Compiling in support for Microsoft Windows native GUI. Compiling in MULE. 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 native sounds. Compiling in fast dired implementation. Using minimal tagbits. Using indexed lrecord implementation. Using union type for Lisp object storage. > Contents of d:\export\home\tmp\21.2\xemacs\nt\xemacs-make-install.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" > and then deleting lines matching > "confl.*with.*auto-inlining" cd d:\export\home\tmp\21.2\xemacs\nt\ nmake -f xemacs.mak PACKAGEPATH="c:\\Program Files\\XEmacs\\xemacs-packages" USE_UNION_TYPE=1 GUNG_HO=1 HAVE_MSW=1 HAVE_MULE=1 HAVE_NATIVE_SOUND=1 HAVE_XFACE=1 COMPFACE_DIR="d:\export\home\tmp\libs4xemacs\compface" HAVE_XPM=1 XPM_DIR="d:\export\home\tmp\libs4xemacs\xpm-3.4k" HAVE_PNG=1 PNG_DIR="d:\export\home\tmp\libs4xemacs\libpng-1.0.2" HAVE_TIFF=1 TIFF_DIR="d:\export\home\tmp\libs4xemacs\tiff-v3.4" HAVE_JPEG=1 JPEG_DIR="d:\export\home\tmp\libs4xemacs\jpeg-6b" ZLIB_DIR="d:\export\home\tmp\libs4xemacs\zlib" DEBUG_XEMACS=0 install Compilation started at Fri May 07 22:45:43 1999 Installing XEmacs in \"c:\\Program Files\\XEmacs\\XEmacs-21.2-b13\". 1 file(s) copied. 1 file(s) copied. 1 file(s) copied. ..\lib-src/pop.c(925) : warning C4013: 'close' undefined; assuming extern returning int ..\lib-src\run.c(68) : warning C4101: 'j' : unreferenced local variable ..\lib-src\run.c(160) : warning C4101: 'tmp' : unreferenced local variable ..\src\glyphs-msw.c(2306) : warning C4133: ':' : incompatible types - from 'struct HICON__ *' to 'struct HBITMAP__ *' E:\Program Files\Microsoft Visual Studio\VC98\include\direct.h(132) : warning C4030: first formal parameter list longer than the second list ..\src\toolbar-msw.c(212) : error C2088: '+' : illegal for union NMAKE : fatal error U1077: 'cl' : return code '0x2' Compilation exited abnormally with code 2 at Fri May 07 22:48:00 -- Adrian Aichner Teradyne GmbH, European Design Center Integra Test Division Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 (What is a Fax?) D-81673 MUENCHEN E-mail adrian.aichner(a)teradyne.com

1 participants
0 comments

xemacs crash in package update 25 years, 6 months

gluzberg＠us.ibm.com

This bug report will be sent to the XEmacs Development Team, not to your local site managers!! Please write in English, because the XEmacs maintainers do not have translators to read other languages for them. In XEmacs 21.0 "20 minutes to Nikko" [Lucid] (i686-redhat-linux) of Thu May 6 1999 on javabench5.watson.ibm.com configured using `configure i686-redhat-linux --with-gcc --cflags=-O6 --with-gnu-make --dynamic --with-x11=yes --with-xpm --with-xface --with-database=gnudbm --with-socks' Please describe exactly what actions triggered the bug and the precise symptoms of the bug: I set up xemacs as in the intructions, except for one thing. In the file config.h I had to change all the occurences of Rconnect, Rbind, etc (for the socks stuff) to SOCKSconnect, SOCKSbind, etc. This is because I was using socks5 instead of socks4. I also had to include -lsocks5 in the link portion of the main Makefile (src/Makefile) I downloaded the sumo tar file and installed it as indicated in the instructions. I then set up the following .emacs file from the option menu for the root user: (custom-set-variables '(efs-remote-shell-takes-user t) '(socks-server (quote ("Default server" "socks2.watson.ibm.com" 1080 4))) '(efs-ftp-program-name "/usr/local/bin/rftp")) (custom-set-faces) rftp is just a socksofied ftp program from socks version 5. I then (as root) went into the the Options menu, went to Manage Packages, "Add download site" added the two top-most sites (xemacs.org and cso.uiuc.edu) and then selected "update install packages"... after finally connecting to the site ( i think it also went as far as succsessfully changing into the proper directory), xemacs promptly crashed. The crash message is included below followed by the C stack backtrace: Fatal error (11). Your files have been auto-saved. Use `M-x recover-session' to recover them. Please report this bug by running the send-pr script included with XEmacs, or selecting `Send Bug Report' from the help menu. As a last resort send ordinary email to `crashes(a)xemacs.org'. *MAKE SURE* to include the information in the command M-x describe-installation. If at all possible, *please* try to obtain a C stack backtrace; it will help us immensely in determining what went wrong. To do this, locate the core file that was produced as a result of this crash (it's usually called `core' and is located in the directory in which you started the editor, or maybe in your home directory), and type gdb /usr/local/bin/xemacs core then type `where' when the debugger prompt comes up. (If you don't have GDB on your system, you might have DBX, or XDB, or SDB. A similar procedure should work for all of these. Ask your system administrator if you need more help.) Lisp backtrace follows: popup-dialog-box(("Package-get entries not PGP signed, continue? " ["Yes" yes t] ["No" no t] nil ["Cancel" abort t])) # bind (echo-keystrokes event prompt) yes-or-no-p-dialog-box("Package-get entries not PGP signed, continue? ") # bind (prompt) yes-or-no-p("Package-get entries not PGP signed, continue? ") # (unwind-protect ...) # bind (content-beg content-end beg end buf) package-get-update-base-from-buffer(#<buffer "*package database*">) # (unwind-protect ...) # (unwind-protect ...) # bind (buf force-current db-file) package-get-update-base(nil t) # bind (force-current) package-get-require-base(t) #<compiled-function nil "...(8)" [package-get-require-base t exit (mapcar #<compiled-function ... "...(14)" ... 4> packages-package-list)] 2 ("/usr/local/lib/xemacs-21.0-b67/lisp/package-get.elc" . 13956) nil>() call-interactively(package-get-update-all) # (condition-case ... . error) # (catch top-level ...) Here is the C stack backtrace: #0 0x40392811 in kill () from /lib/libc.so.6 #1 0x80afd55 in fatal_error_signal () #2 0xbfffe4f4 in ?? () #3 0x4010482e in XmProcessTraversal () from /usr/X11R6/lib/libXm.so.2 #4 0x81c117d in make_dialog () #5 0x81c1645 in xm_create_dialog () #6 0x81beac3 in instantiate_widget_instance () #7 0x81beb8c in lw_make_widget () #8 0x81bf43b in lw_create_widget () #9 0x80cf288 in x_popup_dialog_box () #10 0x80c5da9 in Fpopup_dialog_box () #11 0x80b55da in funcall_recording_as () #12 0x80b99e7 in Ffuncall () #13 0x808caf6 in Fbyte_code () #14 0x80b6764 in funcall_lambda () #15 0x80b5742 in funcall_recording_as () #16 0x80b99e7 in Ffuncall () #17 0x808caf6 in Fbyte_code () #18 0x80b6764 in funcall_lambda () #19 0x80b5742 in funcall_recording_as () #20 0x80b99e7 in Ffuncall () #21 0x808caf6 in Fbyte_code () #22 0x80b6764 in funcall_lambda () #23 0x80b5742 in funcall_recording_as () #24 0x80b99e7 in Ffuncall () #25 0x808caf6 in Fbyte_code () #26 0x80b6764 in funcall_lambda () #27 0x80b5742 in funcall_recording_as () #28 0x80b99e7 in Ffuncall () #29 0x808caf6 in Fbyte_code () #30 0x80b6764 in funcall_lambda () #31 0x80b5742 in funcall_recording_as () #32 0x80b99e7 in Ffuncall () #33 0x808caf6 in Fbyte_code () #34 0x80b6764 in funcall_lambda () #35 0x80b5742 in funcall_recording_as () #36 0x80b8c2c in apply1 () #37 0x808e3e3 in Fcall_interactively () #38 0x80b54e2 in funcall_recording_as () #39 0x80b8cb9 in call1 () #40 0x80e7d91 in execute_command_event () #41 0x80e8b2d in Fdispatch_event () #42 0x80952c3 in Fcommand_loop_1 () #43 0x80954c1 in command_loop_1 () #44 0x80b29b7 in condition_case_1 () #45 0x809559c in command_loop_2 () #46 0x80b9699 in internal_catch () #47 0x80949d3 in initial_command_loop () #48 0x80ae673 in xemacs_21_0_b67_i686_redhat_linux () #49 0x80aff5d in main () Hope that helps... -- Eugene Gluzberg, IBM T.J. Watson Research Center, Java Server Performance (JASPER) Group Phone 914-784-7345, T/L 863-7345 Fax 914-784-6201, T/L Fax 863-6201 gluzberg(a)watson.ibm.com

1 participants
0 comments

Re: viper and gnus in 21.0-b67 25 years, 6 months

Colin Rafferty

Michael Kifer writes: >>>>>> "CR" == Colin Rafferty <of 06 May 1999 15:33:39 EDT> writes: CR> The problem is not that vc conflicts with other libraries. The CR> problem is that it changes the behavior of XEmacs. CR> There are many people who feel that C-x C-q means toggle-read-only, CR> not check out this file. > Is this the only thing???? > Easy to fix, I think :-) Another problem is that if you do `C-x C-f foo.c' in a directory where there is no foo.c, but there is one in the repository, vc will check a copy out for you. Some people think this feature is dangerous. -- Colin

2 participants
1 comments

Build procedure for binary kits 25 years, 6 months

Marcus Thiessel

Jason, you mentioned that were working on a procedure to do binary kits for the 21.x releases. How much will the build procedure chance compared the last build (20.4)? I would like do distribute the XEmacs 21.0.67 internally and do not want to rebuild on every machine (since there might be no C compiler). --Marcus

1 participants
0 comments

Re: A couple of bugs with 21.0.67 25 years, 6 months

Jan Vroonhof

Ian Wells <I.Wells(a)tarragon-et.co.uk> writes: > Secondly, I keep getting the somewhat unusual messages > > Buffer is read-only: #<buffer "*Completions*"> That is weird.. Can you reproduce this with xemacs -vanilla? JAn

2 participants
1 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 May 1999