HDTenEightyP/NetNews huggingface dataset:
From: sjoerd@cwi.nl (Sjoerd Mullender)
Newsgroups: alt.lucid-emacs.bug
Subject: core dump from lucid emacs 19.4
Date: 26 Jan 93 14:46:50 GMT

The following seems to be a quick way to get a core dump from Lucid
Emacs 19.4.  Start emacs -q; edit an empty C file; use font-lock-mode;
then type four double quotes, two control-B's and a slash (that is,
produce the sequence ""/"" with the / typed last).  Emacs will then
abort, leaving a core file behind.

Here is a typescript of a short debugging session.  Emacs aborts in
find_context, on line 355.  I printed out the value of context_cache,
since that apparently has an unexpected value.  If necessary I can
provide more details about all sorts of variables.

This happened on an SGI Indigo.

Script started on Tue Jan 26 15:38:31 1993
Warning: no access to tty; thus no process control in this shell...
& dbx /usr/src/local/gnu/lemacs/src/emacs-19.4.4-Lucid core
dbx version 3.10 Jun 26 1992 18:02:24
Type 'help' for help.
Reading symbolic information of `/usr/src/local/gnu/lemacs/src/emacs-19.4.4-Lucid' . . .
Process name from core dump: emacs-19.4.4-Lucid
Process died at pc 0x5fd128 of signal : Abort
[using memory image in core]
(dbx) where
>  0 .kill.kill(0x70b, 0x6, 0x14, 0x0, 0x40f2d30, 0x3) ["sys/kill.s":14, 0x5fd124]
   1 fatal_error_signal(sig = 6) ["/tmp_mnt/meermin/rwsrc/local/gnu/lemacs-19.4/src/emacs.c":167, 0x44465c]
   2 ._kill._kill(0x70b, 0x6, 0x14, 0x0, 0x100b0000, 0x1008cd48) ["sys/_kill.s":15, 0x60a074]
   3 fatal_error_signal(sig = 1477115588) ["/tmp_mnt/meermin/rwsrc/local/gnu/lemacs-19.4/src/emacs.c":167, 0x44465c]
   4 .abort.abort(0x70b, 0x6, 0x14, 0x0, 0x6, 0x4980dc) ["abort.c":40, 0x5fc13c]
   5 <past end of a.out text>(0x70b, 0x6, 0x14, 0x0, 0xffffffff, 0xffffffff) [0x7fffb944]

warning: address 0xfffffffc for 4 bytes is not in the core file

warning: address 0xfffffffc for 4 bytes is not in the core file
(dbx) up
fatal_error_signal(sig = 6) ["/tmp_mnt/meermin/rwsrc/local/gnu/lemacs-19.4/src/emacs.c":167, 0x44465c]
(dbx) up
._kill._kill(0x70b, 0x6, 0x14, 0x0, 0x100b0000, 0x1008cd48) ["sys/_kill.s":15, 0x60a074]
(dbx) up
.raise.raise(0x70b, 0x6, 0x14, 0x0, 0x3, 0x497c20) ["sys/raise.c":19, 0x6055fc]
(dbx) up
.abort.abort(0x70b, 0x6, 0x14, 0x0, 0x100b0000, 0x10175900) ["abort.c":40, 0x5fc13c]
(dbx) up
find_context(pt = 4, end = 6) ["/tmp_mnt/meermin/rwsrc/local/gnu/lemacs-19.4/src/font_lock.c":355, 0x497c1c]
(dbx) dump
find_context(pt = 4, end = 6) ["/tmp_mnt/meermin/rwsrc/local/gnu/lemacs-19.4/src/font_lock.c":355, 0x497c1c]
prev_c = '/'
target = 5
c = '"'
(dbx) p context_cache
struct context_cache {
    start_point = 4
    end_point = 2
    buffer = 0x10175900
    context = context_string
    ccontext = ccontext_start1
    style = comment_style_none
    scontext = '"'
    depth = 0
    backslash_p = 0
} 
(dbx) quit
& 

script done on Tue Jan 26 15:39:26 1993

-- 
Sjoerd Mullender
CWI, dept. CST, Kruislaan 413, 1098 SJ Amsterdam, Netherlands
email: sjoerd@cwi.nl			fax:   +31 20 592 4199
phone: +31 20 592 4127			telex: 12571 mactr nl
Newsgroups: alt.lucid-emacs.bug
From: haydens@bullwinkle.juliet.ll.mit.edu (Hayden Schultz x3685 g42)
Subject: Re: lemacs19.4/lisp/cl.el
Reply-To: haydens@juliet.ll.mit.edu
Organization: M.I.T. Lincoln Lab - Group 42
	<HAYDENS.93Jan25215857@bullwinkle.juliet.ll.mit.edu>
Date: 25 Jan 93 22:12:09


In article <HAYDENS.93Jan25215857@bullwinkle.juliet.ll.mit.edu> haydens@bullwinkle.juliet.ll.mit.edu (Hayden Schultz x3685 g42) writes:


      I don't ever want cl.el to muck up my environment if I accidentally load
      something that tries to use it.  I won't run anything that uses cl.el.

   Does this mean that cl.el doesn't work in 19.4?

   If cl.el does work, and is merely morally corrupt, is it possible to
   disable the disabling of cl.el? I've already sold my soul to
   Completions.el, so I don't really have anything to loose.


Ok, I'm a bozo. Just renaming the bogus cl.el in the lisp dir does the
trick.

	Sheepishly,

	Hayden (haydens@ll.mit.edu)
From: matsj@Delfi.CMD.UU.SE (Mats Johnson)
Newsgroups: alt.lucid-emacs.bug
Subject: Lucid emacs 19.4 bug with vm
Date: 27 Jan 93 21:32:29 GMT
Reply-To: Mats.Johnson@CMD.UU.SE
Organization: CMD - Center for human computer studies, Uppsala University
NNTP-Posting-Host: delfi.cmd.uu.se


In the file lisp/utils/highlight-headers.el the variable
highlight-headers-regexp is sent to looking-at without checking if it
is nil. In vm the default is to make this nil, resulting in a lisp
error.
--
Mats Johnson, CMD, Uppsala University, Laegerhyddvaegen 18, S-752 37 UPPSALA
Mats.Johnson@CMD.UU.SE
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Tue, 26 Jan 1993 04:53:13 EST
Date: Tue, 26 Jan 1993 10:51:40 +0100
From: popineau%esemetz.ese-metz.fr@lucid.com
Subject: LEmacs dumps core when loading man.el
Newsgroups: alt.lucid-emacs.bug
Whenever I try to load lemacs-19.4/lisp/packages/man.el , lemacs dumps
core with the following backtrace :
Core was generated by `lemacs.orig'.
Program terminated with signal 6, Abort.
#0  0x15de08 in kill ()
(gdb) where
#0  0x15de08 in kill ()
#1  0x1637dc in abort ()
#2  0x1dcb8 in glyph_to_x_pixmap () at xterm.c:1870
#3  0x1e610 in x_write_glyphs () at xterm.c:347
#4  0x49ac in update_screen () at dispnew.c:1567
#5  0xf1e4 in redisplay () at xdisp.c:397
#6  0x18794 in Fnext_event () at event-stream.c:301
#7  0x34054 in command_loop_1 () at keyboard.c:458
#8  0x5d4b0 in condition_case_1 () at eval.c:993
#9  0x33ce4 in command_loop_2 () at keyboard.c:373
#10 0x5d320 in internal_catch () at eval.c:870
#11 0x33814 in command_loop () at keyboard.c:347
#12 0x33890 in recursive_edit_1 () at keyboard.c:206
#13 0x3397c in Frecursive_edit () at keyboard.c:232
#14 0x333f0 in main () at emacs.c:572
(gdb) 
Is it a bug ?

