HDTenEightyP/NetNews huggingface dataset:
From: grunwald@mumble.cs.colorado.edu (Dirk Grunwald)
Subject: Re: blink-paren function
Reply-To: grunwald@foobar.cs.colorado.edu
Organization: University of Colorado at Boulder
	<47573@shamash.cdc.com> <9209150303.AA16539@thalidomide.lucid>
Date: 15 Sep 92 17:40:13

>>>>> On Mon, 14 Sep 1992 20:03:28 PDT, jwz@lucid.com (Jamie Zawinski) said:
	...
JZ> You think this because you think of the cursor as being ON a character.
JZ> You have not truly discovered The Way.  
--

So, why not make the way a little more obvious and have the cursor be
an under-caret between letters. I.e.  someting like....


now is the time for a ll good
                     ^


Or have it be the text style cursor & use another cursor for the
normal mouse cursor style. I.e.

		     v
now is the time for a|ll good
                     ^

afterall, we *are* using bitmaps.
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Thu, 10 Sep 1992 23:49:36 EDT
Date: Thu, 10 Sep 1992 20:47:46 PDT
X-Windows: Form follows malfunction.
From: jwz@lucid.com (Jamie Zawinski)
Subject: Re: 19.3 installation on decstation/ultrix4.2 with native cc
Newsgroups: alt.lucid-emacs.help
In message <9209110328.AA00345@ntu.ac.sg> Frank Siebenlist wrote:
>
> The compiler is not very descriptive, but the offending line reads:
> 
>       char* real_name = (char*)alloca (length + 2);
> 
> Not sure what is wrong with that (?), 

How about running that file through -E to see what cpp is really turning
that line in to.

> The gmalloc.c which came with 19.2 had no problem but seems "very"
> different.
> 19.3 seems to work with the 19.2 version of gmalloc.c though,
> but there must be a reason for having a new version (?),
> so I decided not to use gmalloc at all but the system's one.

GCC2 didn't like the version of gmalloc that we were using in 19.2, so I
grabbed a new version of gmalloc from the FSF v19 sources.  I don't know how
recent it is.  I don't understand why it's so unportable.  (I understand why
it's hard, but I would have expected it to be more portable than it is by
now.)  I humbly await enlightenment...

	-- Jamie
Newsgroups: alt.lucid-emacs.help
From: shankar@wpd.sgi.com (Shankar Unni)
Newsgroups: alt.lucid-emacs.help
Subject: Re: compiling lucid 19.2 on HP 7x0
Date: 11 Sep 92 22:41:41 GMT
Organization: Silicon Graphics, Inc.
X-Newsreader: Tin 1.1 PL5

Danny Bar-Dov (danny@amil.co.il) wrote:

