[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: DCOP question
From:       pbrown () redhat ! com
Date:       1999-11-16 15:26:40
[Download RAW message or body]

On Tue, 16 Nov 1999, Martin Konold wrote:

> On Mon, 15 Nov 1999 pbrown@redhat.com wrote:
> 
> > On Sat, 13 Nov 1999, Geert Jansen wrote:
> > 
> > > 2. Can we introduce a new environment var named DCOPSERVER which contains
> > > the address of the DCOP server? Just like DISPLAY. If no -dcopserver
> > > argument is given, we first look in the var DCOPSERVER, then in .DCOPserver.
> > > This would make it easier for me to implement because then I don't have
> > > to parse the command line to add the -dcopserver argument. And it would
> > > also prevent the need for another command line argument which would disable
> > > adding this argument for non-KDE programs.
> > > Besides easier to implement, it's also more symmetric:
> > > ICEAUTHORITY/DCOPSERVER versus XAUTHORITY/DISPLAY.
> > 
> > We will be doing this.
> 
> In addition the current implementation does not alow to run KDE on two
> workstations simultaneously with nfs shared homes. (The same problem once
> existed with kfm)

Do you know how xsm / X handle this?

I implemented the DCOPSERVER environment variable support.

---
  Preston Brown                                    Systems Engineer
  pbrown@redhat.com                                Red Hat, Inc. 

[prev in list] [next in list] [prev in thread] [next in thread]