January 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Paul Bibilo

Richard Coleman writes: > > Also, my understanding is that 21.0 is the main part of the tree > and 21.2 is a branch. Is there any chance of eventually flipping > this, so that the developmental sources are always the main line > of the tree? > I would also like to see this. -- Paul Bibilo, Delcam plc, | Tel: +44 121 766 5544 Talbot Way, Small Heath, Birmingham, | Fax: +44 121 766 5511 England, B10 0HJ. _____|_____ ICBM-mail: 52 17N 1 30W #include <disclaimer.h> | BLAT FOOP |

2 participants
1 comments

Problems building 21.0.61 for Win95 26 years

Lamont L. Dozier, Jr.

Hey folks, I'm using Visual C++ 5.0 professional, and every time that I attempt to build the XEmacs distro for Windows 95 (native version), I keep ending up with no executable file! Attached below is my output file. Can anyone make heads or tails of this before I strangle my Pentium II? TIA! Lamont -- ...and STILL as Smooth as L! ------------------------------------------------------------------------ lamont.dozier(a)erols.com http://www.erols.com/lamont.dozier "The Lord God has given Me the tongue of the learned, That I should know how to speak a word in season to him that is weary" Isaiah 50:4, NKJV . . . fade to LIGHT. C:\xemacs\xemacs-21.0.61\nt>nmake install -f xemacs.mak HAVE_XPM=1 XPM_DIR="C:\xemacs\libs\xpm-3.4k" HAVE_PNG=1 PNG_DIR="C:\xemacs\libs\libpng-1.0.2" ZLIB_DIR="C:\xemacs\libs\zlib" HAVE_GIF=1 ------------------------------------------------ XEmacs 21.0-b61 "Poitou61" configured for "i386-pc-win32". Installation directory is "c:\Program Files\XEmacs\XEmacs-21.0-b61". 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 native GUI. Compiling in support for XPM images. Compiling in support for GIF images. Compiling in support for PNG images. Compiling in support for toolbars. Compiling in support for dialogs. Compiling in support for native sounds. Compiling in fast dired implementation. ------------------------------------------------ OS: XEmacs 21.0-b61 \"Poitou61\" configured for ^`i386-pc-win32^'. Where should the build process find the source code? C:\\xemacs\\xemacs-21.0.61\\nt What compiler should XEmacs be built with? ＠cl -nologo What window system should XEmacs use? MS Windows lastfile.c link.exe -lib -nologo -out:obj\lastfile.lib obj\lastfile.obj console-msw.c device-msw.c event-msw.c frame-msw.c glyphs-msw.c ..\src\glyphs-msw.c(1589) : warning C4146: unary minus operator applied to unsigned type, result still unsigned menubar-msw.c objects-msw.c redisplay-msw.c scrollbar-msw.c select-msw.c dired-msw.c D:\DEVSTUDIO\VC\INCLUDE\direct.h(158) : warning C4030: first formal parameter list longer than the second list toolbar.c toolbar-msw.c dialog.c dialog-msw.c dgif_lib.c gif_io.c ..\src\gif_io.c(118) : warning C4013: 'close' undefined; assuming extern returning int abbrev.c alloc.c alloca.c blocktype.c buffer.c bytecode.c callint.c callproc.c casefiddle.c casetab.c chartab.c cmdloop.c cmds.c console-stream.c console.c data.c ..\src\data.c(778) : warning C4244: '=' : conversion from 'unsigned long ' to 'unsigned char ', possible loss of data device.c dired.c doc.c doprnt.c dragdrop.c dynarr.c editfns.c ..\src\editfns.c(858) : warning C4013: 'getcwd' undefined; assuming extern returning int ..\src\editfns.c(858) : warning C4047: '=' : 'char *' differs in levels of indirection from 'int ' elhash.c emacs.c eval.c event-stream.c events.c extents.c faces.c file-coding.c fileio.c filelock.c filemode.c ..\src\filemode.c(82) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\filemode.c(83) : warning C4761: integral size mismatch in argument; conversion supplied ..\src\filemode.c(84) : warning C4761: integral size mismatch in argument; conversion supplied floatfns.c fns.c font-lock.c frame.c free-hook.c general.c glyphs.c glyphs-eimage.c gmalloc.c gui.c hash.c indent.c imgproc.c insdel.c intl.c keymap.c line-number.c ..\src\line-number.c(297) : warning C4146: unary minus operator applied to unsigned type, result still unsigned lread.c lstream.c macros.c menubar.c marker.c md5.c minibuf.c nt.c ntheap.c ntplay.c ntproc.c objects.c opaque.c print.c process.c process-nt.c profile.c pure.c rangetab.c realpath.c redisplay-output.c redisplay.c regex.c scrollbar.c search.c signal.c sound.c specifier.c strftime.c symbols.c syntax.c sysdep.c tparam.c undo.c unexnt.c ..\src\unexnt.c(579) : warning C4101: 'bss_data' : unreferenced local variable vm-limit.c widget.c window.c link.exe ＠C:\WINDOWS\TEMP\nma40831. bscmake -nologo -o..\src\temacs.bsc ＠bscmake.tmp copy Installation.el ..\lisp 1 file(s) copied set EMACSBOOTSTRAPLOADPATH=..\lisp ..\src\temacs.exe -batch -l ..\src\..\lisp\update-elc.el cd ..\src set EMACSBOOTSTRAPLOADPATH=..\lisp ..\src\temacs.exe -batch -l ..\src\..\lisp\loadup.el dump Loading ..\src\..\lisp\update-elc.el... Loading very-early-lisp... (1684) Loading find-paths.el... (10464) Loading packages.el... (18800) Loading setup-paths.el... (3988) Loading dump-paths.el... (0) Loading c:\xemacs\xemacs-21.0.61\nt\../lisp/dumped-lisp.el... (64) Loading ..\src\..\lisp\loadup.el... Using load-path (..\lisp) Loading very-early-lisp... (1684) Loading c:\xemacs\xemacs-21.0.61\src\../lisp/dumped-lisp.el... (108) Loading c:\xemacs\xemacs-21.0.61\lisp\backquote.elc... (2500) Loading c:\xemacs\xemacs-21.0.61\lisp\bytecomp-runtime.elc... (3720) Loading c:\xemacs\xemacs-21.0.61\lisp\Installation.el...*** Error in XEmacs initialization (wrong-number-of-arguments setq 3) *** Backtrace really-early-error-handler((wrong-number-of-arguments setq 3)) (setq Installation-string ^ " \nOS: \nXEmacs 21.0-b61 \"Poitou61\" configured for ^`i386-pc-win32^'. \nWhere should the build process find the source code? \nC:\\xemacs\\xemacs-21.0.61\\nt \nWhat compiler should XEmacs be built with? \n＠cl -nologo \nWhat window system should XEmacs use? \nMS Windows \n^") ) # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load("c:\\xemacs\\xemacs-21.0.61\\lisp\\Installation.el") (prog1 (load full-path) (garbage-collect)) ) (if full-path (prog1 (load full-path) (garbage-collect)) (external-debugging-output (format "\nLoad file %s: not found\n" file)) nil) ) # bind (full-path) (let ((full-path ...)) (if full-path (prog1 ... ...) (external-debugging-output ...) nil)) ) # bind (file) pureload("Installation.el") (or (pureload file) (progn (external-debugging-output "Fatal error during load, aborting") (kill-emacs 1))) ) (while (setq file (car files)) (or (pureload file) (progn ... ...)) (setq files (cdr files))) ) # bind (file files) (let ((files preloaded-file-list) file) (while (setq file ...) (or ... ...) (setq files ...)) (if (not ...) (progn ... ...)) (fmakunbound (quote pureload))) ) (lambda nil (setq load-path (split-path ...)) (external-debugging-output (format "\nUsing load-path %s" load-path)) (buffer-disable-undo (get-buffer "*scratch*")) (load "very-early-lisp" nil t) (let (...) (setq load-path ...)) (setq load-warn-when-source-newer t load-warn-when-source-only t) (defun pureload (file) (let ... ...)) (load (concat default-directory "../lisp/dumped-lisp.el")) (let (... file) (while ... ... ...) (if ... ...) (fmakunbound ...)) (packages-load-package-dumped-lisps late-package-load-path))() # (unwind-protect ...) call-with-condition-handler(really-early-error-handler (lambda nil (setq load-path (split-path ...)) (external-debugging-output (format "\nUsing load-path %s" load-path)) (buffer-disable-undo (get-buffer "*scratch*")) (load "very-early-lisp" nil t) (let (...) (setq load-path ...)) (setq load-warn-when-source-newer t load-warn-when-source-only t) (defun pureload (file) (let ... ...)) (load (concat default-directory "../lisp/dumped-lisp.el")) (let (... file) (while ... ... ...) (if ... ...) (fmakunbound ...)) (packages-load-package-dumped-lisps late-package-load-path))) # bind (current-load-list) # (unwind-protect ...) # bind (load-file-name) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) # (unwind-protect ...) load("..\\src\\..\\lisp\\loadup.el") # (condition-case ... . error) # (catch top-level ...) *** Killing XEmacs Installing in c:\Program Files\XEmacs\XEmacs-21.0-b61 ... 1 File(s) copied 1 File(s) copied 7 File(s) copied 1 file(s) copied 1 file(s) copied File not found - ..\src\xemacs.exe 0 file(s) copied 1 file(s) copied 360 File(s) copied 119 File(s) copied 374 File(s) copied Making skeleton package tree in c:\Program Files\XEmacs ... 1 File(s) copied 1 File(s) copied 1 File(s) copied C:\xemacs\xemacs-21.0.61\nt>