F. Popineau

--
e-mail: popineau@loria.loria.fr	      
        popineau@ese-metz.fr                 
voice-mail: (+33) 87-74-99-38                
surface-mail: 	Ecole Superieure d'Electricite
	      	2 rue Edouard Belin           
		F-57078 Metz Cedex 3	      
		FRANCE			      

x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Thu, 28 Jan 1993 13:33:54 EST
Date: Thu, 28 Jan 1993 10:32:37 PST
From: yonkman@hawk.css.gov (Tom Yonkman)
Subject: lemacs freezes
Reply-To: yonkman@esosun.css.gov
Newsgroups: alt.lucid-emacs.bug
lemacs freezes under the following circumstances:

running gdb with a breakpoint set.
when the breakpoint is encountered, gdb tries to load the source file,
which was not loaded prior.
The source file was write protected, being under SCCS control.

I get the usual "File is write protected" message, and then lemacs freezes,
not accepting either keyboard or mouse input.

Note: When finding a write protected file lemacs prints the "File is write
protected" message but does not bring up the file's buffer for display.  If
I redo the find, or just press <return>, the buffer is then displayed.

I am running  lemacs 19.4 on a SPARCstation 2 with SunOS 4.1.1.

--
+---------------------------------------------------------------+
| Tom Yonkman                 UUCP:      seismo!esosun!yonkman  |
| Open Systems Division       Internet:  yonkman@esosun.css.gov |
| SAIC, Mail Stop A2-F        PHONE:     (619)458-4949          |
| 10260 Campus Point Drive    FAX:       (619)458-4993          |
| San Diego, CA  92121                                          |
+---------------------------------------------------------------+

