HDTenEightyP/NetNews huggingface dataset:
From: rsmith@proteus.arc.nasa.gov (Roger Smith -- IAS)
Newsgroups: fj.mail-lists.x-window
Subject: Killing all clients on exit, on an X-terminal
Date: 9 Oct 92 03:21:12 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: Thu, 8 Oct 92 17:12:28 PDT
Message-Id: <9210090012.AA16280@proteus.arc.nasa.gov>

The LAST line in your .Xsession file should be something like:

exec /usr/bin/X11/xterm -title Console -font 6x10 -iconic -C -geometry 80x24+0+290 -name console -xrm "*iconGeometry:+0+521" -ls

The above line creates an ICONIFIED xterm window named "Console".
Since this window was "exec'd", when you exit this window all other
clients of that session will also die. Note also that the "-C" causes
all messages directed to the system console to go to this window...
Maybe not what you want for all situations. Include it or leave it out
to suit.
------------------------------------------------------------------
Roger Smith
Sterling Software at
NASA-Ames Research Center
rsmith@proteus.arc.nasa.gov
- 
If change is -- inevitable -- predictable -- beneficial -- 
doesn't logic demand that you be a part of it?
One man cannot summon the future. But one man can change the present!
    -- Kirk and the Alternate Spock, "Mirror, Mirror," stardate unknown
+
From: ecf_stbo@jhuvms.hcf.jhu.edu (Blabst from the Pabst...)
Newsgroups: fj.mail-lists.x-window
Subject: Re: X Under Windows NT
Date: 11 Oct 92 22:14:07 GMT
Distribution: fj
Organization: The Johns Hopkins University - HCF

Date: Fri, 9 Oct 1992 16:17:00 GMT
Message-Id: <9OCT199211172312@jhuvms.hcf.jhu.edu>
Newsgroups: comp.windows.x,comp.sys.dec

In article <1992Oct8.172513.19695@news.dfrf.nasa.gov>, todd@fred.dfrf.nasa.gov (Todd Vernon) writes...
>I realize that this discussion probably does not belong here, take a
>number and be PROCESSED by Microsoft.

And Bill Gates has been declared by fortune magazine to be the richest man
in america. Maybe you'll be lucky and be randomly picked by IBM to do something
too. Long live marketing!


Tom O'Toole - ecf_stbo@jhuvms.hcf.jhu.edu - JHUVMS system programmer 
Homewood Computing Facilities, Johns Hopkins University, Balto. Md. 21218 
>Here comes a jet ski.
>weuh weeuhh weeuhh weeuhh WEEUHH WEEUHH WEEUHH WEEUHH weeuhh weeuhh weeuhh weuh
From: song@open.dal.ca (Kim Song)
Newsgroups: fj.mail-lists.x-window
Subject: Obtaining RGB values from a Colormap
Date: 8 Oct 92 10:09:54 GMT
Distribution: fj
Organization: OPEN, Dalhousie University, Halifax, NS, Canada

Date: Mon, 5 Oct 1992 15:20:03 GMT
Message-Id: <BvnMLF.7t7@cs.dal.ca>
Newsgroups: comp.windows.x

   I have already created a colormap for a canvas, and I am trying to find
   the RGB values for that colormap given a pixel value.  The colormap is 
   defined as a part of the cms_data structure below:

   cms_data.red[MAXCOLORS];
   cms_data.green[MAXCOLORS];
   cms_data.blue[MAXCOLORS];

   I have been trying to call the function:
	XQueryColor(display, cmap, colorcell_def) where
		display is connection to an Xserver
		cmap is ID of the colormap from which RGB values are retrieved
		colorcell_def is pixel value         
   As:
	XQueryColor(display, xv_find(canvas,CMS,CMS_NAME,"Palette",NULL), pixel_value);
	"Palette" is the name I gave the colormap.

   But I keep getting the error:

   XView warning: invalid object (not a pointer), xv_get
   signal SEGV (no mapping at the fault address) in cms_set_static_colors at 0xf762ba28
   cms_set_static_colors+0x18:     ld      [%l5 + 24], %l5

   Could someone PLEASE tell me what the cms_set_static_colors error exactly means and what parameter I should be passing in as cmap or any other suggestions 
   you might have?

				Kimberley.
From: raj@gdstech.grumman.com (Rajesh Chawla)
Newsgroups: fj.mail-lists.x-window
Subject: Looking for info on SIE
Date: 15 Oct 92 08:29:37 GMT
Distribution: fj
Organization: GRUMMAN DATA SYSTEMS

