February 2000 - XEmacs-Beta - XEmacs Mailing List Archives

Nick V. Pakoulin

There are rumors in the net (comp.lang.lisp) about new release of ILISP. I suppose it's a nice idea to deliver newer(5.9.4) version, then currently supplied 5.8. Nick.

1 participants
0 comments

non-existent arguments to start-process (lisp/code-process.el) 24 years, 10 months

Stephen J. Turnbull

The docstrings for `start-process' and `start-process-internal' refer to non-existent arguments INCODE and OUTCODE. It looks to me from the implementation of `start-process' that these are not arguments at all, but rather are computed from `process-coding-system-alist' and bound to `coding-system-for-read' and `coding-system-for-write' respectively. The coding style is opaque; I don't have time this week to figure it out? Could somebody with a clue about this code check it? -- University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN Institute of Policy and Planning Sciences Tel/fax: +81 (298) 53-5091 _________________ _________________ _________________ _________________ What are those straight lines for? "XEmacs rules."

1 participants
0 comments

Re: start XEmacs on specific CDE desktop (PR#1138) 24 years, 10 months

Jan Vroonhof

Oliver Graf <ograf(a)rhein-zeitung.de> writes: Hi Olivier, LTNT! > I hope this brings some light into it (but I also don't know why the > interaction with CDE is as it is). Some window managers implement the starts on desk functionality by inspecting WM_COMMAND and then parsing the command line. In this case that probably means that the invisible (AppShell) window gets mapped on the correct desk, but the first frame (which doesn't have WM_COMMAND any more) is not. Basically this feature is broken-as-designed. Jan P.S. One could put WM_COMMAND on the first frame as it is mapped an then remove it, but frankly I think there are better ways to implement the functionality. (i.e. give the initial frame a special name and then tell the window manager to map that frame on the correct desk).

2 participants
1 comments

XEmacs crash when dired button at toolbar pushed 24 years, 10 months

Takuro KITAME

All is in subject. uname -a: Linux lilac 2.2.15pre2 #1 Mon Jan 17 18:40:59 JST 2000 i686 unknown In XEmacs 21.2 (beta28) "Hermes" [Lucid] (i386-debian-linux, Mule) of Mon Feb 14 2000 on lilac configured using `configure --with-sound=native --with_menubars=lucid --with_scrollbars=lucid --with_dialogs=athena --site-includes=/usr/include/db1 '--cflags=-O2 -g -Wall ' --with-x11 --extra-verbose --with-site-lisp --statedir=/var/lib --infodir=/usr/share/info/xemacs-21.2-b28 --prefix=/usr --lockdir=/var/lib/emacs/lock --error-checking=none --debug=no --const-is-losing=no --dynamic --with-gpm=no --docdir=/usr/lib/xemacs-21.2-b28/i386-debian-linux/mule/ --with-mule --with-canna=no --with-wnn=no --with-xim=xlib --with-xfs '--package-path=~/.xemacs::/usr/share/xemacs21/packages:/usr/share/xemacs21/mule-packages:/usr/share/xemacs21/site-packages' i386-debian-linux' Where should the build process find the source code? /home/debian/kitame/work/debian/xemacs21.2/xemacs21-21.2.28 What installation prefix should install use? /usr What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O2 -g -Wall Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) 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/X11R6/include Where do we find X Windows libraries? /usr/X11R6/lib Additional header files: /usr/include/db1 Athena library to link: Xaw Athena header include path: X11/Xaw Compiling in support for XAUTH. Compiling in support for XPM images. Compiling in support for PNG image handling. Compiling in support for (builtin) GIF image handling. Compiling in support for JPEG image handling. Compiling in support for TIFF image handling. Compiling in support for X-Face message headers. Compiling in native sound support. Compiling in network sound (NAS) support. Compiling in support for Enlightened Sound Daemon (ESD). Compiling in support for Berkeley DB. Compiling in support for GNU DBM. Compiling in support for LDAP. Compiling in support for ncurses. Compiling in Mule (multi-lingual) support. Compiling in XIM (X11R5+ I18N input method) support. Using raw Xlib to provide XIM support. Using XFontSet to provide bilingual menubar. Compiling in support for proper WM_COMMAND handling. Using Lucid menubars. Using Lucid scrollbars. Using Athena native widgets. Using Athena dialog boxes. Compiling in dynamic shared object module support. movemail will use "dot-locking" for locking mail spool files. Lisp backtrace follows: # (unwind-protect ...) # (catch #<INTERNAL OBJECT (XEmacs bug?) (opaque_ptr, adr=0x81a70c4) 0x81fcea0> ...) # (unwind-protect ...) # (unwind-protect ...) # bind (inhibit-quit) mouse-position() # bind (ignored) balloon-help-mouse-leave-frame-hook(#<x-frame "emacs" 0x254f>) # (condition-case ... . error) # (unwind-protect ...) read-minibuffer-internal("Dired (directory): ") byte-code("..." [recursion-depth minibuffer-depth t standard-input standard-output read-minibuffer-internal prompt] 2) # (catch exit ...) # bind (mouse-grabbed-buffer current-prefix-arg minibuffer-history-variable minibuffer-history-position minibuffer-scroll-window) # (unwind-protect ...) # bind (minibuffer-default _history_ oconfig mconfig frame buffer window oframe owindow dir default abbrev-table history readp keymap initial-contents prompt) read-from-minibuffer("Dired (directory): " "~/" #<keymap read-file-name-map size 2 0xd4a> nil file-name-history nil "~/") # bind (minibuffer-completion-table minibuffer-completion-predicate minibuffer-completion-confirm last-exact-completion insert completer initial-contents must-match default dir prompt history) read-file-name-2(file-name-history "Dired (directory): " nil "~/" nil nil read-file-name-internal) # (unwind-protect ...) # bind (rfhookfun rfcshookfun) # (unwind-protect ...) # bind (user-data dirwin filewin frame butbuff dirbuff filebuf file-p completer initial-contents must-match default dir prompt history) mouse-read-file-name-1(file-name-history "Dired (directory): " nil "~/" nil nil read-file-name-internal) # bind (completer initial-contents must-match default dir prompt history) read-file-name-1(file-name-history "Dired (directory): " nil "~/" nil nil read-file-name-internal) # bind (history initial-contents must-match default dir prompt) read-file-name("Dired (directory): " nil "~/" nil) # bind (default-directory str) dired-read-dir-and-switches("") call-interactively(dired) #<compiled-function nil "...(4)" [call-interactively toolbar-dired-function] 2 nil nil>() call-interactively(toolbar-dired) # bind (callback button event) release-and-activate-toolbar-button(#<buttonup-event button1up>) # bind (command-debug-status) call-interactively(release-and-activate-toolbar-button) # (condition-case ... . error) # (catch top-level ...) C stack trace: #0 0x4032d8d1 in kill () from /lib/libc.so.6 #1 0x80783c7 in XMapRaised () #2 0x4032d808 in sigaction () from /lib/libc.so.6 #3 0x815a192 in alarm () #4 0x8159111 in alarm () #5 0x8159151 in alarm () #6 0x815932d in alarm () #7 0x8159549 in alarm () #8 0x815959c in alarm () #9 0x81445f6 in alarm () #10 0x8144900 in alarm () #11 0x80d4121 in matherr () #12 0x80d73d8 in matherr () #13 0x807cf7e in XMapRaised () #14 0x807c2ec in XMapRaised () #15 0x807d1fa in XMapRaised () #16 0x8126b55 in alarm () #17 0x8126dc5 in alarm () #18 0x80d82f7 in matherr () #19 0x80d599e in matherr () #20 0x81073b1 in matherr () #21 0x81079cd in matherr () #22 0x81080fb in matherr () #23 0x8105f8e in matherr () #24 0x810c4c3 in matherr () #25 0x810d9ed in matherr () #26 0x810dc7a in matherr () #27 0x810d34b in matherr () #28 0x810dc7a in matherr () #29 0x810de98 in matherr () #30 0x810dffa in matherr () #31 0x810e22f in matherr () #32 0x810e47e in matherr () #33 0x80ad7da in error () #34 0x806616a in XMapRaised () #35 0x8065fe5 in XMapRaised () #36 0x807c5f6 in XMapRaised () #37 0x8065c23 in XMapRaised () #38 0x8065c47 in XMapRaised () #39 0x8065dc3 in XMapRaised () #40 0x80fc0d3 in matherr () #41 0x807e837 in error () #42 0x805c5e7 in XMapRaised () #43 0x805ed51 in XMapRaised () #44 0x807e342 in error () #45 0x807c2ec in XMapRaised () #46 0x805cf5c in XMapRaised () #47 0x805c44b in XMapRaised () #48 0x805c2af in XMapRaised () #49 0x807e944 in error () #50 0x805c5e7 in XMapRaised () #51 0x805c2af in XMapRaised () #52 0x807e944 in error () #53 0x805c5e7 in XMapRaised () #54 0x805c2af in XMapRaised () #55 0x807e944 in error () #56 0x805c5e7 in XMapRaised () #57 0x805c2af in XMapRaised () #58 0x807e944 in error () #59 0x805c5e7 in XMapRaised () #60 0x805c2af in XMapRaised () #61 0x807e944 in error () #62 0x805c5e7 in XMapRaised () #63 0x805c2af in XMapRaised () #64 0x807e4f9 in error () #65 0x805f331 in XMapRaised () #66 0x807e85d in error () #67 0x805c5e7 in XMapRaised () #68 0x805c2af in XMapRaised () #69 0x807e944 in error () #70 0x807f3a1 in error () #71 0x805f525 in XMapRaised () #72 0x807e85d in error () #73 0x805c5e7 in XMapRaised () #74 0x805c2af in XMapRaised () #75 0x807e944 in error () #76 0x80602b2 in XMapRaised () #77 0x807da0d in error () #78 0x80afdc7 in error () #79 0x80b02eb in error () #80 0x806617f in XMapRaised () #81 0x8065fe5 in XMapRaised () #82 0x807c5f6 in XMapRaised () #83 0x8065c23 in XMapRaised () #84 0x8065c47 in XMapRaised () #85 0x807c2ec in XMapRaised () #86 0x8065d8e in XMapRaised () #87 0x80792f4 in XMapRaised () #88 0x8079a70 in XMapRaised () #89 0x40327a12 in __libc_start_main () from /lib/libc.so.6 Regards. -- Takuo KITAME kitame(a)northeye.org

1 participants
0 comments

Misc fixes 24 years, 10 months

Andy Piper

This makes layout a little more sane. Still not sane enough for progress gauges for font-lock .... I strongly believe there is some GC wierdness with the subwindow stuff which is causing the reported crashes. I have an idea what it is. Stay tuned. andy 2000-02-13 Andy Piper <andy(a)xemacs.org> * redisplay.c (add_glyph_rune): call get_glyph_cachel_index here to make sure the glyph is in the cachels. * glyphs.h (struct Lisp_Image_Instance): make layout_changed a global image instance flag. (IMAGE_INSTANCE_NEEDS_LAYOUT): new macro. (XIMAGE_INSTANCE_NEEDS_LAYOUT): ditto. * glyphs.c (allocate_image_instance): set dirty bits correctly. (Fset_image_instance_property): mark layout as changed. (invalidate_glyph_geometry_maybe): mark layout as changed. (glyph_width): use new NEEDS_LAYOUT macro. (glyph_ascent): ditto. (glyph_descent): ditto. (glyph_height): ditto. (image_instance_layout): mark layout as clean after laying out. (update_subwindow): don't mark layout as clean here. * glyphs-x.h (IMAGE_INSTANCE_X_WIDGET_ID): undo C++ changes, they should no longer be needed. * glyphs-x.c (x_update_widget): sanitize asserts. (x_finalize_image_instance): sanitize assignment to widgets. * glyphs-widget.c (widget_instantiate): don't need to clear the layout flag here. -------------------------------------------------------------- Dr Andy Piper Senior Consultant Architect, BEA Systems Ltd

1 participants
0 comments

Re: [bug] (mapconcat 'identity '(1 2 3) ".") 24 years, 10 months

Karl M. Hegbloom

>>>>> "Gunnar" == Gunnar Evermann <ge204(a)eng.cam.ac.uk> writes: Gunnar> karlheg(a)bittersweet.inetarena.com (Karl M. Hegbloom) writes: >> (mapconcat 'identity '(1 2 3) ".") >> >> Returns a wta, sequencep, 1 Gunnar> I think that's a feautre. We don't concat integers (i.e.: (concat 1 2) Gunnar> signals an error). See the docstring for concat. Gunnar> you could do: (mapconcat 'int-to-string '(1 2 3) ".") That's obvious now that you point it out. >> This breaks PCL-CVS release v2_9_7, and no doubt other XEmacs software. Gunnar> I guess it breaks only FSFEmacs software :-) Nope. The same change will work there too. I'll fix it.

1 participants
0 comments

Re: New version of pcl-cvs available!! 24 years, 10 months

Jan Vroonhof

Mike Fabian <mike.fabian(a)gmx.de> writes: > Charles Waldman wrote last december in that he has already patched > pcl-cvs-2.9.7 to work with XEmacs. Maybe it is easiest to use his > patch? Here is Charles's mail from December: > > > > Greg Glander man said he was planning to do it, but didn't find the > > > time yet. Maybe you can offer to help him. > > > > > > > The reason I asked is that back in September I posted a patch I suggest you contact Charles and Greg one more time, and then when there is some concensus on what to do submit one final patch to xemacs-patches. Greg is our official pcl-cvs guy, however it seems that he is unfortunately too busy now. I would prefer if one of you managed to get at least a nod of approval from him. Jan

1 participants
0 comments

Re: Another patch status update 24 years, 10 months

Jan Vroonhof

Didier Verna <didier(a)xemacs.org> writes: > Sorry for the late reply. You know, errr, I defend my Ph.D. in two > days ... ;-) Bonne Chance! Jan

