>>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:

Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes: |
Lars> >>>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> | 
Lars> | Lars> Joao Luis Meloni Assirati <[EMAIL PROTECTED]>
Lars> writes:
Lars> | Lars> | On 11 Mar 2003, Lars Gullik Bjønnes wrote:
Lars> | Lars> | 
Lars> | Lars> | > Jean-Marc Lasgouttes <[EMAIL PROTECTED]>
Lars> writes: | Lars> | > | Why? "lyx -client <cmd> <args>" is nice
Lars> too. It has to | Lars> share code with | > | lyx (read prefs,
Lars> for example) anyway.
Lars> | Lars> | >
Lars> | Lars> | > No, it doesn't have to do that.
Lars> | Lars> | 
Lars> | Lars> | How can I know where are lyxpipes?
Lars> | 
Lars> | Lars> We should remove the config options of being able to set
Lars> the | Lars> pipe names. Then the pipes can always be found in
Lars> the same spot.
Lars> | 
Lars> | OK, I am running under afs, so I cannot create a pipe in my
Lars> home dir. | Am I also in the family of people we do not want to
Lars> support?

Lars> Then perhaps we should create our pipes and sockets in a
Lars> different places as standard. (/tmp/)

/tmp seems to be a reasonable place indeed. I guess this is what the
directories like /tmp/.X11-unix or /tmp/mcop-foo do, no?

Lars> I'd also like to know what other applications that has a similar
Lars> facility does. Or are they just not working on afs?
 
If you could cite a few apps, I would try to know.

Lars>         - bloat (sounds strange comming from me doesn't it?) 
Lars>         - server/client separation
        
Lars> I might be swayed, but then the whole client handling in lyx
Lars> needs to be moved our into its own "subsystem".

The idea I had was to change the curent parsing of args to actually
build a list of lfuns to run (create lfuns for file loading,
exporting, etc.) and then depending on the -client tag (or rather
-remote) dispatch it to either the normal lyxfunc, or a special
lyxfunc which will just send the lfuns through the pipe.

So something like
  lyx --remote --export latex foo.lyx
would just work (although I do not claim that it is useful :)

The only point that worries me actually is the problem of speed.

JMarc

Reply via email to