Date: Mon, 12 Oct 1992 13:59:54 GMT
Message-Id: <1992Oct12.135954.7535@gdstech.grumman.com>
Newsgroups: comp.windows.x


Hi, 

I am looking for info on the imaging extension done by NCD, known as
SIE.  If anyone has any info or pointers to documentation, please let
me know.

Thanks,

-- 
==================================================================
Rajesh Chawla				2411 Dulles Corner Park
E-Mail:  raj@gdstech.grumman.com	Suite 500
Phone:	(703) 713-4170	FAX: 713-4103	Herndon VA 22071
From: lemmens@pa.twi.tudelft.nl (Kees Lemmens)
Newsgroups: fj.mail-lists.x-window
Subject: X-terminals
Date: 16 Oct 92 02:05:56 GMT
Distribution: fj
Organization: TU Delft

Date: 15 Oct 92 16:44:57 GMT
Message-Id: <1992Oct15.164457.10637@donau.et.tudelft.nl>
Newsgroups: comp.windows.x



I'm trying to compare the performance of X-terminals from different vendors, but is hard to get an
objective idea from the folders. Is there anybody who can tell we where to find a comparison of DEC,
TEKTRONIX and HP X-terminals ?
I would prefer to have the performance expressed in Xstones, but any other comparison will be welcome.

Thans in advance.

Kees Lemmens,
Techical University of Delft,
Faculty of Techn. Maths. and Informatics.
Delft.
From: mouse@thunder.mcrcim.mcgill.edu (der Mouse)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Blinking
Date: 9 Oct 92 14:03:12 GMT
Distribution: fj
Organization: McGill Research Centre for Intelligent Machines

Date: Wed, 7 Oct 92 06:21:19 GMT
Message-Id: <1992Oct7.062119.11769@thunder.mcrcim.mcgill.edu>
Newsgroups: comp.windows.x,comp.windows.x.motif,comp.windows.x.intrinsics

In article <1992Oct1.204222.13721@relay.nswc.navy.mil>, dnguyen@xobu.nswc.navy.mil (D. Nguyen) writes:

> Does any one know how to implement blinking in X ?  An obvious
> solution is just too costly.

Which obvious solution?  I see two obvious solutions: (1) redraw
periodically and (2) use read/write colormap cells and change their
contents periodically.  (1) is the only solution that's fully portable.
(2) produces much better performance, when you're using a dynamic
visual and can afford the necessary colormap cell(s).

Are you sure your "obvious solution" really is too costly?  Don't say
this until you've tried it; guesses about what is and is not too
expensive are often wrong.

There's not much else you can do and stay within the core protocol.
There may be an extension somewhere for blinking, but I don't know of
any such.

					der Mouse

			    mouse@larry.mcrcim.mcgill.edu
From: klute@tommy.informatik.uni-dortmund.de (Rainer Klute)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Imake on DEC?
Date: 14 Oct 92 09:54:15 GMT
Distribution: fj
Organization: CS Department, Dortmund University, Germany

Date: 13 Oct 92 20:28:30 GMT
Message-Id: <1bfbheINNbbe@fbi-news.Informatik.Uni-Dortmund.DE>
Newsgroups: comp.windows.x

In article <26823.9210081044@photon.phy.hw.ac.uk>,
yuri@physics.heriot-watt.ac.UK (Yuri Rzhanov) writes:
|> The problem is: I need to link some unusual libraries (like
|> libXpm.a, my own, etc.). On Sun, I defined them as LOCAL_LIBRARIES
|> and everything was fine. But on DEC, the target depends not only
|> on $(SRCS) but also on $(DEPLIBS) which are defined to be equal
|> to $(LOCAL_LIBRARIES). So every time I'm trying to build my code
|> it says just before linking stage that it doesn't know how to rebuild
|> the libraries. What should I do? Now I defined my libraries as
|> EXTRA_LIBRARIES, and it works (thanks God), but I have a feeling
|> that it's not correct.

I have some suspicion, but would like to see your Imakefile before making
any comments.

-- 
  Dipl.-Inform. Rainer Klute      klute@irb.informatik.uni-dortmund.de
  Univ. Dortmund, IRB
  Postfach 500500         |)|/    Tel.: +49 231 755-4663
