Emacs as default editor in OpenWindows

[Dale Worley]

I don't use OpenWindows, but I'm pretty familiar with how Emacs behaves,
so here's some ideas about what might be going on:

If Emacs gets fired up and brings up a window with the right name but
wrong full path name, it's probably because it gets started with just the
filename as an argument, rather than the full pathname.  Emacs inherits
the current directory of whatever starts it up and then attempts to find
the file in that directory.  This is probably a bug in OpenWindows.

If you specify the editor as "emacs" and it comes up with a window called
"-WL", that is because OpenWindows is assuming that Emacs understands all
the standard Sun Windows options, and is using a command line like "emacs
-WL xxx file.foo".  Emacs assumes that all arguments are file names..  You
should probably be using emacstool, which *does* understand these options.

With some luck, emacstool will also solve the two-windows problem (one for
the shelltool, one for emacs), because it should be informing Emacs that
it should use the window already provided, rather than starting an X
window.  If that fails, use the -nw ("no window system") option: "emacs
-nw" (it must be the *first* option to Emacs).

Dale Worley		Compass, Inc.			worley at compass.com

Isn't it interesting that the first thing you do with your
color bitmapped window system on a network is emulate an ASR33?