June 1998 - XEmacs-Beta - XEmacs Mailing List Archives

RE: [Exceedingly Groovy] 21.0 "Toggenburg" XEmacs Lucid on alpha- dec-osf4.0 26 years, 5 months

Reggie Perry

Oops. I guess I should have explicitly mentioned it. If you look at my message that I sent out Sunday, you will notice that I used this configure statement in my build: ./configure --cflags='-std -g3 -O3 -tune host' Using -std1, which enforces strict ANSI, blows chunks in a real bad way. :-( DEC^H^H^H COMPAQ's Digital Unix compiler group has stated that the default will become "-std" in a future release. Currently the default is -std0. -Reggie -----Original Message----- From: Andrew J Cosgriff [mailto:ajc＠bing.wattle.id.au] Sent: Wednesday, June 24, 1998 5:58 PM To: xemacs-beta(a)xemacs.org Subject: Re: [Exceedingly Groovy] 21.0 "Toggenburg" XEmacs Lucid on alpha-dec-osf4.0 >>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: Martin> That (questionable) part only gets used if __STDC__ is Martin> undefined. Try ``cc -std'' instead. If this works, we should Martin> make sure that -std is used by default on DU cc invocations. Martin> The C standard's been out for 10 years! checking for socket... yes checking for netinet/in.h... yes checking for arpa/inet.h... yes Defining HAVE_SOCKETS we have a winner ! -- Andrew J Cosgriff <ajc(a)bing.wattle.id.au> exterminate all rational thought ! kingdom xylitol paranoia thousand boy

1 participants
0 comments

Re: [Exceedingly Groovy] 21.0 "Toggenburg" XEmacs Lucid on alpha-dec-osf4.0 26 years, 5 months

Andrew J Cosgriff

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: Martin> That (questionable) part only gets used if __STDC__ is Martin> undefined. Try ``cc -std'' instead. If this works, we should Martin> make sure that -std is used by default on DU cc invocations. Martin> The C standard's been out for 10 years! checking for socket... yes checking for netinet/in.h... yes checking for arpa/inet.h... yes Defining HAVE_SOCKETS we have a winner ! -- Andrew J Cosgriff <ajc(a)bing.wattle.id.au> exterminate all rational thought ! kingdom xylitol paranoia thousand boy

1 participants
0 comments

Re: Web maintainer 26 years, 5 months

Andrew J Cosgriff

>>>>> "mt" == Marcus Thiessel <thiessel(a)hpbbse.bbn.hp.com> writes: >> Who is maintaining our web space? Some things in the beta/ tree >> are embarrassingly outdated, e.g. the next beta info. Also, the >> Future Work page should be updated now and then, at least to remove >> the stuff that has actually been done, like "Add a way to resize >> horizontally split windows with the mouse." mt> Well, I did the last updates on the web. Unfortunately, I am a mt> little bit short of time at the moment. (It is embarrassing, at mt> least for me!) I will add the next beta info as soon as I can. mt> For the future work page I would like to have some assistance mt> since I am not sure was actually has been done. I did the last round of updates to the future work pages, back when I also had some free time...these days, i've hardly had time to keep up with the 21.0 betas, apart from my recent burst :( for the future work page, I was thinking the other day of trying to make it a bit more self-maintaining, so that every few months I don't have to ask everyone "which of these things have been done ?", because people can add and remove things as they get done. What do people think of, using something like WILMA[1] for this ? Thanks, Andrew Footnotes: [1] http://rtoo.cbd.net.au/wilma/ -- Andrew J Cosgriff <ajc(a)bing.wattle.id.au> exterminate all rational thought ! tango cars microwave fire lasers

2 participants
1 comments

Re: [Exceedingly Groovy] 21.0 "Toggenburg" XEmacs Lucid on alpha-dec-osf4.0 26 years, 5 months

Hrvoje Niksic

Andrew J Cosgriff <ajc(a)bing.wattle.id.au> writes: > >>>>> "ajc" == Andrew J Cosgriff <ajc(a)bing.wattle.id.au> writes: > > ajc> Not only can I build without --gung-ho, but > ajc> open-network-stream-internal has reappeared, letting Gnus work again. > > ...of course, I may have spoken too soon on the second point. Have you tried inserting debugging printf's at various places in temacs, so that we see when the function disappears exactly? The debugging printf should look like this (untested): printf ("open-network-stream-internal %s\n", !NILP (Ffboundp (intern ("open-network-stream-internal"))) ? "ok" : "MISSING!"); -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- The end of the world is coming... SAVE YOUR BUFFERS!

3 participants
2 comments

Re: [Found?] Re: Xkb-Extensions and XEmacs 26 years, 5 months

Martin Buchholz

>>>>> "C" == Christian Kirsch <ck(a)held.mind.de> writes: C> On Tue, Jun 23, 1998 at 07:16:17PM +0200, vroonhof(a)math.ethz.ch wrote: >> I just found that under an old XEmacs 20.4 (no Mule, Motif) I have >> lying aroung I can reproduce this, but not under 21.1-Mule-XIMMotif. >> I set some breakpoints (unfortunately this not a debug compile) and I >> think I found it. >> C> Yup. It works ok with xim=motif/mule, and doesn't work with C> xim=xlib/no mule -- I could reproduce this with Linux here. xim currently requires mule. C> This is the only change I made, but IIRC it inflates the binary. And I C> don't really see the point: Why should one use a Motif input method C> and Mule, if X provides all the necessary functionality by itself? It's historical. I added all of the input method handling stuff specifically to support Japanese on Solaris with Motif. For them there is no choice but to use mule. You are correct that non-mule XEmacs should do a better job of supporting Latin-1 properly. That will require a major code reorg that won't happen till 21.1 at the earliest. In the meantime, you could always put Multi_key on a key of its own using xmodmap. Then x-compose.el should work properly. Or simply, (define-key function-key-map [your key sequence here] 'compose-map) should also work. Martin

2 participants
1 comments

Re: anyone understand ediff crockishness? 26 years, 5 months

Adrian Aichner

>>>>> "Martin" == Martin Buchholz <martin(a)xemacs.org> writes: >>>>> "Andy" == Andy Piper <andyp(a)parallax.co.uk> writes: Andy> Now I can't even byte compile this because of the .3 and .1 - I get errors Martin> Those should certainly work. Martin> Is LISP_FLOAT_TYPE not #defined? Martin> Does (+ .3 .1) work? Works for me in 21.0-b46, natively built on WinNTp3/VC5.0 with (compile "nmake -f xemacs.mak HAVE_MSW=1 \ PATH_PACKAGEPATH=\"c:/export/home/tmp/packages-21.0\" HAVE_XPM=1 \ XPM_DIR=\"c:\\export\\home\\tmp\\xpm-3.4k\"") run as xemacs -no-init-file -no-site-file Adrian Martin> Does 0.3 and 0.1 work instead? Martin> Martin -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

[great] 21.0 "Toggenburg" XEmacs Lucid on i686-pc-linux 26 years, 5 months

Colin Rafferty

Just downloaded to my new Linux box. Compile is much faster on a P333 with 128M of memory. Minor problems with old makeinfo, but everything is great. As usual, only packages are 20.4, but I'm thinking of actually installing all the packages here at home. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /usr/local/src/xemacs-21.0-b46/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: EFS 1.16 bug: FAILS to work with XEmacs-21.0-b46 on Windows NT 26 years, 5 months

Colin Rafferty

Adrian Aichner writes: > Gruss bug team: > Please honor value of `directory-sep-char' instead of using hard-coded > "/" throughout the EFS package. By the way, `expand-file-name' is the best way to create file names. This way, there is no concatenation needed. Also, `file-name-as-directory' is also a useful function. -- Colin

1 participants
0 comments

Is it legal info syntax to have multiple *menu in one node? 26 years, 5 months

Adrian Aichner

Hello Info-nauts! makeinfo 1.68 accepts it, but `Info-validate' fails in info.info for the following node produced from info.texi ＠node Help-M, Help-Adv, Help-^L, Getting Started The problem is an example *menu entry followed by a real ＠menu ... ＠end menu which becomes the second *menu in the info file. Any help would improve my upcoming unidiff against 21.0-b46/man. Best, Adrian -- Adrian Aichner Applications Engineer Teradyne GmbH Semiconductor Test Group Telephone +49/89/41861(0)-208 Dingolfinger Strasse 2 Fax +49/89/41861-217 D-81673 MUENCHEN E-mail aichner(a)ecf.teradyne.com

1 participants
0 comments

Re: package-get-base props 26 years, 5 months

Oliver Graf

Pete Ware <ware(a)cis.ohio-state.edu> writes: > But that's an RPM problem, isn't it? When you convert to RPM format > you'll want to condense all the requires/provides into the actual > package names. Heck, you might even want to make them dependent on > the specific package version. Correct. This is my plan. I'm just asking some stupid questions to get some information. Still missing (the provides requires stuff seems solved): the dump flag of each package. Must a dump == t package be dumped with xemacs? Why is vm one of these packages? In the rpm version I must put vm into the main rpm (always) cause it needs to be dumped. Or is there already a method for keeping temacs to redump if a package requires it? If yes, I can put this redump easily into the post step of the rpm. If this is not supported, I either must build different main packages containing all combinations of dump packages (stupid), or will have to put all dump packages into the main RPM (is ok, cause only a few packages require a dump). Who is the main-maintainer ;-) of the package stuff. I just want to bombard him with some questions ;-) Regards, Oliver.

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