HDTenEightyP/NetNews huggingface dataset:
From: frain@cis.ksu.edu (Jerry Frain)
Newsgroups: alt.lucid-emacs.bug
Subject: Re: isearch-mode missing defconsts
Date: 13 Sep 92 19:58:08 GMT
Organization: Kansas State University
NNTP-Posting-Host: draconis.cis.ksu.edu

Hamish.Macdonald@x400gate.bnr.ca (Hamish Macdonald) writes:

> >>>>> On 11 Sep 92 16:47:39 GMT,
> >>>>> frain@cis.ksu.edu (Jerry Frain) wrote:

> Jerry> To make a long story short, here's a patch to add the missing
> Jerry> defconsts to isearch-mode.el.

> Um, it's all very well to add these constants back in, but they aren't
> *used* anywhere.

Evidently they *are* used somewhere, or vm (the version distributed
with Lucid 19.3) would not have barfed on the incremental search (i.e.
vm-isearch-forward), complaining that search-exit-char was not defined.

Granted, now that I understand the problem, it is not directly a
problem with Lucid Emacs, but due to vm not yet being updated to use
the new isearch-mode.

> The isearch mode in 19.3 is a new one, written by Daniel LaLiberte.
> In this, isearch is a minor mode, so If you want to change the
> characters, you change the isearch-mode-map.  Check
> lisp/prim/isearch-mode.el for details.

Vm uses the search-exit-char variable explicitly (disbelievers may
check the vm-search.el file), changing isearch-mode-map won't help in
this instance.

  --Jerry Frain, frain@cis.ksu.edu
Newsgroups: alt.lucid-emacs.bug
From: jsparkes@bnr.ca (Jeff Sparkes)
Subject: Re: Lucid Emacs 19.3 released
Organization: Bell-Northern Research, Ottawa
Date: Thu, 10 Sep 1992 15:25:17 GMT


jwz>I haven't made diffs, because they would be really huge, and I still don't
jwz>know a truly painless way to make diffs of an emacs source tree.

Have you tried gnu diff and "diff -rcN"?  The -N flags does a diff of
new files as if a zero size old one existed, and patches just fine.
--
--
Jeff Sparkes jsparkes@bnr.ca	Bell-Northern Research, Ottawa (613)765-2503
"For better gas mileage, do not drive with the parking brake on."
  - paraphrased from the owners manual of my Integra.
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Tue, 15 Sep 1992 20:53:48 EDT
Date: Tue, 15 Sep 1992 18:53:34 -0600
From: eeide@asylum.cs.utah.edu (Eric Eide)
Subject: Some Floats Aren't Readable
Newsgroups: alt.lucid-emacs.bug
When I eval 0.4, Lucid GNU Emacs 19.3 prints .4 -- but .4 isn't a readable
float.  Either .4 should be readable or Lucid should print the float 0.4 as
0.4.

-------------------------------------------------------------------------------
Eric Eide          |          University of Utah Department of Computer Science
eeide@cs.utah.edu  | Buddhist to hot dog vendor: "Make me one with everything."
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Mon, 14 Sep 1992 16:11:30 EDT
Date: 14 Sep 1992 16:10:25 -0500
From: "Eric L. Schott" <ELS@icf.hrb.com>
Subject: x-set-point-and-insert-selection
X-Vms-To: IN%"bug-lucid-emacs@lucid.com"
Mime-Version: 1.0
Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
Content-Transfer-Encoding: 7BIT
Newsgroups: alt.lucid-emacs.bug
x-set-point-and-insert-selection (defaults to button2) seems to have
changed from 19.2 to 19.3.  With 19.3, use the mouse to select a
region, then use the middle button to insert that selection in the same
window, but away from the selection.  The new behavior seems to
extend the selection to the click point, then insert the new, larger
selection.  Was this change from 19.2 (which did not extend the
selection) intentional?

---
Eric L. Schott,    HRB Systems, Inc.    814/238-4311     els@icf.hrb.com
  "As we acquire more knowledge, things do not become more comprehensible
   but more mysterious."                  Albert Schweitzer, "Paris Notes"
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Thu, 10 Sep 1992 01:07:08 EDT
From: max@overdrive.nj.nec.com (Maximilian Ott)
Date: Wed, 9 Sep 1992 20:09:57 EDT
Subject: Two problems with 19.3
Newsgroups: alt.lucid-emacs.bug
1) Missing lib file

