What are the details of the python installation that comes with the LyX 2.0
Windows binary?
I'm the author of LyXBlogger, which runs on Python and requires the "socket"
module. But LyXBlogger is failing when run from the Python that comes in the
LyX 2.0 Windows binary.
on xforms,qt and gtk.
I used the same trick in gtk as is used in qt.
This should even make the unix socket based server work for gtk, it
didn't earlier you know... (as in ever)
So unless I get objections this is going in.
? Config
? counter-2.diff
? counter-3.diff
? counter.diff
? deptherror
On Wed, Jul 21, 2004 at 10:58:27PM +0200, Lars Gullik Bj?nnes wrote:
> the pipe fd is registered with the qt event loop with the
> QSocketNotifier.
I thought your patch deleted all of that. OK
john
John Levon <[EMAIL PROTECTED]> writes:
| On Wed, Jul 21, 2004 at 10:02:44PM +0200, Lars Gullik Bj?nnes wrote:
>
>> | So far only compiled on xforms, will test qt as well before
>> | committing... I might skip on gtk.
>>
>> Updated a bit.
>
| Now that Qt has no notion of these pipes, how will we b
On Wed, Jul 21, 2004 at 10:02:44PM +0200, Lars Gullik Bj?nnes wrote:
> | So far only compiled on xforms, will test qt as well before
> | committing... I might skip on gtk.
>
> Updated a bit.
Now that Qt has no notion of these pipes, how will we break out of the
Qt event loop when an fd becomes r
Lars Gullik Bjønnes wrote:
> The changes I did with lyxsocket, can very well be used by the
> lyxserver as well.
>
> This patch does that.
>
> So far only compiled on xforms, will test qt as well before
> committing... I might skip on gtk.
Please don't. If you start a project then at least try
9:58:06 -
@@ -95,16 +95,15 @@ void update_fonts();
bool font_available(LyXFont const & font);
/**
- * add a callback for I/O read notification
+ * add a callback for socket read notification
+ * @param fd socket descriptor (file/socket/etc)
*/
-void set_read_callback(int fd, LyXComm * co
rieving revision 1.25
diff -u -p -r1.25 lyx_gui.h
--- src/frontends/lyx_gui.h 21 Jul 2004 19:03:20 - 1.25
+++ src/frontends/lyx_gui.h 21 Jul 2004 19:44:46 -
@@ -95,16 +95,15 @@ void update_fonts();
bool font_available(LyXFont const & font);
/**
- * add a callback for I/O read notificatio
14 00:16:47
@@ -1,3 +1,7 @@
+2003-10-13 João Luis Meloni Assirati <[EMAIL PROTECTED]>
+
+ * socktools.[Ch]: New files. Wrapper around socket system calls.
+
2003-10-08 Angus Leeming <[EMAIL PROTECTED]>
* copied_ptr.h: get rid of the swap member function.
On Mon, 13 Oct 2003, Jean-Marc Lasgouttes wrote:
> > "Joao" == Joao Luis Meloni Assirati <[EMAIL PROTECTED]> writes:
>
> Joao> For me it is no problem, but I remember people saying that /home
> Joao> is not a good place to put fifos and sockets because it can be
> Joao> an afs or other restri
On Mon, 13 Oct 2003, Joao Luis Meloni Assirati wrote:
> Or simply
>
> ./lyxclient 'LYXCMD:file-open /home/angus/docs/transform_v2.lyx'
>
> if you have only one lyx runing, as the client will search for a running
> lyx.
Ooops... I mean
./lyxclient -c 'file-open /home/angus/docs/transform_v2.lyx
On Mon, 13 Oct 2003, Lars Gullik Bjønnes wrote:
> | It relies only in permission bits. That is, it tries all lyx_tmpdir...,
> | and stays with the first it can connect. Of course it cannot connet to a
> | socket that is under a closed directory. The socket itself is created
> | clos
nect. Of course it cannot connet to a
| socket that is under a closed directory. The socket itself is created
| closed for other users.
Will it then continue the search? (or is that how it searches?)
(I know I could just look at the code...)
--
Lgb
On Mon, 13 Oct 2003, Lars Gullik Bjønnes wrote:
> Is the check clever enough? What about multiuser boxes?
It relies only in permission bits. That is, it tries all lyx_tmpdir...,
and stays with the first it can connect. Of course it cannot connet to a
socket that is under a closed direct
Joao Luis Meloni Assirati <[EMAIL PROTECTED]> writes:
| On Mon, 13 Oct 2003, Angus Leeming wrote:
>
>> Pass commands to lyx:
>> ./lyxclient -a /tmp/lyx_tmpdir222460OMx2d/lyxsocket -c
>> 'LYXCMD:file-open /home/angus/docs/transform_v2.lyx'
>
| Or simply
>
| ./lyxclient 'LYXCMD:file-open /home/angus
> "Joao" == Joao Luis Meloni Assirati <[EMAIL PROTECTED]> writes:
Joao> For me it is no problem, but I remember people saying that /home
Joao> is not a good place to put fifos and sockets because it can be
Joao> an afs or other restrictive filesystem mount. So, looking at all
Joao> other progr
On Mon, 13 Oct 2003, Angus Leeming wrote:
> Pass commands to lyx:
> ./lyxclient -a /tmp/lyx_tmpdir222460OMx2d/lyxsocket -c
> 'LYXCMD:file-open /home/angus/docs/transform_v2.lyx'
Or simply
./lyxclient 'LYXCMD:file-open /home/angus/docs/transform_v2.lyx'
if you have only one lyx runing, as the
p was the best place.
Also, I don't thik it is a good thing having a dead socket in .lyx
each time lyx crashes.
So, I don't see a good reason to change that.
Regards,
Joao.
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | Joao Luis Meloni Assirati wrote:
>>> I wrote a simple local socket interface for lyx that compiles and
>>> runs well in Linux with gcc 3.3 (Debian unstable) with the purpose
>>
Angus Leeming <[EMAIL PROTECTED]> writes:
| Joao Luis Meloni Assirati wrote:
>> I wrote a simple local socket interface for lyx that compiles and
>> runs well in Linux with gcc 3.3 (Debian unstable) with the purpose
>> of getting inverse dvi search working, for witch I wi
Joao Luis Meloni Assirati wrote:
> I wrote a simple local socket interface for lyx that compiles and
> runs well in Linux with gcc 3.3 (Debian unstable) with the purpose
> of getting inverse dvi search working, for witch I will send a patch
> in my next e-mail.
Dear Joao, I attach th
On Mon, Oct 13, 2003 at 11:53:40AM +0200, Andre' Poenitz wrote:
> I was about asking
'about to ask' I suppose...
Andre'
On Mon, Oct 13, 2003 at 10:26:46AM +, Angus Leeming wrote:
> Joao Luis Meloni Assirati wrote:
> > On Wed, 8 Oct 2003, Angus Leeming wrote:
> >
> >> Of course, there are lots of small coding points,
> >
> > It is not a surprise :). If there is a chance of my patch being
> > accepted, I would b
or developing lyx!
>>
> | I am going to commit this patch as-is unless someone speaks up
> | soon.
>
> Are there mac/win/osx issues with this?
Probably, but we should get it into the tree in my opinion. It is a
huge step in the right direction.
> How does the socket code comp
going to commit this patch as-is unless someone speaks up soon.
Are there mac/win/osx issues with this?
How does the socket code compare to this:
(Some old code I planned to base the socket support in lyx on, never
got the time...) (and as you can see this is for tcp, but similar
interf
Joao Luis Meloni Assirati wrote:
> On Wed, 8 Oct 2003, Angus Leeming wrote:
>
>> Of course, there are lots of small coding points,
>
> It is not a surprise :). If there is a chance of my patch being
> accepted, I would be glad to correct them. Note also that
> lyxclient.C is still sort of prelimi
On Wed, 8 Oct 2003, Angus Leeming wrote:
> Of course, there are lots of small coding points,
It is not a surprise :). If there is a chance of my patch being accepted,
I would be glad to correct them. Note also that lyxclient.C is still sort
of preliminary. My concern was mainly the patch.
> So
wledge. I also like the way that you have split the
details of socket communication out of LyXSocketServer. It suggests
that it will be pretty easy to move to a platform-independent
solution once the boost socket library matures.
Of course, there are lots of small coding points, but I thoug
Hello,
I wrote a simple local socket interface for lyx that compiles and runs
well in Linux with gcc 3.3 (Debian unstable) with the purpose of getting
inverse dvi search working, for witch I will send a patch in my next
e-mail.
It consists of two classes:
LyXDataSocket - this class has a
I've just been reading the documentation of the socketstream library.
http://members.aon.at/hstraub/linux/socket++/docu/socket++.html#SEC_Top
It looks very powerful. Chapter 9 seams to describe exactly what we
are looking for, both for lyxserver (socketpair) and for
communication with t
30 matches
Mail list logo