Re: OAF annoyance

[Maciej Stachowiak <mjs eazel com>]

Lutz M <urc8 rz uni-karlsruhe de> writes:

> On 16 Feb 2001 15:39:58 -0600, Federico Mena Quintero wrote:
> > Maybe I have posted this before, so if I have, please tell me that I
> > am too jetlagged still.
> > 
> > Normally oafd gets launched from a random terminal by
> > EOG/Evolution/whatever.  So subsequent processes launched by oafd
> > itself output their spew to the terminal from which oafd was launched.
> > 
> > It is annoying to get spewage to random terminals.  Could we do some
> > fd passing magic to make, say, all the Evolution components output
> > their stuff to the terminal from which you ran "evolution"?
> 
> In addition, the behaviour mentioned above leads to the following
> problem: 
> (1) I ssh into my computer (dormitory) and run evolution displaying it
> through some X server at the university. 
> (2) Back in the dormitory, I run evolution again - but evolution-mail
> etc is still trying to access the remove X server. 
> I always have to start oafd again in order to be able to run evolution.
> 
> Above suggestion would fix this, too. 
> 

No, it's actually totally unrelated; the stdin/stdout/stderr file
descriptors are a totally separate issue from X display.

OAF does have a feature to allow components to be used on programs
running on multiple displays from the same machine (a component can
register as `some.domain.com:0,OAFIID:stuff-stuff'. I think Evolution
is just not using this feature.

Unfortunately, it is not feasible to make this transparent. Because
Gtk+ does not support multiple displays, it is necessary to launch a
separete process for each display for out of proc components; however,
you do not want to do this for non-gui components such as Wombat or
you would waste memory and break expected semantics.

 - Maciej