I just installed 19.3 and tried to run it "out of the box" using the
provided binaries. However "emacsserver" is looking for 

	ld.so: liblucidx.so.2: not found

which I can't find anywhere.

2) Selecting files with mouse

There are also some funny problems with selecting files with the mouse
(a great new feature). It occurs when you have have file names
selected (those things happen with three button mice. Why can't we
stick with select on one and a location sensitive menu on the other.
But that would make live too easy :)). I even got lemacs to core dump
on one occasion:

#0  0x4a14 in pixel_to_glyph_translation () at dispnew.c:1758
#1  0x15f0c in event_pixel_translation () at events.c:488
#2  0x15f80 in Fevent_window () at events.c:549
#3  0x37bf8 in Fkey_binding () at keymap.c:1383
#4  0x189b8 in command_builder_find_leaf () at event-stream.c:1114
#5  0x1905c in compose_command () at event-stream.c:1399
#6  0x18400 in dispatch_event_internal () at event-stream.c:963
#7  0x1981c in Fdispatch_event () at event-stream.c:1710
#8  0x33bbc in command_loop_1 () at keyboard.c:457
#9  0x5c548 in internal_condition_case () at eval.c:979
#10 0x33840 in command_loop_2 () at keyboard.c:384
#11 0x5bfc8 in internal_catch () at eval.c:798
#12 0x337ec in command_loop () at keyboard.c:358
#13 0x33320 in recursive_edit_1 () at keyboard.c:211
#14 0x33428 in Frecursive_edit () at keyboard.c:238
#15 0x32e04 in main () at emacs.c:420

I think I had a whole row selected in the *completion window*. I know
you shouldn't do it, but ...

Otherwise it looks great. (Will I ever get used to NOT use the Esc key
in isearch?)

max
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Mon, 14 Sep 1992 03:23:17 EDT
Date: Mon, 14 Sep 1992 09:22:45 +0200
From: h.b.furuseth%usit.uio.no@lucid.com
Subject: Re: Loss of functionality in 19.3 isearch
Newsgroups: alt.lucid-emacs.bug
Right, but please try to make such changes in a way that would work on
GNU emacs too:

(fset 'isearch-ding
      (if (boundp 'facep)		; Lucid emacs
    	  'ding)
	'(lambda (&optional arg ignore) (ding arg)))

..

     (isearch-ding nil 'isearch-quit)


Hallvard
Newsgroups: alt.lucid-emacs.bug
From: Hamish.Macdonald@x400gate.bnr.ca (Hamish Macdonald)
Subject: Re: isearch-mode missing defconsts
Organization: Bell Northern Research
Date: Fri, 11 Sep 92 20:12:00 GMT

>>>>> On 11 Sep 92 16:47:39 GMT,
>>>>> frain@cis.ksu.edu (Jerry Frain) wrote:

Jerry> When installing v19.3, I decided to recompile all of the
Jerry> distribution elisp files, because there was a bug with vm
Jerry> (something about byte-code).

Jerry> Anyway, I discovered when using vm's incremental search, that
Jerry> some lisp constants were missing, notably "search-exit-char".
Jerry> Looking through the distribution lisp source,
Jerry> "search-exit-char" was not defined anywhere, nor is it defined
Jerry> when I do a "describe-variable".

Jerry> v19.2 had "search-exit-char" in prim/loaddefs.el, but v19.3
Jerry> loaddefs.el had a comment explaining that the isearch-mode
Jerry> defvars had been moved back to isearch-mode.el.  When I looked
Jerry> at isearch-mode.el, there was a whole section of defconsts
Jerry> missing that used to be in v19.2 loaddefs.el, which I cannot
Jerry> find in any other v19.3 lisp file.

Jerry> To make a long story short, here's a patch to add the missing
Jerry> defconsts to isearch-mode.el.

Um, it's all very well to add these constants back in, but they aren't
*used* anywhere.

The isearch mode in 19.3 is a new one, written by Daniel LaLiberte.
In this, isearch is a minor mode, so If you want to change the
characters, you change the isearch-mode-map.  Check
lisp/prim/isearch-mode.el for details.
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Fri, 11 Sep 1992 12:42:46 EDT
Date: Fri, 11 Sep 1992 08:41:28 PDT
From: devin%scylla@lucid.com (Matthieu Devin)
Subject: Re: Simple optimization for blink-paren
Newsgroups: alt.lucid-emacs.bug
In message <92Sep11.081631edt.28714@plg.uwaterloo.ca> Dave Mason wrote:
>  blink-paren is pretty neat, but it is a real network hog, so I
> thought of highlighting the paren rather than having it constantly
> change, so I tried setting the -on and -off fonts the same:

If you just want to highlight (and not blink) you can get rid of the timeout.
It would put a much lower load on the system running your emacs.
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Fri, 11 Sep 1992 17:09:21 EDT
From: bobhays@spss.com
Subject: The dbx info I promised....
Date: Fri, 11 Sep 1992 16:07:31 CDT
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: alt.lucid-emacs.help
Here is the dbx output that I said I'd post.  This is the death and
where info for the core file created when xemacs (lucid 19.3) fails
to start up on AIX 3.2.2:

segmentation violation in unnamed block $b682 at line 686 in file "gmalloc.c"
  686               next->next->prev = next;

(dbx) where
unnamed block $b682, line 686 in "gmalloc.c"
__free(ptr = warning: Unable to access address 0x201d49f8 from core
(invalid char ptr (0x201d49f8))), line 686 in "gmalloc.c"
gmalloc.free(ptr = 0x201d49f8), line 730 in "gmalloc.c"
free_widget_value(wv = 0x2015df00), line 148 in "menubar.c"
free_widget_value(wv = 0x2015dec0), line 159 in "menubar.c"
free_widget_value(wv = 0x2015dcc0), line 160 in "menubar.c"
free_widget_value(wv = 0x2015dc80), line 159 in "menubar.c"
set_screen_menubar(s = 0x201b4400, deep_p = 0), line 527 in "menubar.c"
unnamed block $b239, line 688 in "menubar.c"
update_screen_menubars(), line 688 in "menubar.c"
redisplay(), line 708 in "xdisp.c"
initialize_first_screen(), line 1074 in "xdisp.c"
Finitialize_first_screen(), line 2247 in "dispnew.c"
Ffuncall(nargs = 1, args = 0x2017bff8), line 1802 in "eval.c"
Fbyte_code(bytestr = 202269268, vector = 269378192, maxdepth = 2, 0x100278ac, 0xdeadbeef, 0xdeadbeef, 0xdeadbe
ef, 0xdeadbeef), line 428 in "bytecode.c"
unnamed block $b481, line 1418 in "eval.c"
Feval(form = 336486980, 0x4155804, 0xdeadbeef, 0x100278ac, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef), li
ne 1418 in "eval.c"
Fcondition_case(args = 337129756), line 968 in "eval.c"
Fbyte_code(bytestr = 202269104, vector = 269378036, maxdepth = 3, 0x4155804, 0x0, 0x0, 0x0, 0x0), line 582 in 
"bytecode.c"
funcall_lambda(fun = 403595672, nargs = 0, arg_vector = 0x2015cf8c), line 1969 in "eval.c"
Ffuncall(nargs = 1, args = 0x2015cf88), line 1836 in "eval.c"
Fbyte_code(bytestr = 202268104, vector = 269377044, maxdepth = 5, 0x10027b08, 0xdeadbeef, 0xdeadbeef, 0xdeadbe
ef, 0xdeadbeef), line 428 in "bytecode.c"
funcall_lambda(fun = 403594672, nargs = 0, arg_vector = (nil)), line 1969 in "eval.c"
apply_lambda(fun = 403594672, args = 68507652, eval_flag = 1, 0x10027b08, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 
0xdeadbeef), line 1900 in "eval.c"
Feval(form = 337073900, 0xdeadbeef, 0xdeadbeef, 0x10027b08, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef, 0xdeadbeef), l
ine 1441 in "eval.c"
top_level_2(), line 397 in "keyboard.c"
internal_condition_case(bfun = 0x20148974, handlers = 68507932, hfun = 0x20148968), line 1002 in "eval.c"
top_level_1(dummy = 68507652), line 406 in "keyboard.c"
internal_catch(tag = 68507912, func = 0x20148950, arg = 68507652), line 814 in "eval.c"
command_loop(), line 366 in "keyboard.c"
recursive_edit_1(), line 221 in "keyboard.c"
Frecursive_edit(), line 250 in "keyboard.c"
main(argc = 1, argv = 0x2ff7ff04, envp = 0x2ff7ff0c), line 819 in "emacs.c"

I'll think about this output Monday. :-)

Have fun! - Bob
From: grunwald@mumble.cs.colorado.edu (Dirk Grunwald)
Newsgroups: alt.lucid-emacs.help
Subject: tty 19.3
Date: 15 Sep 92 21:36:45 GMT
Reply-To: grunwald@foobar.cs.colorado.edu
Organization: University of Colorado at Boulder


I notice that 19.3 can be started on a tty but crashes quickly.  Is
this a projected fix in 19.4 - i.e. will I be able to discard 18.58?

Thanks.
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Mon, 14 Sep 1992 11:53:53 EDT
Date: Mon, 14 Sep 1992 08:52:17 PDT
From: eb%watergate@lucid.com (Eric Benson)
Subject: Re: blink-paren function
Reply-To: eb@lucid.com
Newsgroups: alt.lucid-emacs.help
That's the way it works.  Even though the cursor is *on* that
character, it's really meant to be positioned *before* that character.
Most terminals can't display a cursor between characters.
From: bjdunlop@shamash.cdc.com (Bruce Dunlop)
Newsgroups: alt.lucid-emacs.help
Subject: Re: blink-paren function
Date: 15 Sep 92 01:50:00 GMT
Distribution: usa
Organization: Control Data, Arden Hills, MN

In article <192fu4INN3j4@early-bird.think.com> barmar@think.com (Barry Margolin) writes:
>Think about how it works when you're initially typing.  After you type a
>right parenthesis, it's to the left of the cursor, and you want the

Ohhhhhhhhhhhhhh!  That's the first explanation I have gotten that made any
sense.

>the parenthesis of the one you're *about* to type, since Emacs doesn't have
>ESP yet (I think that's planned for the FSF's version, which may be why

DARN,  I was hoping that would be in lemacs 19.3.


Wouldn't it be possible to modify the behavior of blink-paren, depending on
whether you just typed in a right paren. or not?

After moving the cursor, it would be more intuitive and consistent to see
the blink match the hi-lited character.  Consistent, because then left and
right paren matching would both match (blink) the paren matching the
hi-lited character.

Thanks for the explanation.


Jim Dahlberg
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 17:49:48 EDT
Date: Tue, 15 Sep 1992 14:49:01 PDT
From: carney@igor.rational.com (Mike Carney)
Subject: IBM RS6000
Newsgroups: alt.lucid-emacs.help
I'm trying to build lemacs on an RS6000. I've looked in the
$BUILD/etc/MACHINES file, and found that the 'm-' and 's-' files
should be: m-ibmrs6000.h; s-aix3-1.h. I can't seem to find these
anywhere in the source that I have. Could you send me a copy of them
so I can build this wonderful version of emacs on my RS6000? Thanks.

--
    Michael D. Carney
    email: carney@rational.com
    phone: 408-496-3790
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Sat, 12 Sep 1992 03:21:48 EDT
Date: Sat, 12 Sep 1992 15:22:20 +0730
From: franks%ntu.ac.sg@lucid.com (Frank Siebenlist)
Subject: mouse scrolling for lemacs 19
Newsgroups: alt.lucid-emacs.help
The following few lines may make your lifes a little easier
(until we get our scrollbars....),
unless you're using hyperbole 
(in which case the interesting parts keep jumping of your screen...).

Enjoy, Frank.

-------------------------cut-here-------------------------------------------
-
;; mouse-scroll-prop.el
;; proportional mouse scrolling for lemacs-19
;;
;; add next three lines to .emacs and modify key assignment to taste:
;;(load "mouse-scroll-prop")
;;(define-key global-map '(control button2) 'mouse-scroll-up-prop)
;;(define-key global-map '(control button3) 'mouse-scroll-down-prop)

(defun mouse-scroll-up-prop (event)
  "Scrolls window up proportionally, i.e. clicked line becomes first line."
  (interactive "@event")
  (scroll-up (- (event-y event) (car (cdr (window-edges))))))

(defun mouse-scroll-down-prop (event)
  "Scrolls window down proportionally, i.e. clicked line becomes last
line."
  (interactive "@event")
  (scroll-down (- (car (cdr (cdr (cdr (window-edges))))) (event-y event)
2)))

Newsgroups: alt.lucid-emacs.help
From: daveg@thymus.synaptics.COM (Dave Gillespie)
Subject: Re: Lucid Emacs 19.3 released
Reply-To: daveg@synaptics.com
Organization: WU Mail/News Gateway
Date: Wed, 9 Sep 1992 07:40:05 GMT

> Note that ESC no longer terminates an isearch: LFD does instead.

Note that Sun's latest keyboard (the one they ship with Sparc 10's)
has dropped the LFD key.  As far as I know, HP keyboards have never
had a LFD key.  I would recommend at least making sure C-j is
accepted as well as LFD during a search.

Maybe RET would be better, *not* equivalenced to C-m.

								-- Dave
Newsgroups: alt.lucid-emacs.help
From: dmason@plg.uwaterloo.CA (Dave Mason)
Subject: RE: Simple optimization for blink-paren
Organization: WU Mail/News Gateway
Date: Fri, 11 Sep 1992 09:32:31 GMT

> From: devin%scylla@lucid.com (Matthieu Devin)
> In message <92Sep11.081631edt.28714@plg.uwaterloo.ca> Dave Mason wrote:
> >  blink-paren is pretty neat, but it is a real network hog, so I
> > thought of highlighting the paren rather than having it constantly
> > change, so I tried setting the -on and -off fonts the same:
> 
> If you just want to highlight (and not blink) you can get rid of the timeout.
> It would put a much lower load on the system running your emacs.

Unless I've done something stupid, the code I sent already does that (the
``and'' terminates with a nil value if the two faces are equal).

	../Dave
Newsgroups: alt.lucid-emacs.help
From: jwz@lucid.COM (Jamie Zawinski)
Subject: Re: paste in minibuffer (19.3)
Organization: WU Mail/News Gateway
Date: Fri, 11 Sep 1992 03:24:31 GMT

In message <hoelzle.716146448@Xenon.Stanford.EDU> Urs Hoelzle wrote:
>
> In 19.3, the middle mouse button no longer works as "paste" in the
> minibuffer. [...] Is there any way to change this back to the 19.2 behavior?

Of course, just change the binding of button2 in minibuffer-local-map back
to what it is globally.
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Sun, 6 Sep 1992 13:44:34 EDT
From: danny@amil.co.il (Danny Bar-Dov)
Subject: Lucid or not?
Date: Sun, 6 Sep 1992 17:44:35 GMT
Newsgroups: alt.lucid-emacs.help
Henrik B}kman  CSD writes:
 > What is the preferable way to check if you are running Lucid-emacs or
 > not, in an elisp-file?
 > 
 > -- 
 > ----------------------------------------------------------------------
 > Henrik Bakman           Adress: Box 520          Tel: +46 18 181044
 > System Manager                  751 20 UPPSALA   Fax: +46 18 521270
 > Computing Science Dep.          SWEDEN           Email: hb@csd.uu.se
 > Uppsala University

And once upon a time jwz wrote:
I think the easiest way to do this is

 >	(cond ((not (string-lessp emacs-version "19"))
 >	       ;; for any 19-vintage emacs
 >	       )
 >
 >	      ((not (string-lessp emacs-version "19.2"))
 >	       ;; for versions of emacs at 19.2 or above
 >	       )
 >
 >	      ((string-match "Lucid" emacs-version)
 >	       ;; for any Lucid Emacs
 >	       )
 >
 >	      ((and (string-match "Lucid" emacs-version)
 >		    (not (string-lessp emacs-version "19.2")))
 >	       ;; for lemacs 19.2 or greater, but not FSF's 19.2
 >	       ))
 >
 >But having a set of integer variables would be nice as well.  But the problem
 >with that is that Emacs 18 didn't have it, and FSF's 19 might not have it,
 >which means you'd have to use the above code or something like it anyway.
 >
 >	-- Jamie
 >

--
Danny.

-------------------------------
Dan Bar Dov

Applied Materials (Israel)

Email:        danny@amil.co.il
Phone: office 972-3-499573
       home   972-3-5469625
TimeZone:     GMT+2
-------------------------------
From: steve@gabriela.tymnet.com (Steve Sandke)
Newsgroups: alt.lucid-emacs.help
Subject: Problem compiling 19.3 with Motif
Date: 10 Sep 92 18:39:51 GMT
Organization: BT North America, San Jose, CA

I'm having problems compiling 19.3 with Motif support enabled.  Here's what
the linker tells me:

ld   -e __start -Bstatic    -L. -L./lwlib -o temacs crt0.o dispnew.o screen.o scroll.o xdisp.o window.o  events.o event-alloc.o event-stream.o  term.o cm.o xterm.o xfns.o xselect.o xutils.o event-Xt.o menubar.o play.o libsst.o  emacs.o keyboard.o macros.o keymap.o sysdep.o  buffer.o filelock.o insdel.o marker.o  minibuf.o fileio.o dired.o filemode.o  cmds.o casetab.o casefiddle.o indent.o search.o regex.o undo.o  alloc.o data.o doc.o editfns.o callint.o  eval.o floatfns.o fns.o print.o lread.o  abbrev.o sy

ntax.o font_lock.o unexec.o mocklisp.o bytecode.o  process.o callproc.o environ.o  doprnt.o extents.o faces.o elhash.o hash.o tparam.o lastfile.o gmalloc.o vm-limit.o ScreenWidget.o ColumnWidget.o EmacsShell.o sunOS-fix.o strcmp.o strcpy.o  -L/usr/demo/SOUND -laudio    ./lwlib/liblw.a -lXm -lXaw -lXext -lXt -lXmu -lX11   -ltermcap  -lg  -lm -lc
Undefined
___main
_create_debugger_p_sheet
_create_call_browser_p_sheet
_create_breaklist_p_sheet
_create_class_browser_p_sheet
_create_le_browser_p_sheet
_create_project_p_sheet
*** Error code 2
make: Fatal error: Command failed for target `temacs'

I know the problem with main is something else - I remember doing something to 
solve it in 19.2.  But the rest of the stuff is new - it's all in lwlib-Xm.c (or something
like that).  I looked in the 19.2 code, and it isn't there.

What do I do?  What am I missing?

-- 
-------------------
Steve Sandke
steve@orchid.tymnet.com

Newsgroups: alt.lucid-emacs.help
From: mcclen@advtech.uswest.com ( Chris McClenaghan)
Subject: Re: Problem compiling 19.3 with Motif
Organization: US WEST Advanced Technologies, Boulder, Colorado
Date: Fri, 11 Sep 1992 17:29:09 GMT

I had the same problem, in lwlib Imakefile define ENERGIZE, this
will/should force the compiling and linking of the modules in the
energize subdirectory. Then just relink lemacs. I'm not sure that
this is what JWZ intended, possibly some conditional compilation
would remove this need. I haven't experienced any side effects
yet.

--
Chris McClenaghan    mcclen@advtech.uswest.com
From: hb@woody.csd.uu.se (Henrik B}kman  CSD)
Newsgroups: alt.lucid-emacs.help
Subject: floating-point functions
Date: 15 Sep 1992 09:19:50 GMT
Organization: Uppsala University
Distribution: world
NNTP-Posting-Host: woody.csd.uu.se


I'am looking on some floating-point functions, especially the
missing ones in hpux, and I have some questions.

Some of the floating-point functions isn't defined for all values
and returns the special IEEE-754 value 'Nan' and on overflow they
return '+-(infinit)'. There is two C-functions, isnan() and isinf()
which you can check for this special values but I can't find any
such functions in Lucid-emacs. I wonder if there is some functions
like this in Lucid-emacs or if I haven't looked enough or if Lucid-
emacs is handling such math-errors in another way or if Lucid-emacs
doesn't handling such errors at all?

If I want to implement the missing functions what should I go for.
Fast and eaisy but with some round-errors or should I make them
return more correct values? That is, can I use already defined functions
or should I use "pure" numerical methods like Newton-Raphson and such?
(I don't want to implement them in PA-RISC assembler :-) )
 
-- 
----------------------------------------------------------------------
Henrik Bakman           Adress: Box 520          Tel: +46 18 181044
System Manager                  751 20 UPPSALA   Fax: +46 18 521270
Computing Science Dep.          SWEDEN           Email: hb@csd.uu.se
Uppsala University
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Fri, 11 Sep 1992 11:30:40 EDT
From: bobhays@spss.com
Subject: More on AIX 3.2.2 Lucid 19.3
Date: Fri, 11 Sep 1992 10:30:43 CDT
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: alt.lucid-emacs.help
The menus are activating....  I had a friend run the program (we
actually edited some text in the *scratch* buffer) and he succeeded in
using the Exit Lucid option (and no core dump there).

Just a small update....  Hope someone has some ideas....

I've kept the changes (I think) for the files I manipulated, so I will
eventually post these for general info if desired.

Have fun! - Bob
Newsgroups: alt.lucid-emacs.help