x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Mon, 25 Jan 1993 11:36:05 EST
Date: Mon, 25 Jan 1993 17:20:55 +0100
From: Guido.Bosch%loria.fr@lucid.com (Guido Bosch)
Subject: lemacs19.4/lisp/cl.el
Reply-To: bosch%loria.fr@lucid.com (Guido Bosch)
Newsgroups: alt.lucid-emacs.bug
In the Lucid Emacs 19.4 distribution (ftp'ed today), there is a file 

		lemacs19.4/lisp/cl.el 

containing 

(error "you were about to load cl.el")


What is this good for? (besides making packages that do (require 'cl)
not working anymore)

	Guido
From: neal@ctd.comsat.com (Neal Becker)
Newsgroups: alt.lucid-emacs.bug
Subject: chmod with ange-ftp gives error
Date: 22 Jan 93 16:20:22 GMT
Organization: COMSAT Labs
NNTP-Posting-Host: neal.ctd.comsat.com
X-Md4-Signature: 7a9b23d5447736e7b85922bd567da24b

When using ange-ftp when I use M for chmod I get:

  dired-check-process-checker(nil)
  dired-check-process("chmod 444" "chmod" "444" "sys")
  apply(dired-check-process "chmod 444" "chmod" "444" "sys")
  dired-do-chxxx("Mode" "chmod" chmod nil)
  dired-do-chmod(nil)
* call-interactively(dired-do-chmod)

Does anyone have a fix?

Thanks.
From: bcotton@sergei.MITRE.org (Bob Cotton)
Newsgroups: alt.lucid-emacs.bug
Subject: _vendorShellWidgetClass: mutiply defined?
Date: 22 Jan 93 20:01:19 GMT
Organization: MITRE Corp. McLean Va.


Did not see this in the PROBLEMS file.. 

When compiling 19.4 I get the following:

.........
gcc -O   -I/usr/local/X11R5/include -Demacs  -I./lwlib   -c faces.c -o faces.o
gcc -O   -I/usr/local/X11R5/include -Demacs  -I./lwlib   -c tparam.c -o tparam.o
gcc -O   -I/usr/local/X11R5/include -Demacs  -I./lwlib   -c gmalloc.c -o gmalloc.o
gcc -O   -I/usr/local/X11R5/include -Demacs  -I./lwlib   -c vm-limit.c -o vm-limit.o
gcc -O   -I/usr/local/X11R5/include -Demacs  -I./lwlib   -c ScreenWidget.c -o ScreenWidget.o
gcc   -dynamic  -L/usr/local/X11R5/lib -L. -L./lwlib   -o temacs  dispnew.o screen.o scroll.o xdi
sp.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 emacs.o keyboard.o macros.o keymap.o sysdep.o buffer.o filelock.o in
sdel.o marker.o minibuf.o fileio.o dired.o filemode.o cmds.o casetab.o casefiddle.o indent.o sear
ch.o regex.o undo.o pure.o alloc.o data.o doc.o editfns.o callint.o eval.o floatfns.o fns.o print
.o lread.o abbrev.o syntax.o font_lock.o unexsunos4.o mocklisp.o bytecode.o process.o callproc.o
environ.o elhash.o hash.o doprnt.o extents.o faces.o  tparam.o lastfile.o gmalloc.o vm-limit.o  S
creenWidget.o ColumnWidget.o EmacsShell.o sunOS-fix.o strcmp.o strcpy.o  -L/usr/demo/SOUND -laudi
o -llw -lXm   -lXaw -lXext  -lXt -lXmu -lX11     -ltermcap -lg /usr/local/lib/gcc-lib/sun4-sunos4
.1/2.3.3/libgcc.a -lm -lc
ld: /usr/local/X11R5/lib/libXaw.sa.5.0(sharedlib.o): _vendorShellWidgetClass: multiply defined
collect: /usr/bin/ld returned 2 exit status
make[1]: *** [temacs] Error 1
make: *** [doall] Error 1
xcalibur [286]

Any clues?

Reading specs from /usr/local/lib/gcc-lib/sun4-sunos4.1/2.3.3/specs
gcc version 2.3.3
Sun4 4.1.3
Motif 1.2.1

Trying to use the Motif widgets..

Thanks, 
Bob
From: toivo@ucs.uwa.OZ.AU (Toivo Pedaste)
Newsgroups: alt.lucid-emacs.bug
Subject: Ultrix and lemacs19.4 (hanging)
Date: 26 Jan 1993 07:33:20 GMT
Organization: The University of Western Australia
NNTP-Posting-Host: sage.ucs.uwa.edu.au
X-Newsreader: NN version 6.4.19 #1

I have a couple of problems with lemacs hanging under ULTRIX 4.2a

1)
	lemacs hangs when I use emacsclient. This is a problem with
reading from a remote process, for some reason it doesn't use a
non-blocking read. This occured in 19.3 also and I got a fix
off the net for it, but I've lost the old sources and I cann't
remember what it was. Can anyone assist.

2)
	lemacs hanging on when pasteing in a selection from an
