May 1998 - XEmacs-Beta - XEmacs Mailing List Archives

Re: [failure] XEmacs 21.0-b40 on FreeBSD 2.2.6 26 years, 6 months

SAKIYAMA Nobuo

>>>>> In <13663.35921.908780.615253(a)lasker.worley.com> >>>>> Martin Buchholz <martin(a)xemacs.org> wrote: > Yes. XEmacs assumes an ANSI-C environment, and all the above values > can be expected to exist, even without a configure test. So all these > values should be accessed using C, and exported to lisp where > necessary. most-positive-float equals to DBL_MAX most-negative-float equals to -DBL_MAX least-positive-normalized-float equals to DBL_MIN least-negative-normalized-float equals to -DBL_MIN float-epsilon equals to DBL_EPSILON float-epsilon and float-negative-epsilon can be safely calculated in temacs. We cannot set least-positive-float and least-negative-float from <float.h> constants in the portable manner. The following C program do the similar thing to cl-float-limits in calculating least-positive-float, and can generate a C header file. -- SAKIYAMA Nobuo nobuo(a)db3.so-net.or.jp #include <stdio.h> #include <float.h> #include <signal.h> void dummy() { } main () { double x, y; signal(SIGFPE,SIG_IGN); x = DBL_MIN; while(x > 0.0){ y = x; dummy(); x/= 2.0; } printf("#define LEAST_POSITIVE_FLOAT %.*e\n",DBL_DIG, y); }

1 participants
0 comments

Re: enable-clash-detection 26 years, 6 months

Raymond Toy

Olivier Galibert <galibert(a)pobox.com> writes: > On Mon, May 18, 1998 at 11:10:21AM -0400, Raymond Toy wrote: > > No write access means you can't modify that file anyway, so no locking > > is needed? > > Wrong. File permissions and directory permissions are orthogonal. > Of course, how silly of me. I knew that. However, it does mean that xemacs can't create the ~ file, but I guess that's what %backup% in my home directory is for. (I think). I don't usually try to edit files in directories that I can't also write. Ray

1 participants
0 comments

Re: [Failure] xemacs-21.0-b40 on DU4.0D with CDE 26 years, 6 months

Hrvoje Niksic

"Kevin Oberman" <oberman(a)es.net> writes: > Loading cl-extra.el.../bin/sh: 30938 Floating exception - core dumped I think you're very close now. Comment the following code in cl-extra: ;;(defun cl-float-limits () (or most-positive-float ... (setq float-negative-epsilon (* x 2)))) ;;) -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Unspeakable horrors from outer space paralyze the living and resurrect the dead!

2 participants
1 comments

[bug] Completions buffer not splitting window! 26 years, 6 months

Hrvoje Niksic

In b40, showing the completions buffer fails to split the current window! -- Hrvoje Niksic <hniksic(a)srce.hr> | Student at FER Zagreb, Croatia --------------------------------+-------------------------------- Be nice to your kids. They'll choose your nursing home.

2 participants
1 comments

[bug] mouse tracking on horizontal scrollbars broken 26 years, 6 months

Theo Honohan

(20.4, and 21.0 betas 39 and 40) With the lucid scrollbars under X11, dragging the thumb on a horizontal scrollbar back and forth without releasing the mouse button causes the mouse pointer to drift out of place horizontally. I only noticed this problem today when playing with the new vertical dividers; I don't know how long it's been there. I'm afraid I haven't looked at the code enough (yet) to have any idea where the problem is. :-/ Theo.

1 participants
0 comments

New redisplay engine for Emacs 20.x? 26 years, 6 months

William M. Perry

As of Thu, 19 Feb 1998 13:20:54 GMT, Andrew Innes <andrewi(a)harlequin.co.uk> wrote to the emacs-nt list... >Last autumn, I did some profiling of the redisplay engine to try and >identify the major bottlenecks (which isn't terribly relevant any more, as >Emacs will soon have a brand new redisplay engine). However, I also >compared the performance of 20.2 with 19.34.6, out of curiosity. [...] >Anyway, since a new redisplay engine has already been written, most of >this discussion is now moot. The new engine has been designed from >scratch to work well on pixel-oriented displays, and should avoid at least >some of the inefficiencies of the old engine because of that. It also >supports proportionally spaced fonts, and mixing fonts of different >heights and widths, so is a major improvement in that regard too. Is he talking about the XEmacs engine? Or did they go back and totally reimplement everything yet again? -Bill P.

1 participants
0 comments

[Patch] Re: [failure] XEmacs 21.0-b40 on FreeBSD 2.2.6 26 years, 6 months

Kazuyuki IENAGA

> > Signal handling is a fragile mix of system and libc state. If the > > system thinks that a signal (say SIGFPE) isn't handled while the libc > > thinks it is (after starting a dumped executable that was handling it) > > I don't really know what will happen. > > Right. Dumping sucks in many ways. There's plenty of confusion in > the source too. Hmmm, there's no crew who saves sinking FreeBSD. Here's my adhoc & dirty patch for the problem, for the time being. I'm not sure that the problem is FreeBSD specific or not. The code is still working around 12 hours. 1998-05-19 Kazuyuki IENAGA <ienaga(a)jsys.co.jp> * alloc.c: (make_float) Avoids FPE when dumping xemacs, not using signal handler. This code should be removed when the real problem is cleared.

1 participants
0 comments

[OK] 21.0 "Saanen" XEmacs Lucid (beta40) on sparc-sun-solaris2.5.1 26 years, 6 months

Raymond Toy

>From a full tar of everything, b40 builds and runs just fine. > XEmacs Build Report as generated > by build-report-version 1.35 follows: > Contents of /apps/public/XEmacs/Beta/src/xemacs-21.0-b40/Installation: > (Output from most recent run of ./configure)

1 participants
0 comments

Re: enable-clash-detection 26 years, 6 months

Raymond Toy

Paul Bibilo <peb(a)delcam.com> writes: > Jan Vroonhof writes: > > > > Please guys, could you read the patch again. The new clash detection > > does NOT use a global locking directory. It makes a symlink in the > > same directory as the file is. > > > What happens if you don't have write access to the directory ? No write access means you can't modify that file anyway, so no locking is needed? Ray

2 participants
1 comments

Re: is `-name' functional? 26 years, 6 months

Greg Klanderman

>>>>> "OG" == Olivier Galibert <galibert(a)pobox.com> writes: OG> OG> On Mon, May 18, 1998 at 12:23:00PM +0200, Hrvoje Niksic wrote: >> And who said I was using Emacs*blah? I use `XEmacs*blah'. Does that >> make a difference? OG> OG> No. "Emacs" and "XEmacs" are application classes, xemacs is the OG> application name. -name sets the application name. There is no OG> standard way to choose the application class. Right, as far as I can tell XEmacs is behaving correctly. It would be quite easy to add a -class argument (just set Vx_emacs_application_class to build_string() of the class) but I'm not certain we'd want that. greg

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