December 1999 - XEmacs-Beta - XEmacs Mailing List Archives

Re: -b20 and -b22 are leaking tab widgets 24 years, 11 months

Karl Kleinpaste

Andy Piper <andy(a)xemacs.org> writes: > Ok, I think I've got it. The clip window wasn't being deleted because it > wasn't recognised as a valid lw widget. Yes, that seems to fix the tab leakage. XEmacs running Gnus seems to stabilize around 17 first-level children for me, which can rise quite a way during reading until garbage collection, and then regularly drop back down to 17 or 18. And the minimal "C-x 2 C-x 0" test case is taken care of, too, of course. Many thanx.

1 participants
0 comments

Re: -b20 and -b22 are leaking tab widgets 24 years, 11 months

Karl Kleinpaste

Andy Piper <andy(a)xemacs.org> writes: > It only happens when you garbage collect. Does the count go down then? No. Oh, I see part of what's happening... The 2nd level subwindow children (grandchildren) of the overall window are garbage-collected, but the 1st level children are not. Doing repetitious "C-x 2 C-x 0" to knock up the count a ways, I then garbage collect, and the subwindow children go away. But the top-level child count keeps going up. [1656] [16:16:34] beaver:~> xwininfo -tree | grep child 1 child: 14 children: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: [1656] [16:16:45] beaver:~> xwininfo -tree | grep child 1 child: 14 children: 1 child: 1 child: 1 child: 1 child: [1656] [16:17:01] beaver:~> xwininfo -tree | grep child 1 child: 18 children: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: 1 child: [1656] [16:17:11] beaver:~> xwininfo -tree | grep child 1 child: 18 children: 1 child: 1 child: 1 child: 1 child: --karl

2 participants
1 comments

NT native Build Failure for 21.2-b23 24 years, 11 months

Adrian Aichner

Looks like something is wrong with the latest change to ../src/s/windowsnt.h I am investigating Adrian cd d:\tmp\21.2\xemacs\nt\ nmake /f xemacs.mak 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" all Compilation started at Tue Dec 07 23:57:19 1999 Microsoft (R) Program Maintenance Utility Version 6.00.8168.0 Copyright (C) Microsoft Corp 1988-1998. All rights reserved. Creating ..\lib-src\config.values -------------------------------------------------------------------- OS: Windows_NT XEmacs 21.2-b23 \"Hebe\" configured for `i586-pc-win32'. Building XEmacs in \"d:\\tmp\\21.2\\xemacs\\nt\". Using compiler \"cl -nologo -W3 -Od -Zi\". Installing XEmacs in \"c:\\XEmacs\\XEmacs-21.2-b23\". 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. Compiling in extra debug checks. XEmacs will be slow! -------------------------------------------------------------------- copy config.h ..\src 1 file(s) copied. copy Emacs.ad.h ..\src 1 file(s) copied. copy paths.h ..\src 1 file(s) copied. lastfile.c link.exe -lib -nologo -out:..\nt\obj\lastfile.lib ..\nt\obj\lastfile.obj cd ..\lib-src make-docfile.c .\../src/s/windowsnt.h(128) : error C2061: syntax error : identifier 'Vdirectory_sep_char' .\../src/s/windowsnt.h(128) : error C2059: syntax error : ';' NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. Compilation exited abnormally with code 2 at Tue Dec 07 23:57:22

1 participants
0 comments

Re: unexelf on irix (kinda digest) 24 years, 11 months

Colin Rafferty