xterm. This alse happened in 19.3, it didn't seem to happen to
anyone else so it may be something peculiar about my X setup.
Anyway if it does happen to anyone else  my solution was :

at line 1016 in xselect.c replace 

      result =
	XGetWindowProperty (display, window, property,
			    offset/4, buffer_size/4,
			    (delete_p ? True : False),
			    AnyPropertyType,
			    actual_type_ret, actual_format_ret,
			    actual_size_ret, &bytes_remaining, &tmp_data);

with

      result =
	XGetWindowProperty (display, window, property,
			    offset/4, buffer_size/4,
			     False,
			    AnyPropertyType,
			    actual_type_ret, actual_format_ret,
			    actual_size_ret, &bytes_remaining, &tmp_data);
      if (delete_p) XDeleteProperty (display, window, property);
--
------------------------------------------------------------------
 Toivo Pedaste                        Email:  toivo@ucs.uwa.edu.au
 University Computing Services,       Phone:  +61 9 380 2605
 University of Western Australia      Fax:    +61 9 380 1014
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Wed, 27 Jan 1993 17:56:58 EST
From: dror@FibHaifa.com (Dror Caspi)
Subject: copy/paste inconsistency with clipboard and active regions
Reply-To: dror@FibHaifa.com
Date: Wed, 27 Jan 1993 22:56:59 GMT
Newsgroups: alt.lucid-emacs.bug
>> Date: Wed, 27 Jan 93 15:31:13 +0800
>> From: franks%ntrc.ntu.ac.sg@lucid.com (Frank Siebenlist)
>> 
>> Also I seem to loose my active region as soon as my popup-menu pops away,
>> this in contrast with the use of the menubar-menu which let me keep the active region 
>> after it pops up and away. (I apopogize for my English...)

