On 29 Aug 2000, Lars Gullik Bj�nnes wrote:
> Lior Silberman <[EMAIL PROTECTED]> writes:
>
> | On 28 Aug 2000, Lars Gullik Bj=F8nnes wrote:
> |=20
> | > How should we handle two running LyX processes?
> | > Which one should use/delete the lyxpipe?
> | > (we could use a lock file that containes the pid of the "master" lyx,
> | > only this pid should be allowed to changed files in the .lyx dir)
> | >=20
> | > When we get multiple windos this will be easy to solve.
> | >=20
> | > Lgb
> | >=20
> |=20
> | We can still do this by having several .lyx dirs (using -userdir), which
> | avoids this problem.
>
> That is a very hackish solution and not a long term one.
>
> Lgb
>
Definitely. I did not mean to imply otherwise. But, until we have a
long-term solution, ... :-(
Suggestion: add a lyx-command ("Mini-buffer") to change the pipe name, and
a function to LyXComm to handle this:
void LyXComm::setPipename (string const & n_pip)
{
closeConnection();
pipename = n_pip;
openConnection ();
}
Then (by writing the command to the default pipe each time) you can have
several concurrent servers. Note that this will only work if none of these
continues to use the default name (since this pipe is first used by all
instances in this implementation).
Is this too much of a hack also [until we have mutliple windows] ?
Lior.
