🚀 go-pugleaf

**> On 21 May 1993 18:51:11 -0400, Greg.Schechter@eng.SUn.COM (Greg Schechter) said:

  Greg>   Perhaps someone has encountered this situtation and found a solution?
  Greg> I want to run one instance of Epoch (I'm currently on Epoch 4.0
  Greg> Patchlevel 1), and have the flexibility of creating new screens on a
  Greg> different X display than the one I started up on.

Sorry, Greg, epoch won't do that.

It creates a single Display andd never makes another Display
connection (like most X Clients).

I suppose in theory it shouldn't be hard to modify x_create_screen to
make a new connection, but you only want to do that if you are making
a new connection on a different display (you don't want to run out of
file descriptors...).  Also, you'd have to hack the event handling
code in a major way --- I don't want to think what that might look
like.

  Greg>   The obvious way to me to do this would be to set my DISPLAY
  Greg> environment variable within the emacs environment (via "M-x setenv")
  Greg> to the other display (say ":0.1" if my default display was originally
  Greg> ":0.0").  However, this doesn't seem to affect the creation of
  Greg> subsequent windows.

All that will do is affect the environment passed to child
processes.....

  Greg>   Has anyone tried this with any luck?

This kind of thing (and others, like dialing up via modem and
connecting to an existing Emacs process) is one reason why Emacs 19 is
using the X Toolkit to handle event processing.

Brook
--
Klacktoveedsedstene

>>>>> On 22 May 1993 13:47:13 EST,
>>>>> In message <DBC.93May22134713@hamlet.cs.brown.edu>,
>>>>> dbc@cs.brown.edu (Brook Conner) wrote:

Brook> This kind of thing (and others, like dialing up via modem and
Brook> connecting to an existing Emacs process) is one reason why
Brook> Emacs 19 is using the X Toolkit to handle event processing.
       ^^^^^^^^

Lucid emacs 19.

FSF Emacs 19 is built directly on top of Xlib, as it always has been.

In gnu.epoch.misc Brook Conner <dbc@cs.brown.edu> wrote:
> 
> I suppose in theory it shouldn't be hard to modify x_create_screen to
> make a new connection

The real tricky part is resource usage: you have to be careful to use server
IDs only with the server they came from, whereas right now, X ids are stored
all over the place.  (We're probably going to do it eventually.)

> Also, you'd have to hack the event handling code in a major way --- I don't
> want to think what that might look like.

This part is a no-brainer in lemacs.

> This kind of thing (and others, like dialing up via modem and
> connecting to an existing Emacs process) is one reason why Emacs 19 is
> using the X Toolkit to handle event processing.

You mean Lucid Emacs; FSF19 still uses raw Xlib, which is a bad idea for
the reason you just stated...

	-- Jamie