Use (set 'zmacs-region-stays 't) in the popup function.


Dror

x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Mon, 25 Jan 1993 13:55:31 EST
Date: Mon, 25 Jan 1993 10:54:47 PST
X-Windows: The joke that kills.
From: jwz@lucid.com (Jamie Zawinski)
Subject: Re: 19.4 problems (mode-motion and gmhist-app)
Newsgroups: alt.lucid-emacs.bug
> (2) The tree dired package, along with ghmist, used to work with lemacs
> 19.3.  I got the freshest version, and tried to load it, in both 19.3 and
> 19.4.  It worked in 19.3, but not in 19.4 - the error on load of
> ghmist-app.el was something like "keep-lines: too complex".  I also tried
> with the provided "lisp/dired" package - same results.  Anybody out there
> know what's going wrong?

Gmhist is obsolete; a replacement is built in now.  I sent out a message about
this a few days ago.  In the version of dired we distribute, gmhist will not
be automatically loaded, so if it's getting loaded, it's because you're doing
it explicitly.

	-- Jamie
Newsgroups: alt.lucid-emacs.bug
From: me@SAIL.Stanford.EDU (Martin Frost)
Subject: documentation of changes in Lucid Emacs from version 18
Reply-To: me@CS.Stanford.EDU
Organization: Computer Science Department, Stanford University.
Distribution: alt
Date: 24 Jan 93 12:48:11

I have noticed that there are a lot of "little" changes in Lucid Emacs from
version 18, changes that will surprise (if not annoy) many users.  Some of
these are new key definitions (like M-o), some may be replaced key
definitions, and some are slight changes to effects of functions (and thus
their keys) such as next-line/C-n.

For instance, I'm still trying to get used to what C-o does if fill-prefix
is not the empty string.  Of course, I probably like most of the little
changes, although I'm sure I have not discovered most of them.