D-W4600 Dortmund 50       |\|\    Fax : +49 231 755-2386
From: subbarao@nmsu.edu (Ravi Subbarao)
Newsgroups: fj.mail-lists.x-window
Subject: Need X tool like xkermit or other modem dialup apps.
Date: 7 Oct 92 07:55:37 GMT
Distribution: fj
Organization: New Mexico State University

Date: 6 Oct 92 17:27:23 GMT
Message-Id: <1992Oct6.172723.9064@nmsu.edu>
Newsgroups: comp.windows.x,comp.windows.open-look

Hello world!!


I am desperately in need of a X based tool for modem dialups.... 
Is there any tool called xkermit??

I do not read this newsgroup often. I will highly appreciate if
anyone who uses it can tell me where to get it.


Thanks!!!

-Ravi Subbarao
<subbarao@nmsu.edu>
From: eoahmad@ntuix.ntu.ac.sg (Othman Ahmad)
Newsgroups: fj.mail-lists.x-window
Subject: Re: List of XFree86 Video Boards
Date: 14 Oct 92 00:51:02 GMT
Distribution: fj
Organization: Nanyang Technological University - Singapore

Date: 13 Oct 92 02:32:01 GMT
Message-Id: <1992Oct13.023201.12211@ntuix.ntu.ac.sg>
Newsgroups: comp.unix.bsd,comp.windows.x

I have tried et4000,paradise chip set 1, trident tvga8900 chipset based
vga cards and they all work. The main problem is the varieties of clocks
supported but 25Mhz ofr 648X480 and 36Mhz for 800X600 are common for all
the chipsets. To be safe, choose 25Mhz.
	The iterlace mode selection failed for the paradise chipset so is
not advisable to be the default.

The rule of thumb is to choose the lowest clock frequency for each
mode. Delete or comment out all other higher frequencies in the VESA monitor
setting. We do not need others.

To make beginners life easier, use the lowest resolution mode, instead of
the highest first, e.g. 
mode "640x480" "800x600"

It will save a lot of head aches.



--
Othman bin Ahmad, School of EEE,
Nanyang Technological University, Singapore 2263.
Internet Email: eoahmad@ntuix.ntu.ac.sg
Bitnet Email: eoahmad@ntuvax.bitnet
From: allyn@snobol.cs.psu.edu (Barry C Allyn)
Newsgroups: fj.mail-lists.x-window
Subject: X interface builders ?
Date: 7 Oct 92 09:26:39 GMT
Distribution: fj
Organization: Penn State Computer Science

Date: 4 Oct 92 18:28:50 GMT
Message-Id: <BvM0o3.Kvr@cs.psu.edu>
Newsgroups: comp.windows.x


  What X interface builders are available via anonymous ftp?  I've tried
Dirt, but it crashes frequently on our system.  Any info would be 
appreciated.. 
 
Barry Allyn
From: dwex@mtgzfs3.att.com (David E Wexelblat)
Newsgroups: fj.mail-lists.x-window
Subject: 2nd RFD: comp.windows.x.i386unix
Date: 10 Oct 92 22:21:19 GMT
Distribution: fj
Organization: AT&T

Date: 8 Oct 92 13:35:42 GMT
Message-Id: <Bvt1rJ.LH4@uunet.uu.net>
Newsgroups: news.announce.newgroups,news.groups,comp.windows.x,comp.unix.sysv386,comp.unix.bsd,comp.os.linux,comp.os.mach,comp.unix.sys5.r4,comp.unix.sys5.r3,comp.unix.pc-clone.32bit


	Request For Discussion - comp.windows.x.i386unix, unmoderated
	------------------------------------------------------------

[ This RFD supercedes the RFD for comp.windows.x.xfree86.  Initial 
  discussions determined that the scope of that newsgroup was too limited.  
  We have expanded the charter, and hence revised the name.  The name
  choice is probably not optimal, so feel free to suggest new names ]

We propose that a new newsgroup be created to carry on discussions
related to implementations of the X Window System under Unix (and
related OSes) on Intel 3/486 hardware.  The principle free implemetation
is currently XFree86, and will represent most of the traffic in the
newsgroup.  However, the newsgroup will be used for discussions of
vendor-supplied X implementations, and 3rd-party commercial implementations
as well.