1 participants
0 comments

XEmacs Build Report for XEmacs-21.1.9 24 years, 10 months

XEmacs Build 'Bot

Hello XEmacs beta testers. I am in the process of building XEmacs-21.1.9 for distribution. I have tested the attached configuration. Have a great day! Sincerely, The XEmacs Build 'Bot (revision 2) -- uname -a: Linux zion.ne.mediaone.net 2.2.15pre7 #3 SMP Wed Feb 9 22:10:20 EST 2000 i686 unknown ./configure '--prefix=/home/acs/cvsroot' '--cflags=-O' '--with-mule' '--without-x11' '--debug=no' '--error-checking=none' XEmacs 21.1.9 "Canyonlands" configured for `i686-pc-linux'. Where should the build process find the source code? /home/acs/cvsroot/xemacs-21.1 What installation prefix should install use? /home/acs/cvsroot What operating system and machine description files should XEmacs use? `s/linux.h' and `m/intel386.h' What compiler should XEmacs be built with? gcc -O Should XEmacs use the GNU version of malloc? yes (Using Doug Lea's new malloc from the GNU C Library.) Should XEmacs use the relocating allocator for buffers? yes What window system should XEmacs use? none Compiling in native sound support. Compiling in support for Berkeley DB. Compiling in support for ncurses. Compiling in support for GPM (General Purpose Mouse). Compiling in Mule (multi-lingual) support. Compiling in DLL support. movemail will use "dot-locking" for locking mail spool files. Using Lisp_Objects with minimal tagbits.

1 participants
0 comments

find-dired.el (was: New Sumo Tarballs of packages uploaded) 24 years, 10 months

Mike Fabian

Andreas Jaeger <aj(a)suse.de> writes: > I've uploaded a number of new packages and corresponding tarballs to > ftp.xemacs.org/pub/xemacs/packages. [...] > What is _not_ in there (yet): [...] > - Your favorite package that you always use your own copy from FSF > 20.4/20.5/pre-releease for instead of our version (volunteer > needed) [...] `find-dired.el' or something similar seems not to be in the XEmacs packages, therefore I sometimes use the find-dired.el which comes with FSF Emacs 20.5a. A small patch is necessary to make it work with XEmacs: > Feel free to send patches to update these to xemacs-patches(a)xemacs.org. Maybe this could be included in future releases of the packages? If it is inconvenient for you to retrieve the FSF-version of find-dired.el to apply the patch, I can send it by email. It is fairly small, only 8424 Bytes. -- Mike Fabian <mike.fabian(a)gmx.de> <mike(a)nozomi.rhein-neckar.de>

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