1 participants
1 comments

Re: [PATCH] x-symbol should have a _real_ binary package 26 years

Christoph Wedler

For anyone interested, X-Symbol is now (Version 3.2a, package 1.04) a real binary package, i.e., there is no need to create fonts and set the font path -- thanks to Jim Radford. http://www.fmi.uni-passau.de/~wedler/x-symbol/ I managed to keep the binary package as small as before (em... 2.2MB, 430k compressed) by not including all sizes of foreign fonts into the binary distribution (i.e., only those sizes which are supported by my own font). There is still the source distribution for more bdf files... >>>>>"JR" == Jim Radford <radford(a)robby.caltech.edu> writes: JR> Since it seems that directories are not listed in the MANIFEST we JR> could, when removing a package, just remove even if not empty any JR> directories that are listed in the MANIFEST. Since this is not yet supported, etc/x-symbol/bin/ is not yet mentioned in the MANIFEST. - Christoph Changes in X-Symbol 3.2a (package 1.04) --------------------------------------- * Package X-Symbol is really a proper XEmacs package: no need to create fonts and to set the font path. With XEmacs/no-Mule, I still recommend to create the executables, though (type `M-x x-symbol-exec-create'). * New functions used for interaction with Emacs package `comint'. This is necessary for new token language "Isabelle symbol", to be distributed with Emacs package ProofGeneral (http://www.dcs.ed.ac.uk/home/proofgen/). * New characters used for token languages "TeX macro" and "Isabelle symbol". * Minor changes. Manual changes.