XFree86 (previously known as X386 1.2E) is a package of source-code
enhancements for X386 1.2, the Intel-based Unix SVGA server provided with
MIT X11R5.  This development has grown to cover more operating systems
not covered by the stock MIT release, include 386BSD, Linux, and Mach386.
Discussion of XFree86 is contributing to overcrowding in several newsgroups.
In addition, more people are getting involved in developing code for
XFree86.  

			Proposed Charter
			----------------

The newsgroup comp.windows.x.i386unix is intended for discussions about
XFree86, the enhancement package for X11R5 on Intel-based Unix, and for
discussions of commercial implementations of the X Window System from OS 
vendors and third parties.  Areas for discussion include:

	1) Frequently Asked Questions - including archive location and
	   retrieval, configuration, and email addresses for developer
	   contacts.  Vendor contact information will also be listed.
	2) Announcements of new and upcoming releases, including calls
	   for beta-testers.  Commercial vendors will be invited to
	   post product summaries, with cross-references to comp.newprod
	   or other sources of detailed information.
	3) Discussions of new features to be developed in XFree86, including 
	   support for new display devices, protocol extensions, etc.
	4) General support from the developers of XFree86, and hopefully
	   from commercial vendors.

Discussion related to the formation of this group should be posted to
news.groups.  Information about XFree86 can be obtained by mailing
to xfree86@physics.su.oz.au.
-- 
David Wexelblat             | dwex@mtgzfs3.att.com  | Somebody get me a 
AT&T Bell Laboratories      | ...!att!mtgzfs3!dwex  |   cheeseburger!
200 Laurel Ave - 4B-421     |                       |      
Middletown, NJ  07748       | (908) 957-5871        | --Steve Miller Band
From: smr@pki-nbg.philips.de (Stephen Riehm)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Common Command line args bug - any help appreciated
Date: 8 Oct 92 22:11:11 GMT
Distribution: fj
Organization: Workstation Div., Supermicro Systems Group, Sony Corporation

Date: 8 Oct 92 10:28:29 GMT
Message-Id: <smr.718540109@hitkw14>
Newsgroups: comp.sys.hp,comp.windows.x.apps,comp.windows.x

smr@pki-nbg.philips.de (Stephen Riehm) writes:

Regarding my earlier posting:

>I have just discovered the following behaviour:

>% xterm -[normal xterm opts] -e foo -d 5 [other opts for foo]
>Error: Can't Open display

...

>Is there a way to stop XtInitialize() from picking up an argument, but
>while still leaving the argument in the list so it can be used by the
>command,  (in this case) so that xterm can pass it on to another command???

I found a work-around, namely, use quotes, ie:

    %xterm -[blah blah] -e foo '-d 5' [blah blah blah]

This is enough to stop XtInitialize() from seeing the -d, and it xterm
then passes it quite nicely to execvp etc etc...

I still think it shouldn't happen though!

-----------------------------------------------------------------
Stephen Riehm		Configuration Management	   _-_|\ 
smr@pki-nbg.philips.de	Philips Kommunikations Industrie  /     \
Work: +49 911 526 2975	N|rnberg, Germany		  \_.-.*/
Fax:  +49 911 526 2095	"I was there, now I am here!"	       v 
"My company speaks another language, I CAN'T speak on it's behalf"
From: thorsen@stc.nato.int (Einar C. Thorsen)
Newsgroups: fj.mail-lists.x-window
Subject: Re: Sharing read/write colorcells
Date: 9 Oct 92 14:32:14 GMT
Distribution: fj
Organization: SHAPE Technical Centre, NL

Date: 9 Oct 92 07:23:24 GMT
Message-Id: <1992Oct9.072324.27518@stc.nato.int>
Newsgroups: comp.windows.x

In <cwikla.718572492@morrison.wri.com> cwikla@morrison.wri.com (John Cwikla) writes:

>In <1992Oct7.151105.27492@stc.nato.int> thorsen@stc.nato.int (Einar C. Thorsen) writes:

>>We have an application that allocates the top half of the color table (128
>>to 256) for read/write color access.  We would like to be able to share some 
>>of these color cells with another application running on the same server 
>>that also uses these colors. So far, we have only been able to display the 
>>same color by having duplicate entries in the color table.  Does anybody
>>know how we can force the applications to share the same read/write entries?

>In theory yes.  Will it work well?  I doubt it.  Read/write cells are inherently
>non shareable.  However nothing says you can't use them.  If you have some sort
>of color cube for your 128 colors and you can figure out mathematically (ie some
>form of a standard colormap) color->pixel calculations you can just use the pixel
>without allocating it -- just use it.  Of course this implies that the
>first program is always running, and thus always has the entries allocated for
>itself.  If it doesn't, problems.  Big time. 