The problem is that there doesn't seem to be a list of these changes, so
there is no way for a system administrator to warn users of things to look
out for (or take advantage of) when suggesting that they change from
version 18 to Lucid version 19.  Of course, there is documentation for many
major new facilities, but these little mods (many probably being favorites
of Jamie's, and most probably being good things) aren't always documented.

If Jamie doesn't have time to record these changes, that leaves it to
others to discover and maybe document them.  Perhaps someone has already
done some of that documenting?

One question is: Are there lots and lots of these things or only a few.  My
guess is that there are only a moderate number of added/replaced keys but
probably a number of slight changes to functions.  (I'm not talking about
invisible function changes but those that are noticeable to a normal user.)
--
Martin Frost		Computer Science Department, Computer Facilities
Systems Programmer	Stanford University, Stanford, CA  94305-2140
me@CS.Stanford.EDU	(or mfrost@stanford.bitnet)
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Wed, 27 Jan 1993 17:46:36 EST
Date: Wed, 27 Jan 1993 10:12:44 PST
From: Eduardo.Pelegri-Llopart@Eng.Sun.COM (Eduardo Pelegri-Llopart)
Subject: copy/paste inconsistency with clipboard and active regions
Content-Length: 334
Newsgroups: alt.lucid-emacs.bug
> If I double click or drag to make an active selection,
> then it seems that the selection is automatically copied to the clipboard.
> (19.3 shows the same behaviour.)

It is made the PRIMARY selection, not placed in the CLIPBOARD. The "problem"
is that pending-del does not model exactly the behavior of, say, textedit.

- eduardo

x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Mon, 25 Jan 1993 20:25:12 EST
Date: Mon, 25 Jan 1993 17:25:16 -0800
From: erose@leland.stanford.edu
Subject: more problems with vm in 19.4
Newsgroups: alt.lucid-emacs.bug
I installed the patches recently posted for VM.  Unfortunately it still does
not rememdy the problem.  (I patched vm-lucid and highlight-headers)

I traced it to "vm-headers-of" in the vm-message lisp file.  The
argument, "message" is being passed in ass null.  I added a test for
null to return nil, and then the problem went to the "vm-text-of"
function, with the same problem.

So, either the functions should be checking for a nil message, or it
shouldn't call the functions.  Any ideas or suggestions?

Running: Dec 5000/240 Ultrix 4.2A
Emacs: Lucid 19.4

-Eric

x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Mon, 25 Jan 1993 09:58:44 EST
Date: Mon, 25 Jan 1993 15:58:24 +0100
From: Henrik.Bakman%csd.uu.se@lucid.com (Henrik B}kman  CSD)
Subject: _vendorShellWidgetClass: mutiply defined?
X-Charset: ASCII
X-Char-Esc: 29
Newsgroups: alt.lucid-emacs.bug
>GDB 4.4, Copyright 1991 Free Software Foundation, Inc...
>(gdb) run
>Starting program: /tmp_mnt/home/bcotton/bcotton/lemacs-19.4/src/xemacs
>
>Program received signal 11, Segmentation fault
>0x122050 in _XmGetNavigability ()
>(gdb) tb
>Breakpoint 1 at 0x122050
>(gdb) where
>#0  0x122050 in _XmGetNavigability ()
>#1  0x1235e8 in _XmNewTravGraph ()
..

