May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

bug in src/Makefile.in EXTW_LINK() 25 years, 11 months

Colin Rafferty

Hi- I have been gone for a while, but now I'm back. I'm at a new job, where we use XEmacs external widgets for our applications. 20.4 external widget doesn't compile frame-x.c, but the fix was simple, and I see that the change is in 21.0-b41. On the other hand, src/Makefile.in (lines 229--248) has a #define construct for EXTW_LINK(). This is in both 20.4 and 21.0-b41. This function-style #define does not work, since on line 70, there is a `#define NOT_C_CODE', and I think that this makes function macros fail. Anyway, this is easily seen by looking in the generated src/Makefile (given a configure --external-widget). I am not sure what the best way to fix this is. In order to build, I have an ugly hack, but I don't want other people to see it. Can someone give me a hand with this? I would really like to have this fixed officially. Thanks a lot. -- Colin

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Jan Vroonhof

Hrvoje Niksic <hniksic(a)srce.hr> writes: > For the same reason you can't place .cshrc somewhere in your standard > path. The anology doesn't work as the loadpaths are computed before .emacs/init.el is loaded. Jan

1 participants
0 comments

Re: `make-mswindows-device' crashes Cygwin32 21.0B41 25 years, 11 months

Paul Stodghill

> Works for me. > > andy Argh. Can anyone reproduce my crash???? -- Paul Stodghill <stodghil(a)cs.cornell.edu> http://www.cs.cornell.edu/stodghil/

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > Hrvoje Niksic <hniksic(a)srce.hr> writes: > > > Yes yes yes! Agreed 100%. > > > > -> .xemacs-packages/ for personal packages > > Why not .xemacs/packages ? Yes, `.xemacs/packages' is better. > > -> .xemacs/ (if exists) for init files, otherwise various ~/.foo > > files... > > I still fail to see why all these various .foo files (or there .el > equivalents) cannot be placed in the standard loadpath, For the same reason you can't place .cshrc somewhere in your standard path. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Idle RAM is the Devil's playground.

1 participants
0 comments

Re: custom-file 25 years, 11 months

Hrvoje Niksic

Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: > P.S. This IS all 21.1 stuff we are talking about is it? 21.0 will > unfortunately have its customizations still in .emacs? Most likely, yes. -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- - Now what did we learn from this? - I learned what my liver looks like!

1 participants
0 comments

RE: QNX port problems 25 years, 11 months

Sean MacLennan

> -----Original Message----- > From: SL Baur [SMTP:steve＠xemacs.org] > Sent: Tuesday, May 26, 1998 10:54 PM > To: xemacs-beta(a)xemacs.org > Subject: Re: QNX port problems > <snip> > Um, at least in my case, none of your attachments are very useful for > identifying a problem. Please just send the Installation file > generated by configure (M-x describe-installation). > I had to edit the config.h and makefile heavily after running configure, but I can post the installation file tonight. > The code above is one place where the pointer tag bits are being > diddled with. You are apparently using the system malloc (using the > old GNU Malloc distributed with XEmacs might be easier and it might > not). > I'll try it. > Have you tried building with -DUSE_MINIMAL_TAGBITS? The System malloc > > on Linux (the new GNU malloc) has a tendency to return pointers which > can collide with the usual Lisp tagbits. Check the documentation for > malloc and make sure that it does not use mmap. If it does, you will > have to arrange to have it turned off while XEmacs is dumping or you > will lose. See the code guarded by `#ifdef DOUG_LEA_MALLOC' for clues > > on how to do this with one implementation. > The configure had -gung-ho and this caused no end of grief. I did not try MINIMAL_TAGBITS by itself. Thanks for the hints, I'll give it another go tonight. Sean

1 participants
0 comments

Re: Sounds -- .au, .wav, or both? 25 years, 11 months

Raymond Toy

Andy Piper <andyp(a)parallax.co.uk> writes: > At 03:54 PM 5/27/98 +0400, Kirill M. Katsnelson wrote: > >Some time ago, Andy Piper wrote... > >|+ > >| At 12:13 AM 5/24/98 -0700, SL Baur wrote: > >| >If we need both, it will definitely have to be a package and we'll > >| >have to upgrade the sound playing code to have lists of valid > >| >extensions so that `play-sound-file' can Do The Right Thing and either > >| >play "im_so_happy.au" or "im_so_happy.wav" as the situation warrants. > >| > >| What's the outcome of this? > > > >As far as I understand this. On Windows, PlaySound API does not play > >.au files, wavs only. On other platforms, there are APIs as simple to > >use as PlaySound, which do not care about wavs, au only. > > > >Am I correct? > > I think so. Although I think linux understands both. So we need to convert > the .au's to .wav's and ship both? Unfortunately, the NAS code only handles .au's and not .wav's. It would be nice if XEmacs NAS code did. (NAS itself does support .wav's except the ADPCM ones.) Ray

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Didier Verna

sperber(a)informatik.uni-tuebingen.de (Michael Sperber [Mr. Preprocessor]) writes: > [Chuckle ...] Actually, the official location for the late packages > is .../lib/xemacs/xemacs-packages. (You don't know that because the > documentation hasn't been written yet.) Guhh! Disgusting! Since we're under an `xemacs' directory, what sort of packages could we have appart from *xemacs* packages ?! This xemacs- prefix sounds quite meaningless to me. --Didier

1 participants
0 comments

3d object face patch 25 years, 11 months

Andy Piper

This is my 3d-object (was widget) face patch without the controversial default setting that Kyle hates so much. Hey, with this the whole modeline is set to the bg pixmap of the default face under mswindows - so even Kyle might approve :) andy 1998-05-27 Andy Piper <andyp(a)parallax.co.uk> * faces.c: create a new 3d_object_face, make modeline and vertical_divider faces fallback to this rather than the default. 1998-05-27 Andy Piper <andyp(a)parallax.co.uk> * msw-faces.el: set 3d-object face rather than modeline. Specifiy faces as specfier defaults. * package-get.el: don't use package-admin-add-single-file-package. --------------------------------------------------------------------------- " .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

1 participants
0 comments

Re: .emacs vs .xemacs vs .xemacs.el vs...? 25 years, 11 months

Greg Klanderman

>>>>> "Jan" == Jan Vroonhof <vroonhof(a)math.ethz.ch> writes: Jan> Jan> Hrvoje Niksic <hniksic(a)srce.hr> writes: >> Yes yes yes! Agreed 100%. >> -> .xemacs-packages/ for personal packages Jan> Jan> Why not .xemacs/packages ? There is no need to have two directories Yes! That's how I've been configuring for ages.

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 May 1998