Agree, but the problem is really that we would like "our" colourcells to be used
by any other (3rd party) application. We do in fact not change the definitions
once we have allocated our range of colourcells.

Still searching for help...

---------------------------------------------------------------------------
Einar C. Thorsen                        Phone   : + 31 70 314 22 79
Shape Technical Centre                  Fax     : + 31 70 314 21 11
P.O. Box 174                            Internet: thorsen@stc.nl
2501 CD The Hague, The Netherlands      UUCP    : ...!hp4nl!shapetc!thorsen
---------------------------------------------------------------------------
From: ware@oboe.cis.ohio-state.edu (Peter Ware)
Newsgroups: fj.mail-lists.x-window
Subject: Re: XtNameToWidget timing problem?
Date: 8 Oct 92 07:52:10 GMT
Distribution: fj
Organization: Ohio State Computer Science

Date: Mon, 5 Oct 1992 17:52:16 GMT
Message-Id: <WARE.92Oct5125216@oboe.cis.ohio-state.edu>
Newsgroups: comp.windows.x

In article <1992Oct05.131753.24126@rchland.ibm.com>
shmdgljd@rchland.vnet.ibm.com (Jay Schmidgall) writes:

   Is there some sort of timing necessary for XtNameToWidget to work?
   ...

       menu_pane = XmCreatePulldownMenu (menu_bar, "filepane", NULL, 0);
       if (XtNameToWidget(menu_bar, "filepane"))
	   printf("got it\\n");
       else
	   printf("NOT\\n");

   and NOT gets printed out.  What gives?

Motif creates an intevening widget between the menu_bar and the
menu_pane.  Use "*filepane" to look find the menu_pane.

--pete
--
Pete Ware / Ohio State University /
           ware@cis.ohio-state.edu
           (614) 538-0965
Too bad the Nike slogan isn't "Just Do It Right" instead of "Just Do It"
From: hanssgen@iras4.ira.uka.de (Stefan Haenssgen)
Newsgroups: fj.mail-lists.x-window
Subject: TWM on Sun: new window -> hangup on keypress?
Date: 14 Oct 92 04:51:18 GMT
Distribution: fj
Organization: University of Karlsruhe, FRG

Date: 13 Oct 92 15:56:20 GMT
Message-Id: <1berj4INNjbc@iraul1.ira.uka.de>
Newsgroups: comp.windows.x

We have a small problem here:

Whenever the TWM brings up a new window and lets the user position it
using the mouse (the drag-the-outline-and-click-to-place-it, knowhatimean),
and a key is pressed, TWM often doesn't work properly anymore, i.e.
it leaves you with the "upper-left-corner" cursor which you can move around
but do nothing more. No keypresses or mouse button actions can bring it back
to a useable state.
This is quite annoying since one often uses some function key to send a
freshly created window to the background etc.
*Sometimes* it is possible to log in from another machine and send a kill -HUP
to the TWM process, which then acts as if re-initialized, redraws all windows
and works fine afterwards. However, most of the time TWM just dies on HUP.
[Since we use TWM as the last process in the .xinitrc, that also means that
the whole X environment goes down]

Is this a known problem, is the X installation to blame, what can I do
about it?

Many thanx in advance

	Stefan

PS: The environment  -  Sun SPARCstations, SunOS 4.1.1 & 4.1.2,
    X11R5 (Patchlevel >14 at least)

-- 
      ,-----,------,--,--,   Stefan Haenssgen, Comp Sci, Uni Karlsruhe, Germany
     /     /      /  /  /   Email: haenssgen@ira.uka.de or uk0w@dkauni2.bitnet
    /  ---/-,  ,-/  /  /   IRC: sth   Phone: +49/721/593910   Fax: hoo nose
   /     / /  / /     /   Snail: Nuitsstr. 2c, W-7500 Karlsruhe 21, Germany
  /---  / /  / /  /  /   <I collect postcards from all over the world *hint* :>
 /     / /  / /  /  /   "Use the SOURCE, Luke!" (Return of the RedEye Nights)
