Petr Šimon wrote:
> Hello,
> I have a question about citation-insert, which I use from a Firefox
> extension Lyz, a plugin for Zotero.
> When I set the citation format to (Author, year) (using natbib and
> plainnat) and send citation-insert to lyxserver the citation is inserted as
> Author (year),
On 1.02.05, Jean-Marc Lasgouttes wrote:
>
> G> Dear developers, trying to use the lyxserver for a kind of
> G> scripting support, I came accross some troublespots.
>
> I did not have time to look seriously at all the report, but I believe
> that many of them can be trivially fixed.
Nice to hea
> "G" == G Milde <[EMAIL PROTECTED]> writes:
G> Dear developers, trying to use the lyxserver for a kind of
G> scripting support, I came accross some troublespots.
Hello Günter,
I did not have time to look seriously at all the report, but I believe
that many of them can be trivially fixed. Bu
On Wed, Jan 26, 2005 at 04:47:52PM +0100, G. Milde wrote:
> Dear developers,
>
> trying to use the lyxserver for a kind of scripting support, I came accross
> some troublespots.
Could you put that on bugzilla, too? Please.
Andre'
On Monday 19 August 2002 3:45 pm, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | On Monday 19 August 2002 3:31 pm, Lars Gullik Bjønnes wrote:
> >> Remember that a socket could be stale...
> |
> | Surely the LyXServer's d-tor should delete it?
>
> In an ideal world yes..
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 3:31 pm, Lars Gullik Bjønnes wrote:
>> Remember that a socket could be stale...
>
| Surely the LyXServer's d-tor should delete it?
In an ideal world yes but perhaps we crashed before that could
happen.
--
Lgb
On Monday 19 August 2002 3:31 pm, Lars Gullik Bjønnes wrote:
> Remember that a socket could be stale...
Surely the LyXServer's d-tor should delete it?
Angus
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 2:30 pm, Lars Gullik Bjønnes wrote:
>> | Anyway, I'm perfectly happy to use named sockets rather than pipes, but
>> | AFAICS there is still a problem. If I'm an external program, how do I
>> | find out the /name/ of this named s
On Monday 19 August 2002 2:30 pm, Lars Gullik Bjønnes wrote:
> | Anyway, I'm perfectly happy to use named sockets rather than pipes, but
> | AFAICS there is still a problem. If I'm an external program, how do I
> | find out the /name/ of this named socket if LyX is going to have many of
> | them.
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 1:34 pm, Lars Gullik Bjønnes wrote:
>> Try this:
>>
>> cd /tmp
>> mkfifo fifo
>> cat fifo &
>> cat fifo &
>> echo "hello there" > fifo
>>
>> How many "hello there" do you get?
>
| Yes, yes. I understand. But your statement about
"Lars Gullik Bjønnes" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> | No local sockets on Windows...
>
> I think they have local sockets on Windows...
> (at least Java on Windows has LocalSocket)
>
Must be some sort of emulation...
AF_UNIX (AF_LOCAL) is just
On Monday 19 August 2002 1:34 pm, Lars Gullik Bjønnes wrote:
> Try this:
>
> cd /tmp
> mkfifo fifo
> cat fifo &
> cat fifo &
> echo "hello there" > fifo
>
> How many "hello there" do you get?
Yes, yes. I understand. But your statement about LyX not being able to have
multiple clients is nonsense
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 1:10 pm, Lars Gullik Bjønnes wrote:
>> The really great benefit of named sockets/local sockets is that they
>> allow multiple clients. With named pipes you can only have one client
>> at a time.
>
| That's not strictly true. The
On Monday 19 August 2002 1:10 pm, Lars Gullik Bjønnes wrote:
> The really great benefit of named sockets/local sockets is that they
> allow multiple clients. With named pipes you can only have one client
> at a time.
That's not strictly true. The LyXServer can have many clients so long as they
s
On Monday 19 August 2002 1:10 pm, Lars Gullik Bjønnes wrote:
> so you have not played with network programming?
No I'm a fluid dynamics engineer who has been picking up the language of the
computer scientist by playing with LyX.
Angus
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 12:43 pm, Ruurd Reitsma wrote:
>> "Angus Leeming" <[EMAIL PROTECTED]> wrote in message
>> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>>
>> > > And I really think that we should ditch pipes as well and move on to
>> > > local
"Ruurd Reitsma" <[EMAIL PROTECTED]> writes:
| "Angus Leeming" <[EMAIL PROTECTED]> wrote in message
| [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>> >
>> > And I really think that we should ditch pipes as well and move on to
>> > local sockets.
>>
>> What about OS/2 and Windows? Do they have loc
On Monday 19 August 2002 12:43 pm, Ruurd Reitsma wrote:
> "Angus Leeming" <[EMAIL PROTECTED]> wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
>
> > > And I really think that we should ditch pipes as well and move on to
> > > local sockets.
> >
> > What about OS/2 and Windows? Do t
"Angus Leeming" <[EMAIL PROTECTED]> wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> >
> > And I really think that we should ditch pipes as well and move on to
> > local sockets.
>
> What about OS/2 and Windows? Do they have local sockets?
>
No local sockets on Windows... Actually,
On Monday 19 August 2002 11:41 am, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | On Monday 19 August 2002 11:27 am, Lars Gullik Bjønnes wrote:
> >> Angus Leeming <[EMAIL PROTECTED]> writes:
> >> | On Monday 19 August 2002 10:43 am, Lars Gullik Bjønnes wrote:
> >> >> I
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 11:27 am, Lars Gullik Bjønnes wrote:
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>> | On Monday 19 August 2002 10:43 am, Lars Gullik Bjønnes wrote:
>> >> I have a small socket lib that I use from time to time...
>> >> (It works
On Monday 19 August 2002 11:27 am, Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
> | On Monday 19 August 2002 10:43 am, Lars Gullik Bjønnes wrote:
> >> I have a small socket lib that I use from time to time...
> >> (It works for named sockets/unix sockets/local sockets as
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 10:43 am, Lars Gullik Bjønnes wrote:
>> I have a small socket lib that I use from time to time...
>> (It works for named sockets/unix sockets/local sockets as well.)
>
| Isn't this just what lyxserver needs? It just sends and re
On Monday 19 August 2002 10:43 am, Lars Gullik Bjønnes wrote:
> I have a small socket lib that I use from time to time...
> (It works for named sockets/unix sockets/local sockets as well.)
Isn't this just what lyxserver needs? It just sends and receives dats to and
from FIFO files. Could I have
On Monday 19 August 2002 10:46 am, Andre Poenitz wrote:
> PS: I'll attach the stuff in case anybody wants to have a look.
Ok, this does rather more than I was anticipating.
It takes a command as argument, eg "maple -q" and forks a new process,
allowing you to send data to, and receive data fro
On Mon, Aug 19, 2002 at 10:12:34AM +0100, Angus Leeming wrote:
> Didn't André post a pipestream class to the list some time ago? These sort of
> semantic differences should be encapsulated and hidden away.
I believe there was a strong connection between "my" pipestream class
and socket++ (i.e. t
Angus Leeming <[EMAIL PROTECTED]> writes:
| On Monday 19 August 2002 9:33 am, Jean-Marc Lasgouttes wrote:
>> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>> Angus> So, why's LyX going crazy and continually opening and closing
>> Angus> the connection under Tru64 unix? Is this som
On Monday 19 August 2002 9:33 am, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> So, why's LyX going crazy and continually opening and closing
> Angus> the connection under Tru64 unix? Is this something I should
> Angus> worry about?
>
> The sem
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> So, why's LyX going crazy and continually opening and closing
Angus> the connection under Tru64 unix? Is this something I should
Angus> worry about?
The semantics of select on a named pipe are different on tru64 and
others. This m
> "Soeren" == <[EMAIL PROTECTED]> writes:
Soeren> One question which I haven't found out yet. Is the Lyxserver
Soeren> working synchronous or asynchronous for the same client??? Yes
Soeren> of course I could test it out, but for one or the other reason
Soeren> I would like to know whether t
Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
| Ok, done. The "int clients" in LyXServer has been replaced by
| "vector clients". The server adds the clients names on
| "hello" messages instead of doing clients++. On "bye" messages, the server
| checks that the client is in the vector, and remov
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Ok, I will use the crude array in the 1.0.x patches, no
Stefano> problem. Is STL "allowed" in the development version?
It is even extensively used there.
JMarc
Hi Jean-Marc,
> I'd rather avoid to use STL stuff in 1.0.x, since it still compiles
> with old compilers which have broken STL and template support. In
> 1.1.x, the situation is different, since by the time we release it,
> the situation should have improved...
>
> Could you use a plain old link
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> I add to #include the standard in lyxserver.h and
Stefano> in lyxserver.C, but I do not know how to make the
Stefano> necessary modifications to check for these in the configure
Stefano> stuff, sorry.
I'd rather avoid to
Hi Asger and everyone,
> There is no deadline, except that we just got the first cut at docbook support
> in, and that will need some time to be finished, and polished up before the
> 1.0.4 release.
Ok, then I have time to rewrite the server patches for the stable code.
> In particular, if it's
> Ok, can you give me a deadline? I also saw that 1.1.x uses "string"
> instead of LString and a different syntax for error streams. I have coded
> for 1.1.x, will 1.0.4 be based on that or on the 1.0.3 code?
As Jean-Marc noticed, 1.0.4 will be based on the 1.0.3 code (or specifically,
on the ly
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Hi Asger and everyone,
>> > If you think it's worth it, I will submit the following to this
>> list:
>>
>> Of course it is worth it! The earlier you send this, the better
>> ;-) If the patch looks good, I still think we s
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Hi all,
>> Speaking about lyxserver problems, there is one which bothers me
>> now: it does not work at all on Digital Unix, due to a peculiarity
>> of the select() implementation (excerpt from the man page):
>>
>> [Digita
Hi all,
> Speaking about lyxserver problems, there is one which bothers me now:
> it does not work at all on Digital Unix, due to a peculiarity of the
> select() implementation (excerpt from the man page):
>
> [Digital] Objects ready for the requested operation are those which the
> operati
Hi Asger and everyone,
> > If you think it's worth it, I will submit the following to this list:
>
> Of course it is worth it! The earlier you send this, the better ;-)
> If the patch looks good, I still think we should put it into 1.0.4
Ok, can you give me a deadline? I also saw that 1.1.x us
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> I still have one concern with the LyX server code but I don't want
>> to abuse of your patience any longer. I will speak of this another
>> time.
Asger> I have patience to hear what the problem is now. I see no
Asger> reason
> I am working on a LyX client, and I have suggested a small change in the
> LyX server in order to make client implementation easier.
> If you think it's worth it, I will submit the following to this list:
[Lots of great stuff]
Of course it is worth it! The earlier you send this, the better
Miyata Shigeru <[EMAIL PROTECTED]> writes:
| emx has only BSD sockets support. Well, OS/2 named pipes can be
| accessed from multiple cliants if the server takes care of them...
| (In fact you can create many pipes of the same name.)
|
| I'm not ready to determine anything on this. Please cont
On 4 Jun 1999 17:17:27 +0900, Miyata Shigeru wrote:
>[EMAIL PROTECTED] (Lars Gullik Bjnnes) wrote:
>
>> I am not sure if you know the difference between UNIX sockets and BSD
>> sockets. BSD sockets is used for networking and accessing computers
>> and otherplaces in the network, when you connect
[EMAIL PROTECTED] (Lars Gullik Bjnnes) wrote:
> I am not sure if you know the difference between UNIX sockets and BSD
> sockets. BSD sockets is used for networking and accessing computers
> and otherplaces in the network, when you connect to a BSD socket you
> connect to a ip number and a port. U
"Arnd Hanses" <[EMAIL PROTECTED]> writes:
| I'm not a programmer, the only experience comes from some simple
| porting I've done. But I think there are of course sockets and at least
| the OS/2 API has (named) pipes with extended functionality.
|
| The issue here being networked access to and mo
On 01 Jun 1999 20:23:42 +0200, Lars Gullik Bj°nnes wrote:
>
>We will use UNIX sockets, so security will not be a problem.
>(the normal file permissions will apply to the socket)
>| How'll do that for non-UNIX LyX? IIRC neither emx/gcc nor cygwin/gcc
>| know UNIX file permissions. But it would ind
> We should be very restrictive on what we call a bug at this point, the
> '\n' that Jean-Marc added is obvious, changing _any_ part of the
> protocol is not.
Well, I consider the change a bug-fix. The protocol is after all broken, and
should be fixed.
Also, it is a safe change. The two main ex
> bla bla safe change bla bla... how many times have we said that made
> the fix and then we discovers bugs because of it?
Many times.
Also, many times, good things have come. We make mistakes from time to time.
But that should not stop us from making changes, IMO. If we are too afraid to
cha
"Asger Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| Also, it is a safe change. The two main existing LyX-server applications are
| unaffected, and we have the perspective of getting many more LyX server
| applications with a Perl module.
bla bla safe change bla bla... how many times have we s
"Asger Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
[line length Asger...]
| I understand that 1.0.3 is important because 1.0.2 is bugged. So release 1.0.3
| now as it is, and we'll have more time to consider the lyx-server-stuff for
| 1.0.4 when we have the patch. 1.0.4 will require a long de
Alejandro Aguilar Sierra <[EMAIL PROTECTED]> writes:
| On 1 Jun 1999, Lars Gullik Bjønnes wrote:
|
| > I must say that I am very reluctant to all/any changes to the
| > lyxserver code in LyX 1.0.x.
|
| Unless it is considered a bug fix, right?
We should be very restrictive on what we call a bu
On 1 Jun 1999, Lars Gullik Bjønnes wrote:
> I must say that I am very reluctant to all/any changes to the
> lyxserver code in LyX 1.0.x.
Unless it is considered a bug fix, right?
> I'd much rather see a totally new and thought through lyxserver in
> 1.1.x.^^
Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
| > Too few people have used the server, so any fresh discussion about it is
| > useful. Be free to improve it, while that doesn't imply a radical change
| > of protocol for LyX 1.0.x.
| >
| > Alejandro
| >
|
| Ok, I'll give it a try!
| cheers,
|
> > Ok, I just volunteered to change the server code... but I do not know
> > what is best to do now. I suppose changing the protocol now would break
> > Barracuda... I can't find mentions to lyx in the barracuda 1.0.3 src
> > though... is it in a development version?
>
> It's in a patch apparen
On Tue, 1 Jun 1999, Stefano Ghirlanda wrote:
> Ok, I just volunteered to change the server code... but I do not know
> what is best to do now. I suppose changing the protocol now would break
> Barracuda... I can't find mentions to lyx in the barracuda 1.0.3 src
> though... is it in a development
> On Tue, 1 Jun 1999, Stefano Ghirlanda wrote:
>
> > thanks, I have looked into these. However, it *seems* to me, from a
> > cursory inspection in the code, that neither program every reads from
> > .lyxpipe.out, they only write requests to the input pipe... changing
> > the protocol will not aff
On Tue, 1 Jun 1999, Stefano Ghirlanda wrote:
> thanks, I have looked into these. However, it *seems* to me, from a
> cursory inspection in the code, that neither program every reads from
> .lyxpipe.out, they only write requests to the input pipe... changing
> the protocol will not affect these tw
Hi everyone,
> Don't put too much credit to the documentation :-)
> I know it might have bugs, because I rewrote most of it when I cleaned up the
> LyX server, and before I did that, the documentation for sure had lots of bugs.
> ;-)
>
> But, if gBib and the tclBib tool does not rely on the pi
> What I gathered upon first reading of the Lyx Server chapter in the
> customization docs was indeed that a message was always issued to notify
> clients. From that document:
>
>
> "The answer from LyX will arrive in the output pipe a
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
Lars> What do you think?
Lars> I think no. Let's work on making a really good lyxserver in 1.1.
Lars> instead of muddling on with the limited server in 1.0.
It just means rem
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
| What do you think?
I think no. Let's work on making a really good lyxserver in 1.1.
instead of muddling on with the limited server in 1.0.
Lgb
Stephan Witt <[EMAIL PROTECTED]> writes:
| Using a socket is a very elegant solution, but you have to
| create a robust and reliable security scheme too. LyX tends
| to modify files :) and there is a real security hole if the
| running LyX-Server is open to the whole world to assist in
| modifyin
Hi again,
> Asger> You could do a hack: Send a command to LyX that has no ill
> Asger> side-effects, but returns something (like where the cursor is),
> Asger> and if you get the result immediately, you know that the
> Asger> previous command succeeded. Actually, this trick could spare
> Asger>
Hi again,
> > This would be perfectly ok for me. BTW, since you speak of backward
> > compatibility, I assume that people have written other lyx clients (apart
> > from servermonitor.c in the lyx sources). I would like very much to see
> > the code of some of them so I can improve my code, e.g. w
> "Asger" == Asger Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>> Otherwise, I could simply conform to what the lyxserver does now,
>> i.e. not writing anything in the out pipe if a command that returns
>> no data succeeds. In this case, I do not fully understand how to
>> check wheter a comm
> This would be perfectly ok for me. BTW, since you speak of backward
> compatibility, I assume that people have written other lyx clients (apart
> from servermonitor.c in the lyx sources). I would like very much to see
> the code of some of them so I can improve my code, e.g. when it comes to
> e
Hi,
On Mon, 31 May 1999, Asger Alstrup Nielsen wrote:
> > Concerning the thought part below, I just reproduced it so that others
> > can comment on it. Personnally, I agree that some message should be
> > returned on success, but there may be some applications which rely on
> > the fact that not
Lars Gullik Bjønnes wrote:
>
> "Asger Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
>
> | In order to keep backwards compatibility, we can just introduce a certain
> | command that will enable the "error messages" on success.
>
> I think we should not keep backwards compatibility for the lyxserv
> I think we should not keep backwards compatibility for the lyxserver.
> We need to think out a decent protocol with commands _and_ responses.
> Also we should switch to using sockets instead of namedpipes.
Agreed, but only for 1.1.x. And therefore, for 1.0.x, I think we should just
do a hack t
> Concerning the thought part below, I just reproduced it so that others
> can comment on it. Personnally, I agree that some message should be
> returned on success, but there may be some applications which rely on
> the fact that nothing is returned.
>
> So, fellow developpers, any idea?
In ord
"Asger Alstrup Nielsen" <[EMAIL PROTECTED]> writes:
| In order to keep backwards compatibility, we can just introduce a certain
| command that will enable the "error messages" on success.
I think we should not keep backwards compatibility for the lyxserver.
We need to think out a decent protocol
> "Stefano" == Stefano Ghirlanda <[EMAIL PROTECTED]> writes:
Stefano> Hi Jean-Marc, this is about the "idea" project. I have been
Stefano> working on a perl module, Lyx::Comm, handling communication
Stefano> with Lyx. For example:
Stefano> my $lyx = Lyx::Comm->new(client => "Idea");
Stefano>
73 matches
Mail list logo