> 1. Lucid specifies an ansi C compiler. Not having gcc - I tried to
> use HP's cc with the ansi mode flag (-Aa). After complaints about
> errors in header files (HP's) I tried the HP CC (C++) compiler -
> same problems. The c89 (another flavor of HP ansi compiler) yielded
> same results.  To make a long story short I've found out that you
> must define _INCLUDE_POSIX_SOURCE _INCLUDE_HPUX_SOURCE
> _INCLUDE_XOPEN_SOURCE to make it work.

Don't define the _INCLUDE_* names here - just define _HPUX_SOURCE.
This will cause all three names above to get defined.  This is a
standard HP FAQ.

Better still, use the flag combination "-Aa +e" (the +e flag defines
_HPUX_SOURCE and enables a couple of hp extensions to C that should
not affect any programs not using them, like asm(), etc)..

(The short version is that when you turn on -Aa in HP's C compiler,
you get a *PURE* ANSI C namespace - i.e. names that are not explicitly
in the ANSI C standard do not get defined in the headers. To get these
back, you need to define one of three possible "name-space" defines -

  _POSIX_SOURCE <= _XOPEN_SOURCE <= _HPUX_SOURCE

(i.e. each of these names is a subset of the one to its right)).

> 2. HP do not provide Xmu & Xaw include files. Also they do not
> give these libraries in both archive & shared library formats -
> one is provided only as a shared lib. the other as an archive.
> - solution - I compiled against X11R5 native distribution.

The compiled X11R4 libs and headers are on "hpcvaaz.cv.hp.com" (use
anonymous ftp - I don't remember the exact directory).

> 3. (This was partly mentioned in lucid-19.3 announcement) There are
> some mathematic functions missing under the HP platform
> some are called differently (i.e. remainder() is called fabs())
> others (i.e. atanh) are totally missing. I simply closed all these
> references with #ifndef HPUX

That's "fmod()", not "fabs()".

Jamie - very few systems have implemented the remainder() function
(which seems to be something out of IEEE754).  Could you convert all
such references to the more common ANSI C function "fmod()"?


--
Shankar Unni				E-Mail:	shankar@sgi.com
Silicon Graphics Inc.			Phone:	+1-415-390-2072
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 13:48:48 EDT
From: Tony.Bennett@East.Sun.COM (Tony E. Bennett)
Subject: minor 19.3 problems
Mailed-From: GNU Emacs or Epoch (4.2.2)
Content-Length: 1591
Date: Tue, 15 Sep 1992 17:48:49 GMT
Newsgroups: alt.lucid-emacs.help
Solaris 2.0 (svr4); SS2, compiled with the unbundled compiler.
Openwindows 3.x; olvwm 3.2

a few minor problems and questions:

    +  how do I assign a command to C-2 (control 2)
        Every thing I've tried has either complained that C-2 is
        not printable or screwed up another key defn (notably C-R !)

            (global-set-key '(control 2) 'set-mark-command)
            (global-set-key "\C-2" 'set-mark-command)

        invoking 'global-set-key' interactively does work, however.

    +  how do you move a screen, using set-screen-position and -0?
            eg: (set-screen-position screen -0 -0)
                is equivalent to 0 0.
                but -1 -1 behaves as expected.
       It's pretty clear what is happening, but how do you work around it?

    +  is it possible to have an extent within mode-line-format.
        (In epoch you can insert zones in the mode-line-format, and
        get, for example, 'Mail' in a different color)

    +  How to color the mouse pointer?
        I've tried all of the following, to no effect:

            Emacs*pointerBackgroundColor:	        Red
            Emacs*pointerForegroundColor:	        Red
            Emacs*pointerColorBackground:	        Red
            Emacs*pointerColorForeground:	        Red
            Emacs*pointerColor:	                Red

    +  How to set the screen name to the value of a variable?

            (setq my-screen-name "example")
            (x-create-screen '((name . my-screen-name)))
    
        just complains that my-screen-name is not a string.

Thanks for any help!

--tony
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Mon, 14 Sep 1992 10:11:09 EDT
From: bobhays@spss.com
Subject: Here are diffs so far to get Lucid to build on AIX
Date: Mon, 14 Sep 1992 09:10:55 CDT
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: alt.lucid-emacs.help
Here are my differences so far.

First, config.h.  This is trivial and you should know what to do here
(note that I am using Motif).

> diff config.h config.h-dist
35c35
< /* #define USE_GCC */
---
> #define USE_GCC
43c43
< #include "s/s-aix3-1.h"
---
> #include "s/s-sunos4.h"
50c50
< #include "m/m-ibmrs6000.h"
---
> #include "m/m-sparc.h"
177c177
< #define LWLIB_USES_MOTIF
---
> /* #define LWLIB_USES_MOTIF */

Second, gmalloc.c.  Here, somebody just goes and defines size_t and
then includes stdio.h later!  Someone should read something on ANSI C
I think.  Anyway, this hack is definitely dependent on AIX; now that I
think about it, a possibly better solution is to undef size_t before
entering stdio.h.

> diff gmalloc.c gmalloc.c~
49c49
< #    include <stddef.h>
---
> #include <stddef.h>
51,53c51,55
< #    undef  size_t
< #    define size_t unsigned int
< #    define _SIZE_T
---
> #undef        size_t
> #define       size_t  unsigned int
> #ifdef AIX
> #define _SIZE_T                                                                 /* Do this to keep stdio.h h
appy. */
> #endif

Third, look at sysdep.c.  You'll see AIX 3.1 isms.  You must change
HFQEIO to HFQERROR for 3.2.

> diff sysdep.c sysdep.c~
4246c4246
<   if (ioctl (0, HFQERROR, 0) < 0)
---
>   if (ioctl (0, HFQEIO, 0) < 0)
4284c4284
<   if (ioctl (0, HFQERROR, 0) != -1)
---
>   if (ioctl (0, HFQEIO, 0) != -1)
4300c4300
<   if (ioctl (0, HFQERROR, 0) < 0)
---
>   if (ioctl (0, HFQEIO, 0) < 0)

I had to turn off LD_SWITCH_SYSTEM (this should probably be done in
m-ibmrs6000.h).

I had to slightly restructure ymakefile - make is so clumsy and
non-standard.  I think the following def for obj would make things
much better for AIX at least:

obj=    dispnew.o screen.o scroll.o xdisp.o window.o \
        events.o event-alloc.o event-stream.o \
        term.o cm.o $(XOBJ) SOUND_OBJS \
        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 syntax.o font_lock.o UNEXEC mocklisp.o bytecode.o \
        process.o callproc.o $(environobj) \
        doprnt.o extents.o \
        faces.o ENERGIZE_OBJS BTLOBJS FREECHECKOBJS REALPATH_OBJS

In s-aix3-1.h, I defined NEED_REALPATH.

I had to define ENERGIZE in Imakefile in lwlib - otherwise, I had
unresolved references (naughty people:-).

In lwlib.c, I had to conditionally remove alloca.h:

#ifdef AIXV3
#else
#include <alloca.h>
#endif

I also conditioned out the signal handler for segment violation in
emacs.c so that I could get core files that had useful where info in
them (a compile time option for this would be handy).

Hope that helps.  I would really really like to get this working on
vanilla AIX 3.2.2 and hope that this info and the stack trace provided
in an earlier message (Friday) may help others complete the task.

Have fun! - Bob
Newsgroups: alt.lucid-emacs.help
From: grunwald@mumble.cs.colorado.edu (Dirk Grunwald)
Subject: can't ``xon some-host lemacs'' anymore
Reply-To: grunwald@foobar.cs.colorado.edu
Organization: University of Colorado at Boulder
Date: 11 Sep 92 16:09:18



It used to be that I could start a Lemacs on another host using the
standard 'xon' script. E.g.,


xon goober lemacs -display foobar:0

Xon does an rsh and setups up HOME and DISPLAY.  However, now lemacs
complains about needing TERM to be defined - it didn't need this
before. Is there a fix, other than having a version of 'xon' which
sets TERM as well?
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 18:34:06 EDT
Site: 
Subject: New user finds bugs?  Or maybe I'm just confused.
Date: Tue, 15 Sep 1992 18:21:39 EDT
From: jjd@spserv.bbn.com (James J Dempsey)
Newsgroups: alt.lucid-emacs.help
Every day I uncover more nifty things!

 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:

Emacs*default.attributeFont: -*-courier-medium-r-*-*-20-*-*-*-*-*-*-*
Emacs*blink-paren-off.attributeFont: -*-courier-medium-r-*-*-20-*-*-*-*-*-*-*
Emacs*blink-paren-off.attributeBackgroundPixmap: gray3
Emacs*blink-paren-on.attributeFont: -*-courier-medium-r-*-*-20-*-*-*-*-*-*-*
Emacs*blink-paren-on.attributeBackgroundPixmap: gray3

  However the set-extent-face code doesn't check to see if the new
face is the same as the old face, and you get all the extra timer
interrupts anyway, so I made blink-paren-post-command do the check.
Here is the diff:
*** /usr/local/src/lemacs/lemacs-19.3/lisp/packages/blink-paren.el	Fri Sep  4 05:42:38 1992
--- Emacs/blink-paren.el	Thu Sep 10 19:07:57 1992
***************
*** 79,84 ****
--- 79,88 ----
  (defun blink-paren-post-command ()
    (blink-paren-pre-command)
    (if (and (setq blink-paren-extent (blink-paren-make-extent))
+ 	   (not (and (face-equal 'blink-paren-on 'blink-paren-off)
+ 		     (progn
+ 		       (set-extent-face blink-paren-extent 'blink-paren-on)
+ 		       t)))
  	   (or (floatp blink-paren-timeout)
  	       (integerp blink-paren-timeout)))
        (setq blink-paren-timeout-id

This might be worth putting in the distribution with a comment about
the amount of network activity that plain blink-paren produces.

A couple of other useful font changes that I've found:

This works well for isearch, even when using hilite, etc.:
Emacs*isearch.attributeForeground: black
Emacs*isearch.attributeBackground: white
Emacs*highlight.attributeBackgroundPixmap: dimple3

This makes for quieter modelines:
Emacs*modeline.attributeForeground: white
Emacs*modeline.attributeBackground: black
Emacs*modeline.attributeBackgroundPixmap: dimple3

	../Dave
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Fri, 11 Sep 1992 01:25:34 EDT
Date: Fri, 11 Sep 1992 13:23:02 +0730
From: franks%ntu.ac.sg@lucid.com (Frank Siebenlist)
Subject: Re: 19.3 installation on decstation/ultrix4.2 with native cc
Newsgroups: alt.lucid-emacs.help
>> The compiler is not very descriptive, but the offending line reads:
>> 
>>       char* real_name = (char*)alloca (length + 2);
>> 
>> Not sure what is wrong with that (?), 
>
>How about running that file through -E to see what cpp is really turning
>that line in to.
>

yields exactly the code in the error message:
   char* real_name = (char*) __builtin_alloca (length + 2);

>GCC2 didn't like the version of gmalloc that we were using in 19.2, so I
>grabbed a new version of gmalloc from the FSF v19 sources.>

so using the 19.2 version of gmalloc would be ok (?)

>I humbly await enlightenment...

when "it" arrives, please let me know what, where, when, how...

--Frank.

x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 17:42:04 EDT
Date: Tue, 15 Sep 1992 14:39:56 PDT
X-Windows: The problem for your problem.
From: jwz@lucid.com (Jamie Zawinski)
Subject: Re: Available Minibuffer Partial Completion Packages?
	<9209152052.AA19718@thymus.synaptics>
Newsgroups: alt.lucid-emacs.help
There's a working partial-completion package in lisp/ilisp/completer.el.
This is ccm's; I don't know what the difference is between his and daveg's.
I ported daveg's as well at one point but I can't find it now.  It only
took a couple of lines.
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 21:48:45 EDT
Date: Tue, 15 Sep 1992 18:45:42 PDT
X-Windows: Power tools for power fools.
From: jwz@lucid.com (Jamie Zawinski)
Subject: Re: New user finds bugs? Or maybe I'm just confused.
	<9209160110.AA19851@thymus.synaptics>
Newsgroups: alt.lucid-emacs.help
In message <9209160110.AA19851@thymus.synaptics> Dave Gillespie wrote:
>
>>     emacs:  Alt_R (0x39) generates Mod1, which is generated by Meta.
>>     Unfortunately, this is exactly the behaviour I want.  I want Meta-x
>>     and Alt_R-x to be indistinguishable.
> 
> I agree here.  Lucid GNU Emacs needs to be more forgiving about this.
> Does anybody know why lemacs checks this while other programs don't
> seem to mind?

Other programs do arbitrarily wrong things, because Xt contains no sanity
checks.  The X keyboard model is a complete mess that allows huge numbers of
ambiguities.  Meta and Alt are not the same "key".  They are distinguishable,
and thus should have different modifiers attached to them.

If you want two keys to act as "meta" then they should both have "meta"
keysyms attached to them.  You get this message when you have a Meta keysym
attached to one and an Alt keysym attached to the other.

I believe that emacs behaves exactly the same as Xt, the only difference
being that emacs complains when it sees a keyboard configuration that doesn't
make sense, and Xt does not.

	-- Jamie
Newsgroups: alt.lucid-emacs.help
From: neumann@dec4.wu-wien.ac.AT (Gustaf Neumann)
Subject: testing ...
Organization: WU Mail/News Gateway
Date: Mon, 14 Sep 1992 22:41:35 GMT

do not appear in at.mail!

--
Gustaf Neumann          neumann@dec4.wu-wien.ac.at, neumann@awiwuw11.bitnet
Vienna University of Economics and Business Administration 
Augasse 2-6,  A-1090 Vienna, Austria		
Tel: +43 (222) 31-336 x4533  	Fax: 347-555
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Sat, 12 Sep 1992 06:01:23 EDT
Date: Sat, 12 Sep 1992 05:01:49 -0700
From: marca@ncsa.uiuc.edu (Marc Andreessen)
Subject: Lightbrite 1.1 (for Epoch and Lucid Emacs)
X-Dano: Everything I did last year was for the purpose of advancing my --
 everything I did politically -- advancing my election.  And of course
 I'm not going to say that.
                -- President George Bush, June 1989.
Newsgroups: alt.lucid-emacs.help
Lightbrite 1.1 (a source-code highlighting package) is available for
anonymous FTP from ftp.ncsa.uiuc.edu in /outgoing/marca/epoch.  It
runs (transparently) on both Epoch 4.2 and Lucid Emacs 19.3.

It hasn't been greatly stress-tested yet, so bugs surely remain; in
the tradition of c++-mode, it has an automatic bug-report generation
command specifically designed to make it extra-easy to whine and
complain :-).

Features of Lightbrite 1.1 include:

o Accurate comment highlighting.
o Regexp touchup highlighting.
o Easy specification of visual attributes of multiple 
  highlighting styles.
o Instant highlighting (as you type) with adjustable 
  responsiveness.
o Buffer size thresholds for both comment and touchup 
  highlighting.
o Use of minor mode and local keymaps.
o Re-highlight visible screen, current paragraph, current
  function, immediate area, or entire buffer.
o Large assortment of default mode-specific highlighting
  patterns.
o Automatic highlight on find-file and/or write-file.
o Special handling of mail and rmail modes.
o Works with both Epoch and Lucid Emacs transparently.

Enjoy,

Marc

--
Marc Andreessen
Software Development Group
National Center for Supercomputing Applications
marca@ncsa.uiuc.edu

x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Thu, 10 Sep 1992 09:50:46 EDT
From: danny@amil.co.il (Danny Bar-Dov)
Subject: compiling lucid 19.2 on HP 7x0
Date: Thu, 10 Sep 1992 13:50:47 GMT
Newsgroups: alt.lucid-emacs.help
I just finished compiling lemacs-19.2 on an HP 7x0 platform (hpux 8.07)
and I think some of you might be interested in some of the
problems.

1. Lucid specifies an ansi C compiler. Not having gcc - I tried to use
HP's cc with the ansi mode flag (-Aa). After complaints about errors in header
files (HP's) I tried the HP CC (C++) compiler - same problems. The c89
(another flavor of HP ansi compiler) yielded same results.
To make a long story short I've found out that you must define
_INCLUDE_POSIX_SOURCE _INCLUDE_HPUX_SOURCE _INCLUDE_XOPEN_SOURCE
to make it work.

2. HP do not provide Xmu & Xaw include files. Also they do not
give these libraries in both archive & shared library formats -
one is provided only as a shared lib. the other as an archive.
- solution - I compiled against X11R5 native distribution.

3. (This was partly mentioned in lucid-19.3 announcement) There are
some mathematic functions missing under the HP platform
some are called differently (i.e. remainder() is called fabs())
others (i.e. atanh) are totally missing. I simply closed all these
references with #ifndef HPUX

4. The last problem (woth mentioning) has to do with the
init_term function. Lucid emacs has an INVISIBLE_TERMINAL_KLUDGE
which puts in the environment (or in the MAINTAINED_ENVIRONMENT)
a definition of an "invisible" TERM & TERMCAP - and then calls
init_term recursively. init_term calls tgetent which is supposed to
read TERMCAP if defined and /etc/termcap otherwise. Only on the HP
tgetent is said to "emulate" termcap by using terminfo. It does not
read the TERMCAP variable - instead it goes directly to
/usr/lib/terminfo/i/invisible and fails the startup.
After not succeeding to fix the code I did the obvious (?)
I created the missing terminfo entry.

--
Danny.

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

Applied Materials (Israel)

Email:        danny@amil.co.il
Phone: office 972-3-499573
       home   972-3-5469625
TimeZone:     GMT+2
-------------------------------
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 21:35:31 EDT
Subject: Re: New user finds bugs? Or maybe I'm just confused.
Reply-To: daveg@synaptics.com
Date: Tue, 15 Sep 1992 18:10:00 -0700
From: daveg@thymus.synaptics.com (Dave Gillespie)
Newsgroups: alt.lucid-emacs.help
> * ^W^Y^W doesn't work

The sequence C-x C-x C-x C-x (exchange-point-and-mark, twice) can be
used to re-enable the region.  This workaround is easy enough that I'd
vote for leaving C-y the way it is, not activating the yanked region,
just to reduce screen clutter.

> * The SPACE key terminates an i-search-forward and self-inserts!!!

This sounds like an interaction with auto-fill-mode.

>     emacs:  Alt_R (0x39) generates Mod1, which is generated by Meta.
>     Unfortunately, this is exactly the behaviour I want.  I want Meta-x
>     and Alt_R-x to be indistinguishable.

I agree here.  Lucid GNU Emacs needs to be more forgiving about this.
Does anybody know why lemacs checks this while other programs don't
seem to mind?

								-- Dave
Newsgroups: alt.lucid-emacs.help
From: laufer@math.luc.edu (Konstantin Laufer)
Subject: lemacs 19.2 binary for IBM RS 6000 under AIX 3.2?
Reply-To: laufer@math.luc.edu
Fcc: +outbox
Organization: Loyola University Chicago
Date: Wed, 9 Sep 1992 00:20:41 GMT

Hello,

I need to use an RS 6000 under AIX 3.2 :-( for a class, and I was
wondering if anybody had a binary for this configuration.  Thanks,

-- 
-Konstantin [laufer@math.luc.edu]
x-gateway: rodan.UU.NET from help-lucid-emacs to alt.lucid-emacs.help; Tue, 15 Sep 1992 09:09:53 EDT
Date: Tue, 15 Sep 1992 09:09:43 EDT
From: summers@geordi.calspan.com (Mike Summers)
Subject: Wanted: Info about lucid emacs and hyperbole
Newsgroups: alt.lucid-emacs.help
Please subscribe me to this mailing list.
Newsgroups: alt.lucid-emacs.help