'-----' '--' '--'--'   "I feel a great disturbance in the SOURCE"
From: bobmcg@castle.ed.ac.uk (Bob McGonigle)
Newsgroups: fj.mail-lists.x-window
Subject: Postscript to European X User Group Conference
Date: 7 Oct 92 22:55:16 GMT
Distribution: fj
Organization: Edinburgh University Computing Service

Date: 7 Oct 92 16:55:21 GMT
Message-Id: <26649@castle.ed.ac.uk>
Newsgroups: comp.windows.x

The recently held European X User Group conference and exhibition was
resounding success.  This is the fourth year the event has been held, and X
Windows continues to gain new ground and attract more players.

The exhibition was well-attended, with exhibitors offering a wide range of
X terminals, software development tools, training programmes and
connectivity products.  Exhibitors included NCD, Tektronics, V1, VisionWare
and IST.

Speakers addressed issues such as X for conferencing and group working;
current technological trends; X over slow lines; display PostScript and
graphics within X Windows.

Continuing the EXUG policy of inviting big names from the world of X, this
year three US-based experts headed the programme - Doug Young, Oliver Jones
and Bob Scheifler.  The programme included presentations by over 20
speakers, from eight countries.

Pre-conference tutorials proved a major attraction.  Subjects on offer this
year included 'Using C++ with Motif', Debugging X Programs', and a course
designed for newcomers to X - 'From Awareness to Understanding'.

The strength of interest shown in this year's conference has given a boost
to EXUG plans for 1993, including a rolling programme of tutorials,
seminars and workshops, to be held in centres in the UK and other EC
countries.

This year's proceedings are available for 30 pounds (inc.  P&P) from
EXUG, PO Box 458, Cambridge, CB3 8SD, Great Britain.  Payment by cheque
or credit card. 

For further information about the European X User Group and coming
events, telephone +44 (0)223 426534 or fax +44 (0) 223 420251.
From: pierre@lectra.fr (Pierre Ficheux)
Newsgroups: fj.mail-lists.x-window
Subject: Test
Date: 13 Oct 92 12:16:10 GMT
Distribution: fj
Organization: Lectra Systemes, Cestas, France

Date: 7 Oct 92 15:04:48 GMT
Message-Id: <1992Oct7.150448@lectra.fr>
Newsgroups: comp.windows.x

Test, please ignore.

-- 
 ._______________________________.__________________________. 
+-------------------------------'--------------------------'|
| Pierre FICHEUX                | tel   : +33 56 68 80 00  ||
| Lectra Systemes               | fax   : +33 56 78 88 31  ||
| ZI Marticot 33610 CESTAS      | E-mail: pierre@lectra.fr ||          
| FRANCE                        |     			   ||	
`-------------------------------^--------------------------'
Vous qui avez un pied dans la tombe, chaussez l'autre de cuir,
le cuir respire, lui !
From: ajn@solb1.essex.ac.uk (Neil A J)
Newsgroups: fj.mail-lists.x-window
Subject: xnews and Numlock
Date: 7 Oct 92 09:04:38 GMT
Distribution: fj
Organization: University of Essex, Colchester, UK

Date: 6 Oct 92 16:24:11 GMT
Message-Id: <5719@sersun1.essex.ac.uk>
Newsgroups: comp.windows.open-look,comp.windows.x,comp.sys.sun.misc

Does anyone out there know a way to make the NumLock key work on a type
4 keyboard under xnews. We are running OpenWindows 2 (gag I know) on a 
Sun IPX with sunos 4.1.1-IPX. 

other possible solutions, I suppose it could be possible to use xmodmap
to repmap the keypad keys to the number. Or since I am only interested in
using xterm, a set of xterm keybinfings might work - unfortunately I lack
the documentation to perform the minor miracles, or any words of wisdom
would be appreciated.

Thanks - Alastair.
From: eroethke@ems.cdc.com (Earl Roethke)
Newsgroups: fj.mail-lists.x-window
Subject: Convert dxf files to X images
Date: 13 Oct 92 09:07:14 GMT
Distribution: fj
Organization: Empros Systems International, a division of CDC

Date: 9 Oct 92 17:13:37 GMT
Message-Id: <28969@nntp_server.ems.cdc.com>
Newsgroups: comp.graphics,comp.windows.x

What I want to do is convert a dxf file into a structure that I can
load quickly into an X image.  The end result will be to put the image
to a pixmap to be used as the background for a drawing widget.

Anybody know how to do this?  Anybody have a better plan?

Thanks in advance.

-- 
Earl Roethke
eroethke@ems.cdc.com