Max Matveev writes: > First off all, my appologies - I've been a bit busy with "another" > open-source project recently, so I'd try to reply to everybody at once > now. > Jan Vroonhof writes: > :> Max Matveev <makc(a)sgi.com> writes: > :> > :> What exactly was wrong? > :> > Assumption that .bss section should be outside the PT_LOADable > :> > segment. On IRIX with version 6.2 and above, .bss (or .sbss, if it's > :> > present) is inside the 'data' segment. This would fail the test which > :> > was used to find a segment to grow and cover new heap. Instead of this > :> > assumption, I created another one - on IRIX the segment to grow should > :> > start below .bss and it's address should extent above the end of > :> > .bss. Once thise segment is identified, it's grown to accomodate the > :> > new heap and new zero-length .bss section is added at the end of > :> > data2. > :> > :> Ok thanks for writing this, it would be nice to have this comment > :> verbatim in unexelfsgi.c > Am I right to assume that Colin is doing it? Yes and no. I tried working on this earlier, but but the patch I had did not apply cleanly, and after applying it by hand, I did not get it to build (using MIPSpro Compilers: Version 7.2.1.3m). I am going to be away for a week, and will have no time to work on it. >From a different message, it appears as though Gunnar got something to work. Maybe you (Max) can write a Changelog and split your patch into its two logical components. -- Colin

1 participants
0 comments

Making thingatp.el official instead of thing.el [Re: Please Vote on Proposals] 24 years, 11 months

Jan Vroonhof

[Io moved to =beta] Hrvoje Niksic <hniksic(a)iskon.hr> writes: > We have several options. > > a) Implement the "thingapt" API in terms of `thing.el' so that > programs just work. This would be in the spirit of fsf-compat. > (Although the analogy doesn't fully hold water. It's listed just > for completeness.) > > b) Proclaim `thing.el' obsolete and replace it with `thingapt.el'. > This has the problem of losing backward compatibility in a way that > would set Kyle on your shoulders, clawing at your spine. > > c) Proclaim `thing.el' obsolete and `thingapt.el' its follower. > Provide clear instructions on how to change all programs, and keep > `thing.el' in a "compatibility" package (not `fsf-compat', but > `old-compat'.) This is an option only if FSF's `thingapt.el' > really is better than `thing.el'. > > d) The same as c), but implement `thing.el' API in terms of > `thingapt.el' for compatibility. > > Which one do you think should apply? Well currently the only thing in our package tree that uses thing.el is mode-motion+.el (this even uses some internals, there are some ugly tricks to reduce cons'ing). So we could rewrite that and do d). However we could also simply consider thing.el part of mode-motion and be done with it. I don't think browse-url is that much better than thing.el and/or vice versa. browse-url's only claim to fame is URL support. Most packages seem to use their own at-point stuff. I thing browse-url using thing-at-point is a new trend. I think the lazy option would be e) let the two coexist. Maybe stick a comment in thing.el that it is depreciated. I don't think it is even worth it doing a) Jan

1 participants
0 comments

Re: xemacs-21.2.23 "Hebe" is released 24 years, 11 months

William M. Perry

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > wmperry(a)aventail.com (William M. Perry) writes: > > > > I'm hoping that 21.2.24 will be released once the current Irix or > > > Windows problems are declared fixed. > > > > Uhm, define 'released' please. :) > > Show up on ftp.xemacs.org? When I see 'released' I think 'non-beta'. Please say that isn't so. -Bill P.

1 participants
0 comments

Re: Running packages "in place" 24 years, 11 months

Didier Verna

Hrvoje Niksic wrote: > Is it possible to run packages "in place", the same way XEmacs can be > run in place? AFAIK, you can't because the CVS directory architecture is different from what the package system expects. I run xemacs in place, but I install the packages. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / EPITA / LRDE mailto:didier＠epita.fr /_/ / /_/ / /__ / 14-16 rue Voltaire Tel. +33 (1) 44 08 01 77 94276 Kremlin-Bicêtre cedex Fax. +33 (1) 44 08 01 99

1 participants
0 comments

Re: Running packages "in place" 24 years, 11 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)iskon.hr> writes: > Is it possible to run packages "in place", the same way XEmacs can be > run in place? Yes. But not in the way you mean. > The packages I use are always in `~/work/emacs/xemacs-packages/'. I > tell that to XEmacs by using the `--package-path=~/.../xemacs-packages' > switch to configure. I do about the same. Only I make a symlink from xemacs-packages package tree to xemacs-packages in the build tree so that XEmacs automatically pics them up when run "in place". Like it used to do with the "site-lisp" directory. > Now, I'd like to check out packages and use them in place, so that > `cvs update' automatically updates the sources I actually use. Is > that possible? If so, what do I need to do? The CVS packages contain > apparently weird directories like `oa/', `os/', `comm/', etc. The layout is a pain. What you could do (I used this for Gnus) is change the make install such that it doesn't copy but makes symlinks. Then it works fairly well. VC is even smart enough to see (when you do M-x find-library) that you are visiting a file that is symlinked to a CVS file. Jan

1 participants
0 comments

Re: xemacs-21.2.23 "Hebe" is released 24 years, 11 months

Hrvoje Niksic

wmperry(a)aventail.com (William M. Perry) writes: > > I'm hoping that 21.2.24 will be released once the current Irix or > > Windows problems are declared fixed. > > Uhm, define 'released' please. :) Show up on ftp.xemacs.org?

1 participants
0 comments

Re: xemacs-21.2.23 "Hebe" is released 24 years, 11 months

Norbert Koch

Martin Buchholz <martin(a)xemacs.org> writes: Hi! On WinNT, I get the following error (and, sorry, don't have the time to look into it): buffer.c ..\src\buffer.c(2789) : error C2224: left of '.gu' must have struct/union type ..\src\buffer.c(2803) : error C2224: left of '.gu' must have struct/union type NMAKE : fatal error U1077: 'cl' : return code '0x2' Stop. Norbert.

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