1 participants
0 comments

Re: XEmacs 21 /vs./ my keyboard: I want my DEL back 26 years

Hrvoje Niksic

Martin Buchholz <martin(a)xemacs.org> writes: > This is pretty good. I congratulate the implementors (not sure who: > Jan Vroonhof, Hrvoje Niksic and Gary Foster?) Glynn Clements and Gary Foster, in alphabetic order. Jan and yourself did great work on x-compose, if I remember correctly.

1 participants
0 comments

Correction (Re: 21.0 vs 21.2) 26 years

Tor Arntsen

On Jan 4, 16:12, I wrote: > xemacs `cvs -q -n update | grep 'C ' | cut -d" " -f1` That should be -f2 of course.. - Tor

1 participants
0 comments

mega-package rather than sumo tarball 26 years

Richard Coleman

I was thinking that when 21.0 is released, it might be better to have a mega-package (union of all common binary packages) rather than a sumo tarball. This would accomplish the same things as sumo tarball (helping those admins on large multi-user systems) while making it clear that there is a package system working in the background. Also, updates to core XEmacs and mega-package could be made separately. It might make sense to update the mega-package once a month, regardless of new XEmacs release. It might even be possible to write a script that combines the list of common packages into a mega-package on the first of every month. Just a thought. -- Richard Coleman coleman(a)math.gatech.edu

1 participants
0 comments

[Success] 21.0 "Poitou61" XEmacs Lucid (beta61) on i686-pc-linux 26 years

Hayashi Tanaka

Patched up from beta60. Fine. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /home/tanaka/src/xemacs-21.0.61/Installation: > (Output from most recent run of ./configure) # Mr.Steve and Mr.Martin, can you tell us your visit plan in Japan? # Probably beta-testers in Japan will have a welcome party for # you. :-)

1 participants
0 comments

progress guages 26 years

Andy Piper

This patch implements the progress guage widget. andy 1999-01-03 Andy Piper <andy(a)xemacs.org> * glyphs.h: add Q_percent and Qprogress. * glyphs-widget.c (image_instantiator_format_create_glyphs_widget): add progress guages. (syms_of_glyphs_widget): new keyword :percent. * glyphs-msw.c: implement glyph progress guages. (mswindows_progress_instantiate): new function. (mswindows_progress_set_property): new function. set the position of a progress guage. (image_instantiator_format_create_glyphs_mswindows): add progress guages. (vars_of_glyphs_mswindows): provide progress guages. --------------------------------------------------------------------------- " .sigs are like your face - rarely seen by you and uglier than you think" Dr Andy Piper, Technical Architect, Parallax Solutions Ltd mail: andyp(a)parallax.co.uk web: www.parallax.co.uk/~andyp

2 participants
2 comments

Re: mailing list for commit messages 26 years

Didier Verna

SL Baur writes: >> I had asked this a while ago and seen no answer. sb> That list has been up for a *long*[1] time. sb> Footnotes: [1] Since 2-May-1998. Geeze. Remember my request for a new mailing cvs-related list last month ? It triggered a dozen messages. Well, this xemacs-cvs thing is just about /all/ I wanted :-/ Why didn't anybody understood me ?! -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19

1 participants
0 comments

Re: XEmacs 21.0.60 core dumps on FreeBSD 2.2.6 26 years

SL Baur

Richard Coleman <coleman(a)math.gatech.edu> writes in xemacs-beta(a)xemacs.org: ... > Configuring with `./configure --cflags="-O3 -fno-caller-saves"' fixed > the problem. So I guess it's a compiler problem. Yup. Kyle identified that one long, long ago. > I'm using gcc 2.7.2.1 (which is the default compiler on FreeBSD 2.2.6). > But I think newer versions of FreeBSD are also using this version of gcc. > So, I'm afraid this might be a common situation. It's long passed the FAQ threshold. The solution is documented, very poorly albeit, in PROBLEMS.

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