Am 13.11.2010 um 14:59 schrieb Enrico Forestieri:
On Sat, Nov 13, 2010 at 01:57:54PM +0100, Stephan Witt wrote:
Am 13.11.2010 um 13:46 schrieb Jean-Marc Lasgouttes:
Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
I don't know how that single instance enforcement is attained, but if
Am 13.11.2010 um 14:59 schrieb Enrico Forestieri:
> On Sat, Nov 13, 2010 at 01:57:54PM +0100, Stephan Witt wrote:
>
>> Am 13.11.2010 um 13:46 schrieb Jean-Marc Lasgouttes:
>>
>>> Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
I don't know how that single instance enforcement is
On Fri, Nov 12, 2010 at 09:28:07PM -0500, BH wrote:
On Fri, Nov 12, 2010 at 5:50 PM, Enrico Forestieri for...@lyx.org wrote:
On Fri, Nov 12, 2010 at 11:43:57PM +0100, Jean-Marc Lasgouttes wrote:
Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
Without any preference set or command line
On Sat, Nov 13, 2010 at 01:47:22AM +0100, Pavel Sanda wrote:
Richard Heck wrote:
On 11/12/2010 04:34 PM, Enrico Forestieri wrote:
Here is a complete patch with preferences and command line switches.
It is designed such that an already running instance is contacted only
when a document
Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
I don't know how that single instance enforcement is attained, but if
that is true, you should not be able to launch a new instance of lyx
by using the --no-remote switch. So, launch lyx a first time, then try
to get a new instance using lyx
Am 13.11.2010 um 13:46 schrieb Jean-Marc Lasgouttes:
Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
I don't know how that single instance enforcement is attained, but if
that is true, you should not be able to launch a new instance of lyx
by using the --no-remote switch. So, launch lyx a
On Sat, Nov 13, 2010 at 01:57:54PM +0100, Stephan Witt wrote:
Am 13.11.2010 um 13:46 schrieb Jean-Marc Lasgouttes:
Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
I don't know how that single instance enforcement is attained, but if
that is true, you should not be able to launch a new
On Fri, Nov 12, 2010 at 09:28:07PM -0500, BH wrote:
> On Fri, Nov 12, 2010 at 5:50 PM, Enrico Forestieri wrote:
> > On Fri, Nov 12, 2010 at 11:43:57PM +0100, Jean-Marc Lasgouttes wrote:
> >
> >> Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
> >> >Without any preference set
On Sat, Nov 13, 2010 at 01:47:22AM +0100, Pavel Sanda wrote:
> Richard Heck wrote:
> > On 11/12/2010 04:34 PM, Enrico Forestieri wrote:
> >> Here is a complete patch with preferences and command line switches.
> >>
> >> It is designed such that an already running instance is contacted only
> >>
Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
I don't know how that single instance enforcement is attained, but if
that is true, you should not be able to launch a new instance of lyx
by using the --no-remote switch. So, launch lyx a first time, then try
to get a new instance using "lyx
Am 13.11.2010 um 13:46 schrieb Jean-Marc Lasgouttes:
> Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
>> I don't know how that single instance enforcement is attained, but if
>> that is true, you should not be able to launch a new instance of lyx
>> by using the --no-remote switch. So, launch
On Sat, Nov 13, 2010 at 01:57:54PM +0100, Stephan Witt wrote:
> Am 13.11.2010 um 13:46 schrieb Jean-Marc Lasgouttes:
>
> > Le 13 nov. 10 à 12:29, Enrico Forestieri a écrit :
> >> I don't know how that single instance enforcement is attained, but if
> >> that is true, you should not be able to
On Thu, Nov 11, 2010 at 04:32:26PM +0100, Enrico Forestieri wrote:
Here is another somewhat polished version.
So, should I commit this patch?
--
Enrico
On 11/11/2010 10:32 AM, Enrico Forestieri wrote:
On Thu, Nov 11, 2010 at 04:59:01AM +0100, Enrico Forestieri wrote:
On Thu, Nov 11, 2010 at 02:57:48AM +0100, Vincent van Ravesteijn wrote:
I'd like you to guide me a bit in with respect to using the pipes
then. Detecting whether a pipe exists is
Richard Heck wrote:
The only thing lacking here is the preference stuff, but someone else could
do that, if you wish.
yes it should be under preferences. personally i would like to run always
without this feature (dont like when crash in one window kill all other
windows).
btw what happens
yes it should be under preferences. personally i would like to run always
without this feature (dont like when crash in one window kill all other
windows).
Hmm.. you're working on multiple documents in the same time. Why do we
have the multiple window option then in LyX ? (And I thought you
Vincent van Ravesteijn wrote:
yes it should be under preferences. personally i would like to run always
without this feature (dont like when crash in one window kill all other
windows).
Hmm.. you're working on multiple documents in the same time. Why do we
have the multiple window
Here is a complete patch with preferences and command line switches.
It is designed such that an already running instance is contacted only
when a document is to be loaded. So, if you export from command line,
things go as usual.
You can set a preference for the default behavior, but you can
On 11/12/2010 04:34 PM, Enrico Forestieri wrote:
Here is a complete patch with preferences and command line switches.
It is designed such that an already running instance is contacted only
when a document is to be loaded. So, if you export from command line,
things go as usual.
You can set a
Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
Without any preference set or command line switch specified, the
default
is to try to load documents in an already running instance, as I think
that this the most logical behavior. However, once you untick the
Single instance check box in the
On Fri, Nov 12, 2010 at 11:43:57PM +0100, Jean-Marc Lasgouttes wrote:
Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
Without any preference set or command line switch specified, the
default
is to try to load documents in an already running instance, as I think
that this the most logical
Richard Heck wrote:
On 11/12/2010 04:34 PM, Enrico Forestieri wrote:
Here is a complete patch with preferences and command line switches.
It is designed such that an already running instance is contacted only
when a document is to be loaded. So, if you export from command line,
things go as
On Fri, Nov 12, 2010 at 5:50 PM, Enrico Forestieri for...@lyx.org wrote:
On Fri, Nov 12, 2010 at 11:43:57PM +0100, Jean-Marc Lasgouttes wrote:
Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
Without any preference set or command line switch specified, the
default
is to try to load
On Thu, Nov 11, 2010 at 04:32:26PM +0100, Enrico Forestieri wrote:
> Here is another somewhat polished version.
So, should I commit this patch?
--
Enrico
On 11/11/2010 10:32 AM, Enrico Forestieri wrote:
On Thu, Nov 11, 2010 at 04:59:01AM +0100, Enrico Forestieri wrote:
On Thu, Nov 11, 2010 at 02:57:48AM +0100, Vincent van Ravesteijn wrote:
I'd like you to guide me a bit in with respect to using the pipes
then. Detecting whether a pipe exists is
Richard Heck wrote:
> The only thing lacking here is the preference stuff, but someone else could
> do that, if you wish.
yes it should be under preferences. personally i would like to run always
without this feature (dont like when crash in one window kill all other
windows).
btw what happens
> yes it should be under preferences. personally i would like to run always
> without this feature (dont like when crash in one window kill all other
> windows).
Hmm.. you're working on multiple documents in the same time. Why do we
have the multiple window option then in LyX ? (And I thought
Vincent van Ravesteijn wrote:
> > yes it should be under preferences. personally i would like to run always
> > without this feature (dont like when crash in one window kill all other
> > windows).
>
> Hmm.. you're working on multiple documents in the same time. Why do we
> have the multiple
Here is a complete patch with preferences and command line switches.
It is designed such that an already running instance is contacted only
when a document is to be loaded. So, if you export from command line,
things go as usual.
You can set a preference for the default behavior, but you can
On 11/12/2010 04:34 PM, Enrico Forestieri wrote:
Here is a complete patch with preferences and command line switches.
It is designed such that an already running instance is contacted only
when a document is to be loaded. So, if you export from command line,
things go as usual.
You can set a
Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
Without any preference set or command line switch specified, the
default
is to try to load documents in an already running instance, as I think
that this the most logical behavior. However, once you untick the
"Single instance" check box in
On Fri, Nov 12, 2010 at 11:43:57PM +0100, Jean-Marc Lasgouttes wrote:
> Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
> >Without any preference set or command line switch specified, the
> >default
> >is to try to load documents in an already running instance, as I think
> >that this the most
Richard Heck wrote:
> On 11/12/2010 04:34 PM, Enrico Forestieri wrote:
>> Here is a complete patch with preferences and command line switches.
>>
>> It is designed such that an already running instance is contacted only
>> when a document is to be loaded. So, if you export from command line,
>>
On Fri, Nov 12, 2010 at 5:50 PM, Enrico Forestieri wrote:
> On Fri, Nov 12, 2010 at 11:43:57PM +0100, Jean-Marc Lasgouttes wrote:
>
>> Le 12 nov. 10 à 22:34, Enrico Forestieri a écrit :
>> >Without any preference set or command line switch specified, the
>> >default
>> >is to try
Enrico Forestieri wrote:
Due to this, I think that it means that the code can be basically
destabilized, provided that there's consensus. Fine, good to know.
yes.
do you know the immigration story of kurt goedel? before entering u.s.
he went closely throught the constitution to be prepared for
On Thu, Nov 11, 2010 at 04:59:01AM +0100, Enrico Forestieri wrote:
On Thu, Nov 11, 2010 at 02:57:48AM +0100, Vincent van Ravesteijn wrote:
I'd like you to guide me a bit in with respect to using the pipes
then. Detecting whether a pipe exists is indeed easy. However, I need
to add some
Enrico Forestieri wrote:
> Due to this, I think that it means that the code can be "basically"
> destabilized, provided that there's "consensus". Fine, good to know.
yes.
do you know the immigration story of kurt goedel? before entering u.s.
he went closely throught the constitution to be
On Thu, Nov 11, 2010 at 04:59:01AM +0100, Enrico Forestieri wrote:
> On Thu, Nov 11, 2010 at 02:57:48AM +0100, Vincent van Ravesteijn wrote:
> > I'd like you to guide me a bit in with respect to using the pipes
> > then. Detecting whether a pipe exists is indeed easy. However, I need
> > to add
Hi all,
These two patches implement a single instance LyX.
I can add some preference options.
- What kind of preference do we need ?
- Do we want to include the code for QtSingleApplication in our tree ?
- We then depend on QtNetwork.dll/lib and should be included in the installers.
- The
These two patches implement a single instance LyX.
Comments ?
Pavel,
Do you think it has a chance to make it into 2.0.0 ?
Vincent
On 11/10/2010 12:14 PM, Vincent van Ravesteijn wrote:
Hi all,
These two patches implement a single instance LyX.
Nice work!
I can add some preference options.
- What kind of preference do we need ?
A preference to enable or disable this kind of behavior. So:
if
On Wed, Nov 10, 2010 at 06:21:52PM +0100, Vincent van Ravesteijn wrote:
These two patches implement a single instance LyX.
Comments ?
Pavel,
Do you think it has a chance to make it into 2.0.0 ?
I think no, if we follow the rules.
--
Enrico
Pavel,
Do you think it has a chance to make it into 2.0.0 ?
I think no, if we follow the rules.
I thought that the rule was to ask Pavel ;).
Vincent
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
--
Enrico
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
http://www.gitorious.com/lyx/lyx/commit/b985f653c03ad9dbf77c9e3dadf9f6d3eeaba8ae
http://www.gitorious.com/lyx/lyx/commit/8edf37e21bfbbae23e87210b959ef9dfe5e8e81c
or find them attached to the bug:
Op 10-11-2010 20:14, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
http://www.gitorious.com/lyx/lyx/commit/b985f653c03ad9dbf77c9e3dadf9f6d3eeaba8ae
http://www.gitorious.com/lyx/lyx/commit/8edf37e21bfbbae23e87210b959ef9dfe5e8e81c
or find
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
We can maybe rewrite it to use pipes. Or we can rewrite the piped code
to
On Wed, Nov 10, 2010 at 08:13:48PM +0100, Vincent van Ravesteijn wrote:
Pavel,
Do you think it has a chance to make it into 2.0.0 ?
I think no, if we follow the rules.
I thought that the rule was to ask Pavel ;).
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg163211.html
I thought that the rule was to ask Pavel ;).
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg163211.html
Development moved to the beta phase which basically means we will no
more include new features and focus on polishing the current ones.
basically leaves room for
On Wed, Nov 10, 2010 at 08:17:11PM +0100, Vincent van Ravesteijn wrote:
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
On Wed, Nov 10, 2010 at 08:21:37PM +0100, Vincent van Ravesteijn wrote:
I thought that the rule was to ask Pavel ;).
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg163211.html
Development moved to the beta phase which basically means we will
no more include new features and focus
On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
We can maybe rewrite
On Wed, Nov 10, 2010 at 03:10:07PM -0500, Richard Heck wrote:
On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency.
Enrico Forestieri wrote:
Do you think it has a chance to make it into 2.0.0 ?
I think no, if we follow the rules.
i would like to know whats going on behind this.
you dont like that
1. we push new features
2. this feature is evil
or 3. the implementation of this feature is not your taste?
On Wed, Nov 10, 2010 at 03:10:07PM -0500, Richard Heck wrote:
On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency.
Vincent van Ravesteijn wrote:
- What kind of preference do we need ?
[ ] use single instance for all windows
i would vote for letting this off by default.
- Do we want to include the code for QtSingleApplication in our tree ?
- We then depend on QtNetwork.dll/lib and should be included in
On Thu, Nov 11, 2010 at 12:09:01AM +0100, Pavel Sanda wrote:
Enrico Forestieri wrote:
Do you think it has a chance to make it into 2.0.0 ?
I think no, if we follow the rules.
i would like to know whats going on behind this.
you dont like that
1. we push new features
Yes, especially
On Thu, Nov 11, 2010 at 12:14:11AM +0100, Andre Poenitz wrote:
On Wed, Nov 10, 2010 at 03:10:07PM -0500, Richard Heck wrote:
On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van
Enrico Forestieri wrote:
I think no, if we follow the rules.
i would like to know whats going on behind this.
you dont like that
1. we push new features
Yes, especially not when by the rules they would be basically forbidden.
thats misunderstanding. release announcement is public
There's already code that checks for an existing lyxpipe. If another
instance of lyx is connected to the other end, a message is printed
to that effect, otherwise it is a stale pipe (maybe a left over from
a previous crash) and is removed.
So, instead of printing a message to the console,
On Thu, Nov 11, 2010 at 02:57:48AM +0100, Vincent van Ravesteijn wrote:
I'd like you to guide me a bit in with respect to using the pipes
then. Detecting whether a pipe exists is indeed easy. However, I need
to add some public functions to the Server interface that relays to
LyXComm. Moreover,
On Thu, Nov 11, 2010 at 01:38:27AM +0100, Pavel Sanda wrote:
Enrico Forestieri wrote:
I think no, if we follow the rules.
i would like to know whats going on behind this.
you dont like that
1. we push new features
Yes, especially not when by the rules they would be basically
Hi all,
These two patches implement a single instance LyX.
I can add some preference options.
- What kind of preference do we need ?
- Do we want to include the code for QtSingleApplication in our tree ?
- We then depend on QtNetwork.dll/lib and should be included in the installers.
- The
> These two patches implement a single instance LyX.
>
>
> Comments ?
>
Pavel,
Do you think it has a chance to make it into 2.0.0 ?
Vincent
On 11/10/2010 12:14 PM, Vincent van Ravesteijn wrote:
Hi all,
These two patches implement a single instance LyX.
Nice work!
I can add some preference options.
- What kind of preference do we need ?
A preference to enable or disable this kind of behavior. So:
if
On Wed, Nov 10, 2010 at 06:21:52PM +0100, Vincent van Ravesteijn wrote:
> > These two patches implement a single instance LyX.
> >
> >
> > Comments ?
> >
>
>
> Pavel,
>
> Do you think it has a chance to make it into 2.0.0 ?
I think no, if we follow the rules.
--
Enrico
>>
>> Pavel,
>>
>> Do you think it has a chance to make it into 2.0.0 ?
>
> I think no, if we follow the rules.
>
I thought that the rule was to ask Pavel ;).
Vincent
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
> - We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
--
Enrico
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
> http://www.gitorious.com/lyx/lyx/commit/b985f653c03ad9dbf77c9e3dadf9f6d3eeaba8ae
> http://www.gitorious.com/lyx/lyx/commit/8edf37e21bfbbae23e87210b959ef9dfe5e8e81c
>
> or find them attached to the bug:
>
Op 10-11-2010 20:14, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
http://www.gitorious.com/lyx/lyx/commit/b985f653c03ad9dbf77c9e3dadf9f6d3eeaba8ae
http://www.gitorious.com/lyx/lyx/commit/8edf37e21bfbbae23e87210b959ef9dfe5e8e81c
or find
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
We can maybe rewrite it to use pipes. Or we can rewrite the piped code
to
On Wed, Nov 10, 2010 at 08:13:48PM +0100, Vincent van Ravesteijn wrote:
> >>
> >> Pavel,
> >>
> >> Do you think it has a chance to make it into 2.0.0 ?
> >
> > I think no, if we follow the rules.
> >
>
> I thought that the rule was to ask Pavel ;).
I thought that the rule was to ask Pavel ;).
http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg163211.html
>Development moved to the beta phase which basically means we will no
more include new features and focus on polishing the current ones.
"basically" leaves room for
On Wed, Nov 10, 2010 at 08:17:11PM +0100, Vincent van Ravesteijn wrote:
> Op 10-11-2010 20:13, Enrico Forestieri schreef:
> >On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
> >>- We then depend on QtNetwork.dll/lib
> >YA dependency. This is bad for a next to useless
On Wed, Nov 10, 2010 at 08:21:37PM +0100, Vincent van Ravesteijn wrote:
>
> >>I thought that the rule was to ask Pavel ;).
> >http://www.mail-archive.com/lyx-devel@lists.lyx.org/msg163211.html
> >
>
> >Development moved to the beta phase which basically means we will
> no more include new
On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
Op 10-11-2010 20:13, Enrico Forestieri schreef:
On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
- We then depend on QtNetwork.dll/lib
YA dependency. This is bad for a next to useless feature.
We can maybe rewrite
On Wed, Nov 10, 2010 at 03:10:07PM -0500, Richard Heck wrote:
> On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
> > Op 10-11-2010 20:13, Enrico Forestieri schreef:
> >>On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
> >>>- We then depend on QtNetwork.dll/lib
> >>YA
Enrico Forestieri wrote:
> > Do you think it has a chance to make it into 2.0.0 ?
>
> I think no, if we follow the rules.
i would like to know whats going on behind this.
you dont like that
1. we push new features
2. this feature is evil
or 3. the implementation of this feature is not your
On Wed, Nov 10, 2010 at 03:10:07PM -0500, Richard Heck wrote:
> On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
> > Op 10-11-2010 20:13, Enrico Forestieri schreef:
> >>On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van Ravesteijn wrote:
> >>>- We then depend on QtNetwork.dll/lib
> >>YA
Vincent van Ravesteijn wrote:
> - What kind of preference do we need ?
[ ] use single instance for all windows
i would vote for letting this off by default.
> - Do we want to include the code for QtSingleApplication in our tree ?
> - We then depend on QtNetwork.dll/lib and should be included
On Thu, Nov 11, 2010 at 12:09:01AM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > > Do you think it has a chance to make it into 2.0.0 ?
> >
> > I think no, if we follow the rules.
>
> i would like to know whats going on behind this.
> you dont like that
> 1. we push new features
Yes,
On Thu, Nov 11, 2010 at 12:14:11AM +0100, Andre Poenitz wrote:
> On Wed, Nov 10, 2010 at 03:10:07PM -0500, Richard Heck wrote:
> > On 11/10/2010 02:17 PM, Vincent van Ravesteijn wrote:
> > > Op 10-11-2010 20:13, Enrico Forestieri schreef:
> > >>On Wed, Nov 10, 2010 at 06:14:53PM +0100, Vincent van
Enrico Forestieri wrote:
> > > I think no, if we follow the rules.
> >
> > i would like to know whats going on behind this.
> > you dont like that
> > 1. we push new features
>
> Yes, especially not when by the rules they would be "basically" forbidden.
thats misunderstanding. release
> There's already code that checks for an existing lyxpipe. If another
> instance of lyx is connected to the other end, a message is printed
> to that effect, otherwise it is a stale pipe (maybe a left over from
> a previous crash) and is removed.
>
> So, instead of printing a message to the
On Thu, Nov 11, 2010 at 02:57:48AM +0100, Vincent van Ravesteijn wrote:
> I'd like you to guide me a bit in with respect to using the pipes
> then. Detecting whether a pipe exists is indeed easy. However, I need
> to add some public functions to the Server interface that relays to
> LyXComm.
On Thu, Nov 11, 2010 at 01:38:27AM +0100, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > > > I think no, if we follow the rules.
> > >
> > > i would like to know whats going on behind this.
> > > you dont like that
> > > 1. we push new features
> >
> > Yes, especially not when by the rules
86 matches
Mail list logo