I got the same problem in lemacs 19.3 with motif 1.2.1. I got
a mail from Lucid about it that I should try the beta-version
of 19.4. I didn't had time to do this but the problem seems
to be there in 19.4 to :-(

You should report this to Lucid.

The Lucid-boys told me that they only had motif 1.1.4 (I think)
so there seems to be some small incompatibility problem when
changing to motif 1.2.1. Well I hope someone have time to
dig into it.

----------------------------------------------------------------------
Henrik Bakman           Adress: Box 311          Tel: +46 18 181044
System Manager                  751 05 UPPSALA   Fax: +46 18 521270
Computing Science Dep.          SWEDEN           Email: hb@csd.uu.se
Uppsala University
Newsgroups: alt.lucid-emacs.bug
From: carney@rocky.rational.com (Mike Carney)
Subject: Bug in mail mode in V19.4
Organization: Rational, Santa Clara, CA
Distribution: alt
Date: Tue, 26 Jan 1993 19:35:35 GMT


Try this:

1. M-x mail
2. move the cursor down to the message area and type a few tabs. In my
copy, this causes a core dump of lemacs.

Any ideas?

Thanks in advance
--
               '`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`
               '                                   |  `
               ' Michael D. Carney                 |  `
               ' carney@rational.com               |  `
               ' Santa Clara, CA  _   _   _+      _|_ `
               '                 /_`-'_`-'_|  \+/  0  `
               ' "You can never  \_`M'_`C'_| _<=>_//  `
               '  really *know*    `-' `-' 0/ \|/ /   `
               '  anything"                \/]\|/[    `
               '        -Heisenberg        | /_V_\    `
               '         (paraphrased)     | [] []    `
               '                           | d! !b    `
               `'`'`'``'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`'`
Newsgroups: alt.lucid-emacs.bug
Skip Koppenhaver wrote:
> 
> 2. My .emacs file explicitly loaded gmhist and gmhist-app but I got an
>    error when loading gmhist-app. Something about keep-lines being to
>    complicated for gmhist.  I commented out the loading of gmhist and
>    gmhist-app and everything was okay. What happened here?

I forgot to mention that there is now a builtin minibuffer history mechanism
which replaces gmhist.  Getting history is now the default, instead of
explicit action needing to be taken for each command.

	-- Jamie
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Sun, 24 Jan 1993 17:09:52 EST
Date: Sun, 24 Jan 1993 14:09:47 PST
X-Windows: Live the nightmare.
From: jwz@lucid.com (Jamie Zawinski)
Subject: Re: documentation of changes in Lucid Emacs from version 18
Newsgroups: alt.lucid-emacs.bug
Martin Frost wrote:
> 
> and some are slight changes to effects of functions (and thus
> their keys) such as next-line/C-n.

What has changed there?

> For instance, I'm still trying to get used to what C-o does if fill-prefix
> is not the empty string.

Actually, that bugged me a lot too...  I rebound it in my .emacs file.
Probably I should just nuke it.

> but these little mods (many probably being favorites of Jamie's, and most
> probably being good things) aren't always documented.

Actually, quite a lot of these piddling little changes were inherited from
the FSF v19 back when we were still living under the illusion that we were
working together.  Any time I've changed the behavior of something that is
user-visible, I've tried to document it in the NEWS file (I'm sure I missed
some, but I have been trying.)

> One question is: Are there lots and lots of these things or only a few.  My
> guess is that there are only a moderate number of added/replaced keys but
> probably a number of slight changes to functions.  (I'm not talking about
> invisible function changes but those that are noticeable to a normal user.)

I suspect there aren't a whole lot that haven't already made it into the NEWS
file.  If you notice any others, let me know and I'll document them there.

I haven't made a list of keybinding changes; that would be a good thing.

	-- Jamie
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Fri, 22 Jan 1993 08:50:07 EST
From: simon%lia.di.epfl.ch@lucid.com (Simon Leinen)
Subject: 19.4 problems
Date: Fri, 22 Jan 1993 13:50:08 GMT
Newsgroups: alt.lucid-emacs.bug
>   3. vm crashes when invoked, with the following trace back:
> Signalling: (wrong-type-argument stringp nil)
> 
>   looking-at(nil)
>   highlight-headers(687211 688112 t)
>   vm-highlight-headers([[#<marker at 687211 in INBOX> #<marker at 688005 in INBOX> #<marker at 688112 in INBOX> #<marker at 688499 in INBOX> nil nil <<>> nil <--] [nil nil nil nil] [nil nil nil nil nil nil nil nil nil] [nil nil nil nil nil nil nil nil nil nil nil nil "^From:" nil nil nil] nil] nil)

>   vm-preview-current-message()
>   vm-goto-message(202)
>   vm-gobble-bookmark()
>   byte-code("@p!	q\n+@\n!	qC ,	

Yes... in fact this is exactly what happened when I started VM to read
your message.  The problem is that "vm-highlighted-header-regexp" is
nil in the default setup.  If you set it to a string, such as
"^Subject:", then the error should disappear.

There should be a reasonable default value for this variable in
lisp/vm/vm-lucid.el.
-- 
Simon.
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Thu, 21 Jan 1993 05:12:22 EST
Date: Thu, 21 Jan 1993 02:12:11 PST
From: jwz@lucid.com (Jamie Zawinski)
Subject: Lucid Emacs 19.4 released
Newsgroups: alt.lucid-emacs.bug
Please excuse the previous (referenced) message.   I thought that
bug-lucid-emacs@lucid.com was read by the Lucid Emacs developers,
not, as it appears, by most of the world's Lemacs users.  (I have
reached a contact point at Lucid for the complementary issue.)

Yours, Rich Morin
rdm@cfcl.com
x-gateway: rodan.UU.NET from bug-lucid-emacs to alt.lucid-emacs.bug; Thu, 28 Jan 1993 14:49:54 EST
Date: Thu, 28 Jan 1993 11:45:57 PST
From: yonkman@hawk.css.gov (Tom Yonkman)
Subject: lemacs freezes
Reply-To: yonkman@esosun.css.gov
Newsgroups: alt.lucid-emacs.bug