Re: plyx

[Wolfgang Engelmann]

On Wednesday 29 January 2014 22:38:53 Andrew Parsloe wrote:
 On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:
  On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
  
  Andrew recommended to useplyx for eg exchanging globally in a lyx
  document the location of the figure paths (e.g. from something to ./)
  
  I have tried to install the plyx/qlyx
  
  and havethis problem:
  
  I followed
  
  Chapter 2 Putting the pieces in their places
  
  1.Specifically: (a-e)
  
  2.File formats (a)
  
  in trying to do (b):
  
  Similarly create a new file format qLyX, short name qlyx, extension
  lyx; none of the other check boxes or slots need to be filled. Click
  Apply.
  
  I was asked to reconfigure, which I did. However, I had lyx in the
  left/right view with the instructions what to do on the left and the
  new pLyX.lyx to the right. I probably made a mistake in not closing
  the left side before reconfiguring. When I restarted lyx, I got at
  the left upper menu line just below Datei (File ) and Bearbeitentwo
  wheels with a black bar going through them.
  
  This happens with each new start of lyx with this warning on the
  terminal
  
  we@wolfgang:~$ Fontconfig warning:
  /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having
  multiple values in test isn't supported and may not work as
  expected
  
  Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line
  138: Having multiple values in test isn't supported and may not 
work
  as expected
  
  LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
  
  If no other LyX program is active, please delete the pipe by hand and
  try again.
  
  However, there is no
  
  Pipe /home/we/.lyx/lyxpipe
  
  which I could delete.
  
  Note that the Fontconfig warnings I had before and didn't bother 
about
  them, because they do not seem to affect the working with LyX.
  
  How do I get rid of this? Do I have to install lyx anew?
  
  Andrew, perhaps a note about the reconfigure after the plyx creation
  before the qlyx creation would be good and a warning, to close first
  the second lyx file before reconfiguring, if this is indeed the
  reason for the error.
  
  Wolfgang
 
 I'm sorry this has become messy, Wolfgang. I didn't anticipate left and
 right screen views being open while putting the pieces in their places,
 although it is clearly convenient to do so. However, I've just tried
 reconfiguring with left and right views open, and it proceeded without
 problems (on my Windows 7 machine).
 
 The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from
 other threads) that you have a LyX installation that you've compiled
 yourself? Perhaps you should remove all pLyX stuff and try reconfiguring
 after that. Then, if you wish, start again.
 
 Andrew

Thanks, Andrew,

I am on Debian (Linux). My assumption that the strange appearance 
(see my screen shot of the upper left LyX menu bar) was a result of 
the lyxpipe warning was wrong, since I do not get this anymore. However, 
the strange appearance is found whenever I start LyX.
If it does not interfere with my working with LyX, I don't mind. But its 
strange...

Wolfgang
attachment: Bildschirmphoto11.png

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 9:16 AM, Wolfgang Engelmann
engelm...@uni-tuebingen.de wrote:
 On Wednesday 29 January 2014 22:38:53 Andrew Parsloe wrote:

 On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:

  On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:

 

  Andrew recommended to useplyx for eg exchanging globally in a lyx

  document the location of the figure paths (e.g. from something to ./)

 

  I have tried to install the plyx/qlyx

 

  and havethis problem:

 

  I followed

 

  Chapter 2 Putting the pieces in their places

 

  1.Specifically: (a-e)

 

  2.File formats (a)

 

  in trying to do (b):

 

  Similarly create a new file format qLyX, short name qlyx, extension

  lyx; none of the other check boxes or slots need to be filled. Click

  Apply.

 

  I was asked to reconfigure, which I did. However, I had lyx in the

  left/right view with the instructions what to do on the left and the

  new pLyX.lyx to the right. I probably made a mistake in not closing

  the left side before reconfiguring. When I restarted lyx, I got at

  the left upper menu line just below Datei (File ) and Bearbeitentwo

  wheels with a black bar going through them.

 

  This happens with each new start of lyx with this warning on the

  terminal

 

  we@wolfgang:~$ Fontconfig warning:

  /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having

  multiple values in test isn't supported and may not work as

  expected

 

  Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line

  138: Having multiple values in test isn't supported and may not work

  as expected

 

  LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.

 

  If no other LyX program is active, please delete the pipe by hand and

  try again.

 

  However, there is no

 

  Pipe /home/we/.lyx/lyxpipe

 

  which I could delete.

 

  Note that the Fontconfig warnings I had before and didn't bother about

  them, because they do not seem to affect the working with LyX.

 

  How do I get rid of this? Do I have to install lyx anew?

 

  Andrew, perhaps a note about the reconfigure after the plyx creation

  before the qlyx creation would be good and a warning, to close first

  the second lyx file before reconfiguring, if this is indeed the

  reason for the error.

 

  Wolfgang



 I'm sorry this has become messy, Wolfgang. I didn't anticipate left and

 right screen views being open while putting the pieces in their places,

 although it is clearly convenient to do so. However, I've just tried

 reconfiguring with left and right views open, and it proceeded without

 problems (on my Windows 7 machine).



 The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from

 other threads) that you have a LyX installation that you've compiled

 yourself? Perhaps you should remove all pLyX stuff and try reconfiguring

 after that. Then, if you wish, start again.



 Andrew



 Thanks, Andrew,



 I am on Debian (Linux). My assumption that the strange appearance (see my
 screen shot of the upper left LyX menu bar) was a result of the lyxpipe
 warning was wrong, since I do not get this anymore. However, the strange
 appearance is found whenever I start LyX.

 If it does not interfere with my working with LyX, I don't mind. But its
 strange...

It is strange. Did you try a different theme?

Liviu



 Wolfgang



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:

 
 It is strange. Did you try a different theme?

This strange double-wheel adding to the upper left corner of the LyX frame  
is completely independent of the lyx files and themes I load. 
But I can live with it...

Wolfgang

 
 Liviu

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
engelm...@uni-tuebingen.de wrote:
 On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:





 It is strange. Did you try a different theme?



 This strange double-wheel adding to the upper left corner of the LyX frame
 is completely independent of the lyx files and themes I load.

I was actually thinking about the DE theme. Which DE are you using?
And did you try a different one?

Liviu


 But I can live with it...



 Wolfgang





 Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
 On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
 
 engelm...@uni-tuebingen.de wrote:
  On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
  It is strange. Did you try a different theme?
  
  This strange double-wheel adding to the upper left corner of the LyX
  frame is completely independent of the lyx files and themes I load.
 
 I was actually thinking about the DE theme. Which DE are you using?
 And did you try a different one?
 DE theme: sorry, I don't know what you mean

Wolfgang
 
 Liviu

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 1:56 PM, Wolfgang Engelmann
engelm...@uni-tuebingen.de wrote:
 On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:

 On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann



 engelm...@uni-tuebingen.de wrote:

  On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:

  It is strange. Did you try a different theme?

 

  This strange double-wheel adding to the upper left corner of the LyX

  frame is completely independent of the lyx files and themes I load.



 I was actually thinking about the DE theme. Which DE are you using?

 And did you try a different one?

 DE theme: sorry, I don't know what you mean

Desktop Environment. Actually Qt or Gtk, or however your system is set
up. On Xfce there is Settings  Appearance  Style. Of course,
assuming that you are using Linux.

Liviu




 Wolfgang



 Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Jean-Marc Lasgouttes]

30/01/2014 09:16, Wolfgang Engelmann:

I am on Debian (Linux). My assumption that the strange appearance (see
my screen shot of the upper left LyX menu bar) was a result of the
lyxpipe warning was wrong, since I do not get this anymore. However, the
strange appearance is found whenever I start LyX.

If it does not interfere with my working with LyX, I don't mind. But its
strange...


This looks like the old bug about new toolbars showing up at weird 
places. I think this is will go away with a clean session. Try removing 
~/.config/LyX/lyx.conf (or a different name if LyX was built with 
version suffix).


JMarc

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 14:54:07 Jean-Marc Lasgouttes wrote:
 30/01/2014 09:16, Wolfgang Engelmann:
  I am on Debian (Linux). My assumption that the strange appearance 
(see
  my screen shot of the upper left LyX menu bar) was a result of the
  lyxpipe warning was wrong, since I do not get this anymore. However,
  the strange appearance is found whenever I start LyX.
  
  If it does not interfere with my working with LyX, I don't mind. But
  its strange...
 
 This looks like the old bug about new toolbars showing up at weird
 places. I think this is will go away with a clean session. Try removing
 ~/.config/LyX/lyx.conf (or a different name if LyX was built with
 version suffix).
 
 JMarc

Yes, after renaming lyx.conf to lyx.conf.x the weird toolbar disappeared. 
However, even after reconfigure no new  lyx.conf was created. Might come 
after rebooting?
Thanks, 

Wolfgang

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 14:19:17 Liviu Andronic wrote:
 On Thu, Jan 30, 2014 at 1:56 PM, Wolfgang Engelmann
 
 engelm...@uni-tuebingen.de wrote:
  On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
  On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
  
  engelm...@uni-tuebingen.de wrote:
   On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
   It is strange. Did you try a different theme?
   
   This strange double-wheel adding to the upper left corner of the
   LyX
   
   frame is completely independent of the lyx files and themes I load.
  
  I was actually thinking about the DE theme. Which DE are you using?
  
  And did you try a different one?
  
  DE theme: sorry, I don't know what you mean
 
 Desktop Environment. Actually Qt or Gtk, or however your system is set
 up. On Xfce there is Settings  Appearance  Style. Of course,
 assuming that you are using Linux.

I am using Debian and KDE, so Qt, I guess. 

Haven't tried another one.

Wolfgang

Re: plyx

[Jean-Marc Lasgouttes]

30/01/2014 15:16, Wolfgang Engelmann:

Yes, after renaming lyx.conf to lyx.conf.x the weird toolbar
disappeared. However, even after reconfigure no new lyx.conf was
created. Might come after rebooting?


It should be created when quitting LyX. This is the place that stores 
toolbar positions, window size and other GUI-related things.


JMarc

Re: plyx

[Wolfgang Engelmann]

On Wednesday 29 January 2014 22:38:53 Andrew Parsloe wrote:
 On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:
  On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
  
  Andrew recommended to useplyx for eg exchanging globally in a lyx
  document the location of the figure paths (e.g. from something to ./)
  
  I have tried to install the plyx/qlyx
  
  and havethis problem:
  
  I followed
  
  Chapter 2 Putting the pieces in their places
  
  1.Specifically: (a-e)
  
  2.File formats (a)
  
  in trying to do (b):
  
  Similarly create a new file format qLyX, short name qlyx, extension
  lyx; none of the other check boxes or slots need to be filled. Click
  Apply.
  
  I was asked to reconfigure, which I did. However, I had lyx in the
  left/right view with the instructions what to do on the left and the
  new pLyX.lyx to the right. I probably made a mistake in not closing
  the left side before reconfiguring. When I restarted lyx, I got at
  the left upper menu line just below Datei (File ) and Bearbeitentwo
  wheels with a black bar going through them.
  
  This happens with each new start of lyx with this warning on the
  terminal
  
  we@wolfgang:~$ Fontconfig warning:
  /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having
  multiple values in test isn't supported and may not work as
  expected
  
  Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line
  138: Having multiple values in test isn't supported and may not 
work
  as expected
  
  LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
  
  If no other LyX program is active, please delete the pipe by hand and
  try again.
  
  However, there is no
  
  Pipe /home/we/.lyx/lyxpipe
  
  which I could delete.
  
  Note that the Fontconfig warnings I had before and didn't bother 
about
  them, because they do not seem to affect the working with LyX.
  
  How do I get rid of this? Do I have to install lyx anew?
  
  Andrew, perhaps a note about the reconfigure after the plyx creation
  before the qlyx creation would be good and a warning, to close first
  the second lyx file before reconfiguring, if this is indeed the
  reason for the error.
  
  Wolfgang
 
 I'm sorry this has become messy, Wolfgang. I didn't anticipate left and
 right screen views being open while putting the pieces in their places,
 although it is clearly convenient to do so. However, I've just tried
 reconfiguring with left and right views open, and it proceeded without
 problems (on my Windows 7 machine).
 
 The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from
 other threads) that you have a LyX installation that you've compiled
 yourself? Perhaps you should remove all pLyX stuff and try reconfiguring
 after that. Then, if you wish, start again.
 
 Andrew

Thanks, Andrew,

I am on Debian (Linux). My assumption that the strange appearance 
(see my screen shot of the upper left LyX menu bar) was a result of 
the lyxpipe warning was wrong, since I do not get this anymore. However, 
the strange appearance is found whenever I start LyX.
If it does not interfere with my working with LyX, I don't mind. But its 
strange...

Wolfgang
attachment: Bildschirmphoto11.png

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 9:16 AM, Wolfgang Engelmann
engelm...@uni-tuebingen.de wrote:
 On Wednesday 29 January 2014 22:38:53 Andrew Parsloe wrote:

 On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:

  On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:

 

  Andrew recommended to useplyx for eg exchanging globally in a lyx

  document the location of the figure paths (e.g. from something to ./)

 

  I have tried to install the plyx/qlyx

 

  and havethis problem:

 

  I followed

 

  Chapter 2 Putting the pieces in their places

 

  1.Specifically: (a-e)

 

  2.File formats (a)

 

  in trying to do (b):

 

  Similarly create a new file format qLyX, short name qlyx, extension

  lyx; none of the other check boxes or slots need to be filled. Click

  Apply.

 

  I was asked to reconfigure, which I did. However, I had lyx in the

  left/right view with the instructions what to do on the left and the

  new pLyX.lyx to the right. I probably made a mistake in not closing

  the left side before reconfiguring. When I restarted lyx, I got at

  the left upper menu line just below Datei (File ) and Bearbeitentwo

  wheels with a black bar going through them.

 

  This happens with each new start of lyx with this warning on the

  terminal

 

  we@wolfgang:~$ Fontconfig warning:

  /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having

  multiple values in test isn't supported and may not work as

  expected

 

  Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line

  138: Having multiple values in test isn't supported and may not work

  as expected

 

  LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.

 

  If no other LyX program is active, please delete the pipe by hand and

  try again.

 

  However, there is no

 

  Pipe /home/we/.lyx/lyxpipe

 

  which I could delete.

 

  Note that the Fontconfig warnings I had before and didn't bother about

  them, because they do not seem to affect the working with LyX.

 

  How do I get rid of this? Do I have to install lyx anew?

 

  Andrew, perhaps a note about the reconfigure after the plyx creation

  before the qlyx creation would be good and a warning, to close first

  the second lyx file before reconfiguring, if this is indeed the

  reason for the error.

 

  Wolfgang



 I'm sorry this has become messy, Wolfgang. I didn't anticipate left and

 right screen views being open while putting the pieces in their places,

 although it is clearly convenient to do so. However, I've just tried

 reconfiguring with left and right views open, and it proceeded without

 problems (on my Windows 7 machine).



 The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from

 other threads) that you have a LyX installation that you've compiled

 yourself? Perhaps you should remove all pLyX stuff and try reconfiguring

 after that. Then, if you wish, start again.



 Andrew



 Thanks, Andrew,



 I am on Debian (Linux). My assumption that the strange appearance (see my
 screen shot of the upper left LyX menu bar) was a result of the lyxpipe
 warning was wrong, since I do not get this anymore. However, the strange
 appearance is found whenever I start LyX.

 If it does not interfere with my working with LyX, I don't mind. But its
 strange...

It is strange. Did you try a different theme?

Liviu



 Wolfgang



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:

 
 It is strange. Did you try a different theme?

This strange double-wheel adding to the upper left corner of the LyX frame  
is completely independent of the lyx files and themes I load. 
But I can live with it...

Wolfgang

 
 Liviu

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
engelm...@uni-tuebingen.de wrote:
 On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:





 It is strange. Did you try a different theme?



 This strange double-wheel adding to the upper left corner of the LyX frame
 is completely independent of the lyx files and themes I load.

I was actually thinking about the DE theme. Which DE are you using?
And did you try a different one?

Liviu


 But I can live with it...



 Wolfgang





 Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
 On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
 
 engelm...@uni-tuebingen.de wrote:
  On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
  It is strange. Did you try a different theme?
  
  This strange double-wheel adding to the upper left corner of the LyX
  frame is completely independent of the lyx files and themes I load.
 
 I was actually thinking about the DE theme. Which DE are you using?
 And did you try a different one?
 DE theme: sorry, I don't know what you mean

Wolfgang
 
 Liviu

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 1:56 PM, Wolfgang Engelmann
engelm...@uni-tuebingen.de wrote:
 On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:

 On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann



 engelm...@uni-tuebingen.de wrote:

  On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:

  It is strange. Did you try a different theme?

 

  This strange double-wheel adding to the upper left corner of the LyX

  frame is completely independent of the lyx files and themes I load.



 I was actually thinking about the DE theme. Which DE are you using?

 And did you try a different one?

 DE theme: sorry, I don't know what you mean

Desktop Environment. Actually Qt or Gtk, or however your system is set
up. On Xfce there is Settings  Appearance  Style. Of course,
assuming that you are using Linux.

Liviu




 Wolfgang



 Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Jean-Marc Lasgouttes]

30/01/2014 09:16, Wolfgang Engelmann:

I am on Debian (Linux). My assumption that the strange appearance (see
my screen shot of the upper left LyX menu bar) was a result of the
lyxpipe warning was wrong, since I do not get this anymore. However, the
strange appearance is found whenever I start LyX.

If it does not interfere with my working with LyX, I don't mind. But its
strange...


This looks like the old bug about new toolbars showing up at weird 
places. I think this is will go away with a clean session. Try removing 
~/.config/LyX/lyx.conf (or a different name if LyX was built with 
version suffix).


JMarc

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 14:54:07 Jean-Marc Lasgouttes wrote:
 30/01/2014 09:16, Wolfgang Engelmann:
  I am on Debian (Linux). My assumption that the strange appearance 
(see
  my screen shot of the upper left LyX menu bar) was a result of the
  lyxpipe warning was wrong, since I do not get this anymore. However,
  the strange appearance is found whenever I start LyX.
  
  If it does not interfere with my working with LyX, I don't mind. But
  its strange...
 
 This looks like the old bug about new toolbars showing up at weird
 places. I think this is will go away with a clean session. Try removing
 ~/.config/LyX/lyx.conf (or a different name if LyX was built with
 version suffix).
 
 JMarc

Yes, after renaming lyx.conf to lyx.conf.x the weird toolbar disappeared. 
However, even after reconfigure no new  lyx.conf was created. Might come 
after rebooting?
Thanks, 

Wolfgang

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 14:19:17 Liviu Andronic wrote:
 On Thu, Jan 30, 2014 at 1:56 PM, Wolfgang Engelmann
 
 engelm...@uni-tuebingen.de wrote:
  On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
  On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
  
  engelm...@uni-tuebingen.de wrote:
   On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
   It is strange. Did you try a different theme?
   
   This strange double-wheel adding to the upper left corner of the
   LyX
   
   frame is completely independent of the lyx files and themes I load.
  
  I was actually thinking about the DE theme. Which DE are you using?
  
  And did you try a different one?
  
  DE theme: sorry, I don't know what you mean
 
 Desktop Environment. Actually Qt or Gtk, or however your system is set
 up. On Xfce there is Settings  Appearance  Style. Of course,
 assuming that you are using Linux.

I am using Debian and KDE, so Qt, I guess. 

Haven't tried another one.

Wolfgang

Re: plyx

[Jean-Marc Lasgouttes]

30/01/2014 15:16, Wolfgang Engelmann:

Yes, after renaming lyx.conf to lyx.conf.x the weird toolbar
disappeared. However, even after reconfigure no new lyx.conf was
created. Might come after rebooting?


It should be created when quitting LyX. This is the place that stores 
toolbar positions, window size and other GUI-related things.


JMarc

Re: plyx

[Wolfgang Engelmann]

On Wednesday 29 January 2014 22:38:53 Andrew Parsloe wrote:
> On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:
> > On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
> > 
> > Andrew recommended to useplyx for eg exchanging globally in a lyx
> > document the location of the figure paths (e.g. from something to ./)
> > 
> > I have tried to install the plyx/qlyx
> > 
> > and havethis problem:
> > 
> > I followed
> > 
> > Chapter 2 Putting the pieces in their places
> > 
> > 1.Specifically: (a-e)
> > 
> > 2.File formats (a)
> > 
> > in trying to do (b):
> > 
> > Similarly create a new file format qLyX, short name qlyx, extension
> > lyx; none of the other check boxes or slots need to be filled. Click
> > Apply.
> > 
> > I was asked to reconfigure, which I did. However, I had lyx in the
> > left/right view with the instructions what to do on the left and the
> > new pLyX.lyx to the right. I probably made a mistake in not closing
> > the left side before reconfiguring. When I restarted lyx, I got at
> > the left upper menu line just below Datei (File ) and Bearbeitentwo
> > wheels with a black bar going through them.
> > 
> > This happens with each new start of lyx with this warning on the
> > terminal
> > 
> > we@wolfgang:~$ Fontconfig warning:
> > "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having
> > multiple values in  isn't supported and may not work as
> > expected
> > 
> > Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line
> > 138: Having multiple values in  isn't supported and may not 
work
> > as expected
> > 
> > LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
> > 
> > If no other LyX program is active, please delete the pipe by hand and
> > try again.
> > 
> > However, there is no
> > 
> > Pipe /home/we/.lyx/lyxpipe
> > 
> > which I could delete.
> > 
> > Note that the Fontconfig warnings I had before and didn't bother 
about
> > them, because they do not seem to affect the working with LyX.
> > 
> > How do I get rid of this? Do I have to install lyx anew?
> > 
> > Andrew, perhaps a note about the reconfigure after the plyx creation
> > before the qlyx creation would be good and a warning, to close first
> > the second lyx file before reconfiguring, if this is indeed the
> > reason for the error.
> > 
> > Wolfgang
> 
> I'm sorry this has become messy, Wolfgang. I didn't anticipate left and
> right screen views being open while putting the pieces in their places,
> although it is clearly convenient to do so. However, I've just tried
> reconfiguring with left and right views open, and it proceeded without
> problems (on my Windows 7 machine).
> 
> The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from
> other threads) that you have a LyX installation that you've compiled
> yourself? Perhaps you should remove all pLyX stuff and try reconfiguring
> after that. Then, if you wish, start again.
> 
> Andrew

Thanks, Andrew,

I am on Debian (Linux). My assumption that the strange appearance 
(see my screen shot of the upper left LyX menu bar) was a result of 
the lyxpipe warning was wrong, since I do not get this anymore. However, 
the strange appearance is found whenever I start LyX.
If it does not interfere with my working with LyX, I don't mind. But its 
strange...

Wolfgang
<>

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 9:16 AM, Wolfgang Engelmann
<engelm...@uni-tuebingen.de> wrote:
> On Wednesday 29 January 2014 22:38:53 Andrew Parsloe wrote:
>
>> On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:
>
>> > On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
>
>> >
>
>> > Andrew recommended to useplyx for eg exchanging globally in a lyx
>
>> > document the location of the figure paths (e.g. from something to ./)
>
>> >
>
>> > I have tried to install the plyx/qlyx
>
>> >
>
>> > and havethis problem:
>
>> >
>
>> > I followed
>
>> >
>
>> > Chapter 2 Putting the pieces in their places
>
>> >
>
>> > 1.Specifically: (a-e)
>
>> >
>
>> > 2.File formats (a)
>
>> >
>
>> > in trying to do (b):
>
>> >
>
>> > Similarly create a new file format qLyX, short name qlyx, extension
>
>> > lyx; none of the other check boxes or slots need to be filled. Click
>
>> > Apply.
>
>> >
>
>> > I was asked to reconfigure, which I did. However, I had lyx in the
>
>> > left/right view with the instructions what to do on the left and the
>
>> > new pLyX.lyx to the right. I probably made a mistake in not closing
>
>> > the left side before reconfiguring. When I restarted lyx, I got at
>
>> > the left upper menu line just below Datei (File ) and Bearbeitentwo
>
>> > wheels with a black bar going through them.
>
>> >
>
>> > This happens with each new start of lyx with this warning on the
>
>> > terminal
>
>> >
>
>> > we@wolfgang:~$ Fontconfig warning:
>
>> > "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having
>
>> > multiple values in  isn't supported and may not work as
>
>> > expected
>
>> >
>
>> > Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line
>
>> > 138: Having multiple values in  isn't supported and may not work
>
>> > as expected
>
>> >
>
>> > LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
>
>> >
>
>> > If no other LyX program is active, please delete the pipe by hand and
>
>> > try again.
>
>> >
>
>> > However, there is no
>
>> >
>
>> > Pipe /home/we/.lyx/lyxpipe
>
>> >
>
>> > which I could delete.
>
>> >
>
>> > Note that the Fontconfig warnings I had before and didn't bother about
>
>> > them, because they do not seem to affect the working with LyX.
>
>> >
>
>> > How do I get rid of this? Do I have to install lyx anew?
>
>> >
>
>> > Andrew, perhaps a note about the reconfigure after the plyx creation
>
>> > before the qlyx creation would be good and a warning, to close first
>
>> > the second lyx file before reconfiguring, if this is indeed the
>
>> > reason for the error.
>
>> >
>
>> > Wolfgang
>
>>
>
>> I'm sorry this has become messy, Wolfgang. I didn't anticipate left and
>
>> right screen views being open while putting the pieces in their places,
>
>> although it is clearly convenient to do so. However, I've just tried
>
>> reconfiguring with left and right views open, and it proceeded without
>
>> problems (on my Windows 7 machine).
>
>>
>
>> The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from
>
>> other threads) that you have a LyX installation that you've compiled
>
>> yourself? Perhaps you should remove all pLyX stuff and try reconfiguring
>
>> after that. Then, if you wish, start again.
>
>>
>
>> Andrew
>
>
>
> Thanks, Andrew,
>
>
>
> I am on Debian (Linux). My assumption that the strange appearance (see my
> screen shot of the upper left LyX menu bar) was a result of the lyxpipe
> warning was wrong, since I do not get this anymore. However, the strange
> appearance is found whenever I start LyX.
>
> If it does not interfere with my working with LyX, I don't mind. But its
> strange...
>
It is strange. Did you try a different theme?

Liviu

>
>
> Wolfgang



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:

> 
> It is strange. Did you try a different theme?

This strange double-wheel adding to the upper left corner of the LyX frame  
is completely independent of the lyx files and themes I load. 
But I can live with it...

Wolfgang

> 
> Liviu

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
 wrote:
> On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
>
>
>
>>
>
>> It is strange. Did you try a different theme?
>
>
>
> This strange double-wheel adding to the upper left corner of the LyX frame
> is completely independent of the lyx files and themes I load.
>
I was actually thinking about the DE theme. Which DE are you using?
And did you try a different one?

Liviu


> But I can live with it...
>
>
>
> Wolfgang
>
>
>
>>
>
>> Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
> On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
> 
>  wrote:
> > On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
> >> It is strange. Did you try a different theme?
> > 
> > This strange double-wheel adding to the upper left corner of the LyX
> > frame is completely independent of the lyx files and themes I load.
> 
> I was actually thinking about the DE theme. Which DE are you using?
> And did you try a different one?
 DE theme: sorry, I don't know what you mean

Wolfgang
> 
> Liviu

Re: plyx

[Liviu Andronic]

On Thu, Jan 30, 2014 at 1:56 PM, Wolfgang Engelmann
 wrote:
> On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
>
>> On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
>
>>
>
>>  wrote:
>
>> > On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
>
>> >> It is strange. Did you try a different theme?
>
>> >
>
>> > This strange double-wheel adding to the upper left corner of the LyX
>
>> > frame is completely independent of the lyx files and themes I load.
>
>>
>
>> I was actually thinking about the DE theme. Which DE are you using?
>
>> And did you try a different one?
>
> DE theme: sorry, I don't know what you mean
>
Desktop Environment. Actually Qt or Gtk, or however your system is set
up. On Xfce there is Settings > Appearance > Style. Of course,
assuming that you are using Linux.

Liviu


>
>
> Wolfgang
>
>>
>
>> Liviu



-- 
Do you know how to read?
http://www.alienetworks.com/srtest.cfm
http://goodies.xfce.org/projects/applications/xfce4-dict#speed-reader
Do you know how to write?
http://garbl.home.comcast.net/~garbl/stylemanual/e.htm#e-mail

Re: plyx

[Jean-Marc Lasgouttes]

30/01/2014 09:16, Wolfgang Engelmann:

I am on Debian (Linux). My assumption that the strange appearance (see
my screen shot of the upper left LyX menu bar) was a result of the
lyxpipe warning was wrong, since I do not get this anymore. However, the
strange appearance is found whenever I start LyX.

If it does not interfere with my working with LyX, I don't mind. But its
strange...


This looks like the old bug about new toolbars showing up at weird 
places. I think this is will go away with a clean session. Try removing 
~/.config/LyX/lyx.conf (or a different name if LyX was built with 
version suffix).


JMarc

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 14:54:07 Jean-Marc Lasgouttes wrote:
> 30/01/2014 09:16, Wolfgang Engelmann:
> > I am on Debian (Linux). My assumption that the strange appearance 
(see
> > my screen shot of the upper left LyX menu bar) was a result of the
> > lyxpipe warning was wrong, since I do not get this anymore. However,
> > the strange appearance is found whenever I start LyX.
> > 
> > If it does not interfere with my working with LyX, I don't mind. But
> > its strange...
> 
> This looks like the old bug about new toolbars showing up at weird
> places. I think this is will go away with a clean session. Try removing
> ~/.config/LyX/lyx.conf (or a different name if LyX was built with
> version suffix).
> 
> JMarc

Yes, after renaming lyx.conf to lyx.conf.x the weird toolbar disappeared. 
However, even after reconfigure no new  lyx.conf was created. Might come 
after rebooting?
Thanks, 

Wolfgang

Re: plyx

[Wolfgang Engelmann]

On Thursday 30 January 2014 14:19:17 Liviu Andronic wrote:
> On Thu, Jan 30, 2014 at 1:56 PM, Wolfgang Engelmann
> 
>  wrote:
> > On Thursday 30 January 2014 11:24:39 Liviu Andronic wrote:
> >> On Thu, Jan 30, 2014 at 10:29 AM, Wolfgang Engelmann
> >> 
> >>  wrote:
> >> > On Thursday 30 January 2014 10:00:39 Liviu Andronic wrote:
> >> >> It is strange. Did you try a different theme?
> >> > 
> >> > This strange double-wheel adding to the upper left corner of the
> >> > LyX
> >> > 
> >> > frame is completely independent of the lyx files and themes I load.
> >> 
> >> I was actually thinking about the DE theme. Which DE are you using?
> >> 
> >> And did you try a different one?
> > 
> > DE theme: sorry, I don't know what you mean
> 
> Desktop Environment. Actually Qt or Gtk, or however your system is set
> up. On Xfce there is Settings > Appearance > Style. Of course,
> assuming that you are using Linux.

I am using Debian and KDE, so Qt, I guess. 

Haven't tried another one.

Wolfgang

Re: plyx

[Jean-Marc Lasgouttes]

30/01/2014 15:16, Wolfgang Engelmann:

Yes, after renaming lyx.conf to lyx.conf.x the weird toolbar
disappeared. However, even after reconfigure no new lyx.conf was
created. Might come after rebooting?


It should be created when quitting LyX. This is the place that stores 
toolbar positions, window size and other GUI-related things.


JMarc

plyx

[Wolfgang Engelmann]

On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
Andrew recommended to use plyx for eg exchanging globally in a lyx 
document the location of the figure paths (e.g. from something to ./)

I have tried to install the plyx/qlyx
and have this problem:
I followed
Chapter 2 Putting the pieces in their places
1.Specifically: (a-e)
2.File formats (a)
in trying to do (b):
Similarly create a new file format qLyX, short name qlyx, extension lyx; 
none of the other check boxes or slots need to be filled. Click Apply.

I was asked to reconfigure, which I did. However, I had lyx in the 
left/right view with the instructions what to do on the left and the new 
pLyX.lyx to the right. I probably made a mistake in not closing the left 
side before reconfiguring. When I restarted lyx, I got at the left upper 
menu line just below Datei (File ) and Bearbeiten two wheels with a 
black bar going through them.
This happens with each new start of lyx with this warning on the terminal 

we@wolfgang:~$ Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-
fonts.conf, line 103: Having multiple values in test isn't supported 
and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 138: 
Having multiple values in test isn't supported and may not work as 
expected
LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
If no other LyX program is active, please delete the pipe by hand and try 
again.

However, there is no 
Pipe /home/we/.lyx/lyxpipe
which I could delete. 

Note that the Fontconfig warnings I had before and didn't bother about 
them, because they do not seem to affect the working with LyX.

How do I get rid of this? Do I have to install lyx anew?

Andrew, perhaps a note about the reconfigure after the plyx creation 
before the qlyx creation would be good and a warning, to close first the 
second lyx file before reconfiguring, if this is indeed the reason for the 
error.

Wolfgang 

 
 Hullo Wolfgang,
 
 This is the kind of thing that can be done with the find--replace
 script of the pLyX scripting system (on the wiki under Examples/pLyX
 system) which allows you to work from within the LyX gui. In fact I was
 faced with a similar task a couple of weeks ago (and found a bug in the
 script which I've since corrected). The system takes a little setting up
 (two file formats and two converters to be defined, plus some files to
 be distributed around your personal LyX folders), and some practice to
 get a feel for how it works.
 
 If you do go this way, then you would need to insert a .find--replace
 inset containing
 
 -i -r
 
 to specify a regular expression inset search, followed by two  
.argument
 insets, the first (the find regular expression) containing
 
 filename .+/([\w\d\-]+)\.jpg
 
 and the second (the replace expression) containing
 
 filename ./\1.jpg
 
 Then click the View other formats button and select pLyX.
 
 This assumes that all your graphics are .jpg format, and that the 
names
 of your images (like 'Kalanchoe-closed') are made up only from letters,
 digits, hyphens and underscores.
 
 Andrew

Re: plyx

[Andrew Parsloe]

On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:

On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:

Andrew recommended to useplyx for eg exchanging globally in a lyx
document the location of the figure paths (e.g. from something to ./)

I have tried to install the plyx/qlyx

and havethis problem:

I followed

Chapter 2 Putting the pieces in their places

1.Specifically: (a-e)

2.File formats (a)

in trying to do (b):

Similarly create a new file format qLyX, short name qlyx, extension lyx;
none of the other check boxes or slots need to be filled. Click Apply.

I was asked to reconfigure, which I did. However, I had lyx in the
left/right view with the instructions what to do on the left and the new
pLyX.lyx to the right. I probably made a mistake in not closing the left
side before reconfiguring. When I restarted lyx, I got at the left upper
menu line just below Datei (File ) and Bearbeitentwo wheels with a black
bar going through them.

This happens with each new start of lyx with this warning on the terminal

we@wolfgang:~$ Fontconfig warning:
/etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having multiple
values in test isn't supported and may not work as expected

Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line
138: Having multiple values in test isn't supported and may not work
as expected

LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.

If no other LyX program is active, please delete the pipe by hand and
try again.

However, there is no

Pipe /home/we/.lyx/lyxpipe

which I could delete.

Note that the Fontconfig warnings I had before and didn't bother about
them, because they do not seem to affect the working with LyX.

How do I get rid of this? Do I have to install lyx anew?

Andrew, perhaps a note about the reconfigure after the plyx creation
before the qlyx creation would be good and a warning, to close first the
second lyx file before reconfiguring, if this is indeed the reason for
the error.

Wolfgang



I'm sorry this has become messy, Wolfgang. I didn't anticipate left and 
right screen views being open while putting the pieces in their places, 
although it is clearly convenient to do so. However, I've just tried 
reconfiguring with left and right views open, and it proceeded without 
problems (on my Windows 7 machine).


The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from 
other threads) that you have a LyX installation that you've compiled 
yourself? Perhaps you should remove all pLyX stuff and try reconfiguring 
after that. Then, if you wish, start again.


Andrew

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

plyx

[Wolfgang Engelmann]

On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
Andrew recommended to use plyx for eg exchanging globally in a lyx 
document the location of the figure paths (e.g. from something to ./)

I have tried to install the plyx/qlyx
and have this problem:
I followed
Chapter 2 Putting the pieces in their places
1.Specifically: (a-e)
2.File formats (a)
in trying to do (b):
Similarly create a new file format qLyX, short name qlyx, extension lyx; 
none of the other check boxes or slots need to be filled. Click Apply.

I was asked to reconfigure, which I did. However, I had lyx in the 
left/right view with the instructions what to do on the left and the new 
pLyX.lyx to the right. I probably made a mistake in not closing the left 
side before reconfiguring. When I restarted lyx, I got at the left upper 
menu line just below Datei (File ) and Bearbeiten two wheels with a 
black bar going through them.
This happens with each new start of lyx with this warning on the terminal 

we@wolfgang:~$ Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-
fonts.conf, line 103: Having multiple values in test isn't supported 
and may not work as expected
Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line 138: 
Having multiple values in test isn't supported and may not work as 
expected
LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
If no other LyX program is active, please delete the pipe by hand and try 
again.

However, there is no 
Pipe /home/we/.lyx/lyxpipe
which I could delete. 

Note that the Fontconfig warnings I had before and didn't bother about 
them, because they do not seem to affect the working with LyX.

How do I get rid of this? Do I have to install lyx anew?

Andrew, perhaps a note about the reconfigure after the plyx creation 
before the qlyx creation would be good and a warning, to close first the 
second lyx file before reconfiguring, if this is indeed the reason for the 
error.

Wolfgang 

 
 Hullo Wolfgang,
 
 This is the kind of thing that can be done with the find--replace
 script of the pLyX scripting system (on the wiki under Examples/pLyX
 system) which allows you to work from within the LyX gui. In fact I was
 faced with a similar task a couple of weeks ago (and found a bug in the
 script which I've since corrected). The system takes a little setting up
 (two file formats and two converters to be defined, plus some files to
 be distributed around your personal LyX folders), and some practice to
 get a feel for how it works.
 
 If you do go this way, then you would need to insert a .find--replace
 inset containing
 
 -i -r
 
 to specify a regular expression inset search, followed by two  
.argument
 insets, the first (the find regular expression) containing
 
 filename .+/([\w\d\-]+)\.jpg
 
 and the second (the replace expression) containing
 
 filename ./\1.jpg
 
 Then click the View other formats button and select pLyX.
 
 This assumes that all your graphics are .jpg format, and that the 
names
 of your images (like 'Kalanchoe-closed') are made up only from letters,
 digits, hyphens and underscores.
 
 Andrew

Re: plyx

[Andrew Parsloe]

On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:

On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:

Andrew recommended to useplyx for eg exchanging globally in a lyx
document the location of the figure paths (e.g. from something to ./)

I have tried to install the plyx/qlyx

and havethis problem:

I followed

Chapter 2 Putting the pieces in their places

1.Specifically: (a-e)

2.File formats (a)

in trying to do (b):

Similarly create a new file format qLyX, short name qlyx, extension lyx;
none of the other check boxes or slots need to be filled. Click Apply.

I was asked to reconfigure, which I did. However, I had lyx in the
left/right view with the instructions what to do on the left and the new
pLyX.lyx to the right. I probably made a mistake in not closing the left
side before reconfiguring. When I restarted lyx, I got at the left upper
menu line just below Datei (File ) and Bearbeitentwo wheels with a black
bar going through them.

This happens with each new start of lyx with this warning on the terminal

we@wolfgang:~$ Fontconfig warning:
/etc/fonts/conf.d/65-droid-sans-fonts.conf, line 103: Having multiple
values in test isn't supported and may not work as expected

Fontconfig warning: /etc/fonts/conf.d/65-droid-sans-fonts.conf, line
138: Having multiple values in test isn't supported and may not work
as expected

LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.

If no other LyX program is active, please delete the pipe by hand and
try again.

However, there is no

Pipe /home/we/.lyx/lyxpipe

which I could delete.

Note that the Fontconfig warnings I had before and didn't bother about
them, because they do not seem to affect the working with LyX.

How do I get rid of this? Do I have to install lyx anew?

Andrew, perhaps a note about the reconfigure after the plyx creation
before the qlyx creation would be good and a warning, to close first the
second lyx file before reconfiguring, if this is indeed the reason for
the error.

Wolfgang



I'm sorry this has become messy, Wolfgang. I didn't anticipate left and 
right screen views being open while putting the pieces in their places, 
although it is clearly convenient to do so. However, I've just tried 
reconfiguring with left and right views open, and it proceeded without 
problems (on my Windows 7 machine).


The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from 
other threads) that you have a LyX installation that you've compiled 
yourself? Perhaps you should remove all pLyX stuff and try reconfiguring 
after that. Then, if you wish, start again.


Andrew

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

plyx

[Wolfgang Engelmann]

On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:
Andrew recommended to use plyx for eg exchanging globally in a lyx 
document the location of the figure paths (e.g. from something to ./)

I have tried to install the plyx/qlyx
and have this problem:
I followed
Chapter 2 Putting the pieces in their places
1.Specifically: (a-e)
2.File formats (a)
in trying to do (b):
Similarly create a new file format qLyX, short name qlyx, extension lyx; 
none of the other check boxes or slots need to be filled. Click Apply.

I was asked to reconfigure, which I did. However, I had lyx in the 
left/right view with the instructions what to do on the left and the new 
pLyX.lyx to the right. I probably made a mistake in not closing the left 
side before reconfiguring. When I restarted lyx, I got at the left upper 
menu line just below Datei (File ) and Bearbeiten two wheels with a 
black bar going through them.
This happens with each new start of lyx with this warning on the terminal 

we@wolfgang:~$ Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-
fonts.conf", line 103: Having multiple values in  isn't supported 
and may not work as expected
Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 138: 
Having multiple values in  isn't supported and may not work as 
expected
LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.
If no other LyX program is active, please delete the pipe by hand and try 
again.

However, there is no 
Pipe /home/we/.lyx/lyxpipe
which I could delete. 

Note that the Fontconfig warnings I had before and didn't bother about 
them, because they do not seem to affect the working with LyX.

How do I get rid of this? Do I have to install lyx anew?

Andrew, perhaps a note about the reconfigure after the plyx creation 
before the qlyx creation would be good and a warning, to close first the 
second lyx file before reconfiguring, if this is indeed the reason for the 
error.

Wolfgang 

> 
> Hullo Wolfgang,
> 
> This is the kind of thing that can be done with the find-&-replace
> script of the pLyX scripting system (on the wiki under Examples/pLyX
> system) which allows you to work from within the LyX gui. In fact I was
> faced with a similar task a couple of weeks ago (and found a bug in the
> script which I've since corrected). The system takes a little setting up
> (two file formats and two converters to be defined, plus some files to
> be distributed around your personal LyX folders), and some practice to
> get a feel for how it works.
> 
> If you do go this way, then you would need to insert a .find-&-replace
> inset containing
> 
> -i -r
> 
> to specify a regular expression inset search, followed by two  
.argument
> insets, the first (the find regular expression) containing
> 
> filename .+/([\w\d\-]+)\.jpg
> 
> and the second (the replace expression) containing
> 
> filename ./\1.jpg
> 
> Then click the View other formats button and select pLyX.
> 
> This assumes that all your graphics are .jpg format, and that the 
names
> of your images (like 'Kalanchoe-closed') are made up only from letters,
> digits, hyphens and underscores.
> 
> Andrew

Re: plyx

[Andrew Parsloe]

On 29/01/2014 11:03 p.m., Wolfgang Engelmann wrote:

On Saturday 25 January 2014 22:52:50 Andrew Parsloe wrote:

Andrew recommended to useplyx for eg exchanging globally in a lyx
document the location of the figure paths (e.g. from something to ./)

I have tried to install the plyx/qlyx

and havethis problem:

I followed

Chapter 2 Putting the pieces in their places

1.Specifically: (a-e)

2.File formats (a)

in trying to do (b):

Similarly create a new file format qLyX, short name qlyx, extension lyx;
none of the other check boxes or slots need to be filled. Click Apply.

I was asked to reconfigure, which I did. However, I had lyx in the
left/right view with the instructions what to do on the left and the new
pLyX.lyx to the right. I probably made a mistake in not closing the left
side before reconfiguring. When I restarted lyx, I got at the left upper
menu line just below Datei (File ) and Bearbeitentwo wheels with a black
bar going through them.

This happens with each new start of lyx with this warning on the terminal

we@wolfgang:~$ Fontconfig warning:
"/etc/fonts/conf.d/65-droid-sans-fonts.conf", line 103: Having multiple
values in  isn't supported and may not work as expected

Fontconfig warning: "/etc/fonts/conf.d/65-droid-sans-fonts.conf", line
138: Having multiple values in  isn't supported and may not work
as expected

LyXComm: Pipe /home/we/.lyx/lyxpipe.in already exists.

If no other LyX program is active, please delete the pipe by hand and
try again.

However, there is no

Pipe /home/we/.lyx/lyxpipe

which I could delete.

Note that the Fontconfig warnings I had before and didn't bother about
them, because they do not seem to affect the working with LyX.

How do I get rid of this? Do I have to install lyx anew?

Andrew, perhaps a note about the reconfigure after the plyx creation
before the qlyx creation would be good and a warning, to close first the
second lyx file before reconfiguring, if this is indeed the reason for
the error.

Wolfgang



I'm sorry this has become messy, Wolfgang. I didn't anticipate left and 
right screen views being open while putting the pieces in their places, 
although it is clearly convenient to do so. However, I've just tried 
reconfiguring with left and right views open, and it proceeded without 
problems (on my Windows 7 machine).


The LyX pipe is nowhere involved in pLyX. Am I right in thinking (from 
other threads) that you have a LyX installation that you've compiled 
yourself? Perhaps you should remove all pLyX stuff and try reconfiguring 
after that. Then, if you wish, start again.


Andrew

---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com

pLyX system: find replace LyX format code

[Andrew Parsloe]

The pLyX system (see http://wiki.lyx.org/Examples/Examples) provides a 
means of launching python scripts at the click of a few toolbar buttons; 
these scripts modify the current document. Given the speed of modern 
computers, the whole process feels built-in -- the document changes 
almost immediately in front of one's eyes.


As part of this system, I've attached a find--replace script for LyX's 
native file format,  associated files:


findrepl.py -- the script that does the finding  replacing.
findrepl_help.py  -- a help script.
pLyXFindReplace(compressed).lyx -- an explanatory LyX document that 
needs to be saved in uncompressed format for the examples in it to work.


In the document I show how the script can be used to tackle some queries 
that have appeared on the users list over the past year:


document-wide changing the width of figures
document-wide centering of figures
converting chemical formulae written in math insets (for the sake of 
sub- and superscripts) to \mathrm
clearing up debris after importing documents from, e.g., OpenOffice or 
Abiword, that have been exported as LaTeX (in other words getting rid of 
all those irritating left  right braces in ERT insets).


One way of tackling such problems is to open the document in a text 
editor and make appropriate changes there. The find--replace script 
means that is no longer necessary. It can be done from the comfort of 
the LyX GUI. There are usually other ways of tackling such matters (and 
perhaps more insightful in a LaTeX sense) but for someone pressed for 
time, this may provide a convenient fallback.


The script has a simple mode capable of finding  replacing possibly 
multiple lines of native LyX format code, and a powerful regular 
expression mode similarly capable, but also of condensing multiple 
simple searches into one regexp search (and, of course, with a health 
warning about crashing LyX, given the obscurity of regexps, but it's 
great fun).


Andrew
# Find  replace elements of the LyX source.
# Part of the pLyX.py system.
#
# Andrew Parsloe (apars...@clear.net.nz)
# version 0.1 (19 November 2012)
#
# findrepl.py 
#
import argparse, re, sys

re_backslash = re.compile(r'\n?\\backslash\n')

flex_fr = r'\begin_inset Flex .find  repl'
flex_arg = r'\begin_inset Flex .[argument]'
begin_layout = r'\begin_layout'
end_layout = r'\end_layout'
begin_std = r'\begin_layout Standard'
begin_inset = r'\begin_inset'
end_inset = r'\end_inset'
begin_note = r'\begin_inset Note'
st_open = 'status open\n'
st_coll = 'status collapsed\n'
end_body = r'\end_body'
end_document = r'\end_document'
backslash = r'\backslash'

begin_msg = r'''\begin_inset Note Note
status open
\begin_layout Plain Layout
'''
end_msg = r'''
\end_layout
\end_inset
'''

##
def main(infl, outfl, options, guff):

def strip_outers(stuff):
'''Strip enclosing layout statements.'''
stuff = stuff.partition('\n')[2]
stuff = stuff.rpartition(end_layout)[0]
return stuff

def inset_contents():
'''Get contents of inset minus LyX paragraphing.'''

contents = lines = ''
layouts, insets = 0, 1
status = True
newpara = False

for line in infl:
lines += line
if line == '\n':
continue
# assumes status open|collapsed is last status line
elif status:
if st_open == line or st_coll == line:
status = False
continue
elif begin_layout in line:
# exclude LyX paragraphing of contents
layouts += 1
if layouts  1:
contents += line
else:
newpara = True
elif begin_inset in line:
insets += 1
contents += line
elif backslash in line:
if newpara:
contents += '\n' + line
else:
contents += line
elif end_layout in line:
newpara = False
# exclude LyX paragraphing of contents
if layouts  1:
contents += line
layouts -= 1
elif end_inset in line:
newpara = False
insets -= 1
if insets == 0:
return contents, lines
else:
contents += line
else:
newpara = False
contents += line

def get_lines(n):
temp = ''
i = 0
if n == 0:
return ''
else:
for line in infl:
if line != '\n':
temp += line
i += 1
if i == n:
break
return temp

def write_msg(msg):
'''Write a yellow

pLyX system: find replace LyX format code

[Andrew Parsloe]

The pLyX system (see http://wiki.lyx.org/Examples/Examples) provides a 
means of launching python scripts at the click of a few toolbar buttons; 
these scripts modify the current document. Given the speed of modern 
computers, the whole process feels built-in -- the document changes 
almost immediately in front of one's eyes.


As part of this system, I've attached a find--replace script for LyX's 
native file format,  associated files:


findrepl.py -- the script that does the finding  replacing.
findrepl_help.py  -- a help script.
pLyXFindReplace(compressed).lyx -- an explanatory LyX document that 
needs to be saved in uncompressed format for the examples in it to work.


In the document I show how the script can be used to tackle some queries 
that have appeared on the users list over the past year:


document-wide changing the width of figures
document-wide centering of figures
converting chemical formulae written in math insets (for the sake of 
sub- and superscripts) to \mathrm
clearing up debris after importing documents from, e.g., OpenOffice or 
Abiword, that have been exported as LaTeX (in other words getting rid of 
all those irritating left  right braces in ERT insets).


One way of tackling such problems is to open the document in a text 
editor and make appropriate changes there. The find--replace script 
means that is no longer necessary. It can be done from the comfort of 
the LyX GUI. There are usually other ways of tackling such matters (and 
perhaps more insightful in a LaTeX sense) but for someone pressed for 
time, this may provide a convenient fallback.


The script has a simple mode capable of finding  replacing possibly 
multiple lines of native LyX format code, and a powerful regular 
expression mode similarly capable, but also of condensing multiple 
simple searches into one regexp search (and, of course, with a health 
warning about crashing LyX, given the obscurity of regexps, but it's 
great fun).


Andrew
# Find  replace elements of the LyX source.
# Part of the pLyX.py system.
#
# Andrew Parsloe (apars...@clear.net.nz)
# version 0.1 (19 November 2012)
#
# findrepl.py 
#
import argparse, re, sys

re_backslash = re.compile(r'\n?\\backslash\n')

flex_fr = r'\begin_inset Flex .find  repl'
flex_arg = r'\begin_inset Flex .[argument]'
begin_layout = r'\begin_layout'
end_layout = r'\end_layout'
begin_std = r'\begin_layout Standard'
begin_inset = r'\begin_inset'
end_inset = r'\end_inset'
begin_note = r'\begin_inset Note'
st_open = 'status open\n'
st_coll = 'status collapsed\n'
end_body = r'\end_body'
end_document = r'\end_document'
backslash = r'\backslash'

begin_msg = r'''\begin_inset Note Note
status open
\begin_layout Plain Layout
'''
end_msg = r'''
\end_layout
\end_inset
'''

##
def main(infl, outfl, options, guff):

def strip_outers(stuff):
'''Strip enclosing layout statements.'''
stuff = stuff.partition('\n')[2]
stuff = stuff.rpartition(end_layout)[0]
return stuff

def inset_contents():
'''Get contents of inset minus LyX paragraphing.'''

contents = lines = ''
layouts, insets = 0, 1
status = True
newpara = False

for line in infl:
lines += line
if line == '\n':
continue
# assumes status open|collapsed is last status line
elif status:
if st_open == line or st_coll == line:
status = False
continue
elif begin_layout in line:
# exclude LyX paragraphing of contents
layouts += 1
if layouts  1:
contents += line
else:
newpara = True
elif begin_inset in line:
insets += 1
contents += line
elif backslash in line:
if newpara:
contents += '\n' + line
else:
contents += line
elif end_layout in line:
newpara = False
# exclude LyX paragraphing of contents
if layouts  1:
contents += line
layouts -= 1
elif end_inset in line:
newpara = False
insets -= 1
if insets == 0:
return contents, lines
else:
contents += line
else:
newpara = False
contents += line

def get_lines(n):
temp = ''
i = 0
if n == 0:
return ''
else:
for line in infl:
if line != '\n':
temp += line
i += 1
if i == n:
break
return temp

def write_msg(msg):
'''Write a yellow

pLyX system: find & replace LyX format code

[Andrew Parsloe]

The pLyX system (see http://wiki.lyx.org/Examples/Examples) provides a 
means of launching python scripts at the click of a few toolbar buttons; 
these scripts modify the current document. Given the speed of modern 
computers, the whole process feels built-in -- the document changes 
almost immediately "in front of one's eyes".


As part of this system, I've attached a find-&-replace script for LyX's 
native file format, & associated files:


findrepl.py -- the script that does the finding & replacing.
findrepl_help.py  -- a help script.
pLyXFindReplace(compressed).lyx -- an explanatory LyX document that 
needs to be saved in uncompressed format for the examples in it to work.


In the document I show how the script can be used to tackle some queries 
that have appeared on the users list over the past year:


document-wide changing the width of figures
document-wide centering of figures
converting chemical formulae written in math insets (for the sake of 
sub- and superscripts) to \mathrm
clearing up "debris" after importing documents from, e.g., OpenOffice or 
Abiword, that have been exported as LaTeX (in other words getting rid of 
all those irritating left & right braces in ERT insets).


One way of tackling such problems is to open the document in a text 
editor and make appropriate changes there. The find-&-replace script 
means that is no longer necessary. It can be done from the comfort of 
the LyX GUI. There are usually other ways of tackling such matters (and 
perhaps more insightful in a LaTeX sense) but for someone pressed for 
time, this may provide a convenient fallback.


The script has a simple mode capable of finding & replacing possibly 
multiple lines of native LyX format code, and a powerful regular 
expression mode similarly capable, but also of condensing multiple 
simple searches into one regexp search (and, of course, with a health 
warning about crashing LyX, given the obscurity of regexps, but it's 
great fun).


Andrew
# Find & replace elements of the LyX source.
# Part of the pLyX.py system.
#
# Andrew Parsloe (apars...@clear.net.nz)
# version 0.1 (19 November 2012)
#
# findrepl.py 
#
import argparse, re, sys

re_backslash = re.compile(r'\n?\\backslash\n')

flex_fr = r'\begin_inset Flex .find & repl'
flex_arg = r'\begin_inset Flex .[argument]'
begin_layout = r'\begin_layout'
end_layout = r'\end_layout'
begin_std = r'\begin_layout Standard'
begin_inset = r'\begin_inset'
end_inset = r'\end_inset'
begin_note = r'\begin_inset Note'
st_open = 'status open\n'
st_coll = 'status collapsed\n'
end_body = r'\end_body'
end_document = r'\end_document'
backslash = r'\backslash'

begin_msg = r'''\begin_inset Note Note
status open
\begin_layout Plain Layout
'''
end_msg = r'''
\end_layout
\end_inset
'''

##
def main(infl, outfl, options, guff):

def strip_outers(stuff):
'''Strip enclosing layout statements.'''
stuff = stuff.partition('\n')[2]
stuff = stuff.rpartition(end_layout)[0]
return stuff

def inset_contents():
'''Get contents of inset minus LyX paragraphing.'''

contents = lines = ''
layouts, insets = 0, 1
status = True
newpara = False

for line in infl:
lines += line
if line == '\n':
continue
# assumes "status open|collapsed" is last status line
elif status:
if st_open == line or st_coll == line:
status = False
continue
elif begin_layout in line:
# exclude LyX paragraphing of contents
layouts += 1
if layouts > 1:
contents += line
else:
newpara = True
elif begin_inset in line:
insets += 1
contents += line
elif backslash in line:
if newpara:
contents += '\n' + line
else:
contents += line
elif end_layout in line:
newpara = False
# exclude LyX paragraphing of contents
if layouts > 1:
contents += line
layouts -= 1
elif end_inset in line:
newpara = False
insets -= 1
if insets == 0:
return contents, lines
else:
contents += line
else:
newpara = False
contents += line

def get_lines(n):
temp = ''
i = 0
if n == 0:
return ''
else:
for line in infl:
if line != '\n':
temp += line
i += 1
if i == n:

Re: The pLyX system

[Richard Heck]

On 01/02/2013 01:40 AM, Liviu Andronic wrote:

On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:

all of this explanation, and these files, there. Better yet, for the files,
create a git repo on github (or somewhere) and point at it.


Could we have a 'wiki' branch on our GIT server? So that contributed
files (modules, scripts, etc.) remain in-house, and contributors can
commit their files there?


I assume we could set up a separate repo, but I'm not that expert with git.

rh

Re: The pLyX system

[Nico Williams]

On Jan 2, 2013 8:13 AM, Richard Heck rgh...@lyx.org wrote:

 On 01/02/2013 01:40 AM, Liviu Andronic wrote:

 On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:

 all of this explanation, and these files, there. Better yet, for the
files,
 create a git repo on github (or somewhere) and point at it.

 Could we have a 'wiki' branch on our GIT server? So that contributed
 files (modules, scripts, etc.) remain in-house, and contributors can
 commit their files there?

 I assume we could set up a separate repo, but I'm not that expert with
git.

Yes, a separate repo (on the same server, of curse) is the best way.

(The Fossil VCS is git-like and has billy-in versioned wiki and ticketing.
Not that you should switch, just saying...  Mind you, i love git.)

Nico
--

Re: The pLyX system

[Pavel Sanda]

Liviu Andronic wrote:
 On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:
  all of this explanation, and these files, there. Better yet, for the files,
  create a git repo on github (or somewhere) and point at it.
 
 Could we have a 'wiki' branch on our GIT server? So that contributed
 files (modules, scripts, etc.) remain in-house, and contributors can
 commit their files there?

Our wiki upload was broken during recent php update on the server and is not
going to be fixed. We started to use current SVN repository for the
new content 
(http://www.lyx.org/trac/browser/lyxsvn/www-user/trunk/images/svnwiki)
which can be directly referred from wiki.
However some developer have to do proxy commit for you :( -- feel free to ask 
though.

If you release some tarballs or major versions you can refer to them in 
wiki/tools,
I tend to mirror things listed in http://wiki.lyx.org/Tools/Tools from time to 
time to
ftp://ftp.lyx.org/pub/lyx/contrib/

Pavel

Re: The pLyX system

[Richard Heck]

On 01/02/2013 01:40 AM, Liviu Andronic wrote:

On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:

all of this explanation, and these files, there. Better yet, for the files,
create a git repo on github (or somewhere) and point at it.


Could we have a 'wiki' branch on our GIT server? So that contributed
files (modules, scripts, etc.) remain in-house, and contributors can
commit their files there?


I assume we could set up a separate repo, but I'm not that expert with git.

rh

Re: The pLyX system

[Nico Williams]

On Jan 2, 2013 8:13 AM, Richard Heck rgh...@lyx.org wrote:

 On 01/02/2013 01:40 AM, Liviu Andronic wrote:

 On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:

 all of this explanation, and these files, there. Better yet, for the
files,
 create a git repo on github (or somewhere) and point at it.

 Could we have a 'wiki' branch on our GIT server? So that contributed
 files (modules, scripts, etc.) remain in-house, and contributors can
 commit their files there?

 I assume we could set up a separate repo, but I'm not that expert with
git.

Yes, a separate repo (on the same server, of curse) is the best way.

(The Fossil VCS is git-like and has billy-in versioned wiki and ticketing.
Not that you should switch, just saying...  Mind you, i love git.)

Nico
--

Re: The pLyX system

[Pavel Sanda]

Liviu Andronic wrote:
 On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:
  all of this explanation, and these files, there. Better yet, for the files,
  create a git repo on github (or somewhere) and point at it.
 
 Could we have a 'wiki' branch on our GIT server? So that contributed
 files (modules, scripts, etc.) remain in-house, and contributors can
 commit their files there?

Our wiki upload was broken during recent php update on the server and is not
going to be fixed. We started to use current SVN repository for the
new content 
(http://www.lyx.org/trac/browser/lyxsvn/www-user/trunk/images/svnwiki)
which can be directly referred from wiki.
However some developer have to do proxy commit for you :( -- feel free to ask 
though.

If you release some tarballs or major versions you can refer to them in 
wiki/tools,
I tend to mirror things listed in http://wiki.lyx.org/Tools/Tools from time to 
time to
ftp://ftp.lyx.org/pub/lyx/contrib/

Pavel

Re: The pLyX system

[Richard Heck]

On 01/02/2013 01:40 AM, Liviu Andronic wrote:

On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck  wrote:

all of this explanation, and these files, there. Better yet, for the files,
create a git repo on github (or somewhere) and point at it.


Could we have a 'wiki' branch on our GIT server? So that contributed
files (modules, scripts, etc.) remain in-house, and contributors can
commit their files there?


I assume we could set up a separate repo, but I'm not that expert with git.

rh

Re: The pLyX system

[Nico Williams]

On Jan 2, 2013 8:13 AM, "Richard Heck"  wrote:
>
> On 01/02/2013 01:40 AM, Liviu Andronic wrote:
>>
>> On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck  wrote:
>>>
>>> all of this explanation, and these files, there. Better yet, for the
files,
>>> create a git repo on github (or somewhere) and point at it.
>>>
>> Could we have a 'wiki' branch on our GIT server? So that contributed
>> files (modules, scripts, etc.) remain in-house, and contributors can
>> commit their files there?
>>
> I assume we could set up a separate repo, but I'm not that expert with
git.

Yes, a separate repo (on the same server, of curse) is the best way.

(The Fossil VCS is git-like and has billy-in versioned wiki and ticketing.
Not that you should switch, just saying...  Mind you, i love git.)

Nico
--

Re: The pLyX system

[Pavel Sanda]

Liviu Andronic wrote:
> On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck  wrote:
> > all of this explanation, and these files, there. Better yet, for the files,
> > create a git repo on github (or somewhere) and point at it.
> >
> Could we have a 'wiki' branch on our GIT server? So that contributed
> files (modules, scripts, etc.) remain in-house, and contributors can
> commit their files there?

Our wiki upload was broken during recent php update on the server and is not
going to be fixed. We started to use current SVN repository for the
new content 
(http://www.lyx.org/trac/browser/lyxsvn/www-user/trunk/images/svnwiki)
which can be directly referred from wiki.
However some developer have to do proxy commit for you :( -- feel free to ask 
though.

If you release some tarballs or major versions you can refer to them in 
wiki/tools,
I tend to mirror things listed in http://wiki.lyx.org/Tools/Tools from time to 
time to
ftp://ftp.lyx.org/pub/lyx/contrib/

Pavel

The pLyX system

[Andrew Parsloe]

Sometime in the first half of last year (2012) I discovered that LyX 
allowed one to export from a file with extension .lyx to a file with 
extension .lyx. What was needed to make the process work was a different 
file format name, something other than Lyx. The point of doing so was 
that during the export process one could manipulate the file in various 
ways with a script and then do a buffer-reload to overwrite the current 
document with the altered file. With the speed of modern computers, the 
whole process felt as if it were built-in to LyX -- there was no 
interruption to work flow. Rather like ERT, the process offered a means 
of plugging gaps in LyX's functionality (like sorting for instance).


I accumulated a variety of scripts to perform a variety of tasks, 
thinking I needed a new file format name for each script. That became 
unwieldy. Then it occurred to me that only one script was needed, a 
master script, which would launch a secondary script to do the actual 
export processing depending on a signal in the document. The signal is 
provided by a custom inset. This is 'the pLyX system' offered in the 
attached files to this posting and in two associated postings.


With this posting there are 9 files:

pLyX.py, pLyX_help.py -- the 'master' script  its help file
qLyX.py -- an 'undo' script which uses the backup file to do the undoing
pLyX.module -- a LyX module defining various custom insets
pLyX(compressed).lyx -- an explanatory LyX document

The explanatory document is in compressed format and needs to be 
uncompressed for the examples in it to work. There are also two 'sub-' 
or 'child' scripts:


calcul8.py, calcul8_help.py -- a calculator  its help file
break.py, break_help.py -- a stop-processing script  its help file

I know LyX users have not been crying out for a calculator but it 
provides an easy illustration of how the system works and was 
ridiculously easy to write, doing little more than feed an arithmetic or 
mathematical expression into the gaping maw of python's eval function. 
(And it's rather nice to see an expression like e**pi - pi**e evaluated 
before one's eyes in LyX.)


To keep this posting and number of files to a reasonable level, there 
are two associated postings, one containing scripts for sorting tables 
(a reworking of a script from some months ago) and sorting lists, 
including sub-lists (to all 6 levels if needed); the other containing a 
script for a system of text macros (the 'jewel in the crown' of the pLyX 
system).


There are other scripts in the offing: find and replace in native LyX 
format; a script for counting various (e.g. LyX format) objects; and one 
for heuristically structuring text 'paste-special-ed' into LyX (e.g. 
from a pdf). I have basic working examples of each of these, but they 
all need polishing.


Andrew



#\DeclareLyXModule{pLyX}
#DescriptionBegin
# Provides custom insets for specifying python scripts
# to run. To be used with the converter pLyX.py which
# exports from LyX to pLyX format. 
#DescriptionEnd
#
#v.1.0 2013-01-01
#Author: Andrew Parsloe apars...@clear.net.nz
#
Preamble
\newcommand{\pLyXgobble}[1]{}
EndPreamble

# All inset names begin with a full stop
# to aid alphabetical grouping
 MultiPar   1   

#(upper-case initial letter for this inset only)
InsetLayout Flex:.Run script(s)
  LyXType   custom
  LatexType command
  LatexName pLyXgobble
  Decorationclassic
  ContentAsLabel0
  Font
Miscno_emph
Miscno_bar
Miscno_noun
Miscno_strikeout
Miscno_uuline
Miscno_uwave
Family  roman
Series  medium
Shape   up
Sizenormal
Color   none
  EndFont
  LabelFont
Color   blue
  EndFont
  LabelString   Run script(s)
  MultiPar  1
  ResetsFont0
  Spellcheck0
End

InsetLayout Flex:.[argument]
  CopyStyle Flex:.Run script(s)
  ContentAsLabel1
  LabelFont
Color   none
  EndFont
  LabelString   .
  FreeSpacing   0
End

InsetLayout Flex:.expand macro|txtmacs
  CopyStyle Flex:.Run script(s)
  ContentAsLabel1
  LabelString   Macro
  FreeSpacing   0
End

 MultiPar   0   

InsetLayout Flex:.stop|break
  CopyStyle Flex:.Run script(s)
  LabelString   Stop
  MultiPar  0
End

InsetLayout Flex:.calculate formula|calcul8
  CopyStyle Flex:.Run script(s)
  ContentAsLabel1
  LabelString   Calculate
  MultiPar  0
End

InsetLayout Flex:.sort table|sortable

The pLyX system: sorting tables and lists

[Andrew Parsloe]

There are four scripts attached with this email and one 
compressed-format LyX document:


sortable.py, sortable_help.py -- a script for sorting tables in LyX,  
its help file
sortlist.py, sortlist_help.py -- a script for sorting lists in LyX,  
its help file

pLyXSorting(compressed).lyx -- an explanatory document with examples

The LyX document is in compressed LyX format. For the examples to work 
it must be saved in uncompressed format. (The pLyX system depends on LyX 
files being *text* files.) It contains some example tables and a 
substantial multi-level list to play with.


The table sorting script reworks for the pLyX system a script aired on 
this list back in September. On the developer's list I've noticed recent 
work to swap columns or swap rows in tables. I imagine once that is 
done, the next step will be hard to resist: go the whole way and sort 
the table. This might be a short-lived script.


The list sorting script is new and was harder to write because of the 
recursive calls to the sorting routine required by the (possible) 
presence of sub-lists. My underlying interest in sorting lists arose 
from a wish to sort indexes. (With their headings, subheadings, 
sub-subheadings, ... the logic is the same.)


Andrew


def helpnote(hv):
if hv  1:
return header + version
else:
return header + tail

header = r'''\begin_layout LyX-Code
\family roman
\series bold
.sort table
\end_layout
'''
version = r'''\begin_layout LyX-Code
\family roman
Version 1.0 (15 December 2012) Columns can be sorted more than once for
 inter-filed mixed-case alphabetical sorting.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.4 (1 November 2012) First version for pLyX system.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.3 (17 September 2012) Use of custom insets; yellow notes option,
 hrules and vrules preserved.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (13 September 2012) Script now ignores ERT insets.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (12 September 2012 Table sorting script posted to user's list.
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Sort the
\emph on
 rows
\emph default
 by the values in specified columns.
\end_layout
\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Global options
\end_layout
\begin_layout LyX-Code
\family roman
-
\series bold
h  --help
\series default
  show this help note.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-v --version
\series default
  show version information.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-n  --notes
\series default
make LyX's (yellow) notes sortable; notes are
 sort-neutral by default.
\end_layout
\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Local options
\end_layout
\begin_layout LyX-Code
\family roman
A sort specification is a sequence like 
\series bold
2a3A1+
\series default
 (or 
\series bold
2a 3A 1+
\series default
 or 
\series bold
2a
\series default
,
\series bold
 3A
\series default
,
\series bold
 1+
\series default
, etc.) where the number indicates the column and the qualifying letter or
 sign indicates the kind of sort. A specification may involve from one to
 all columns in the table and a column may appear in the spec. more than once.
 The primary sort is by the first column specified, the secondary sort by
 the second column, etc. 
\end_layout
\begin_layout Itemize
\family roman
\series bold
a, A, +
\series default
 indicate ascending sorts; 
\end_layout
\begin_layout Itemize
\family roman
\series bold
z, Z, -
\series default
 indicate descending sorts; 
\end_layout
\begin_layout Itemize
\family roman
letters indicate alphabetical sorts, uppercase indicating case sensitivity;
\end_layout
\begin_layout Itemize
\family roman
\series bold
+, -
\series default
 indicate numerical sorts.
\end_layout
\begin_layout LyX-Code
\family roman
The 
\emph on
next
\emph default
 and subsequent rows of a table following a sort specification are sorted.
 For neat alphabetical sorts involving inter-filed mixed case, specify columns
 twice, e.g. 
\series bold
1a1A
\series default
 for an AaBbCc ... sort, or
\series bold
1a1Z
\series default
 for an aAbBcC ... sort.
\end_layout
'''




def helpnote(hv):
if hv  1:
return header + version
else:
return header + tail

header = r'''\begin_layout LyX-Code
\family roman
\series bold
.sort list
\end_layout
'''
version = r'''\begin_layout LyX-Code
\family roman
Version 1.0 (16 December 2012) Allow secondary, tertiary, etc. sorts.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (13 December 2012) Include -a and -n options.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (8 November 2012)
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Sort one or more lists and sub-lists.
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code

The pLyX system: text macros

[Andrew Parsloe]

 to the parent macro.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.5 (c.1 December 2012)
 built-in 'if0' and 'if1' macros.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.4 (10 November 2012)
 built-in 'toggle' macro.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.3 (21 October 2012)
 first version for the pLyX system.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (18 October 2012)
 first functioning script using insets instead of markers.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (13 October 2012)
 first script for expanding abbreviations.
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Define and expand text macros.
\end_layout
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Global options
\end_layout
\begin_layout LyX-Code

\family roman
\series bold
-h --help  
\series default
show this help note.
\end_layout

\begin_layout LyX-Code

\family roman
\series bold
-v --version  
\series default
show version information.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-g  
\series default
 set global default value for arguments; the default is the empty string.
 E.g. 
\series bold
-g *
\series default
 sets the global default to *.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-n   
\series default
make macros within (yellow) notes expandable; default 
\series bold
False
\series default
.
\end_layout
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Defining macros
\end_layout
\begin_layout LyX-Code
\family roman
\emph on
Example 1:
\end_layout
\begin_layout LyX-Code
\family roman
\begin_inset Flex .expand macro|txtmacs
status open
\begin_layout Plain Layout
\family roman
Lp
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout
\begin_inset Formula ${\displaystyle \left(\frac{\partial^{2}}{\partial x^{2}}+\frac{\partial^{2}}{\partial y^{2}}+\frac{\partial^{2}}{\partial z^{2}}\right)\phi=0}$
\end_inset
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout LyX-Code
\family roman
defines a 
\begin_inset Quotes els
\end_inset

pure abbreviation
\begin_inset Quotes ers
\end_inset

 macro 
\series bold
Lp
\series default
 (one with no parameters) which expands to Laplace's equation in mathematical
 display format: 
\family default

\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
Lp
\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
\emph on
Example 2: 
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
hg 1 
\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout

\family roman
h
\end_layout

\end_inset

 
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman

\backslash
1yperbolic geometry
\end_layout

\end_inset


\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
shows the definition of a macro 
\series bold
hg
\series default
 with one parameter.
 The default value of the parameter is 
\begin_inset Quotes els
\end_inset

h
\begin_inset Quotes ers
\end_inset

. Using 
\begin_inset Quotes els
\end_inset

=
\begin_inset Quotes ers
\end_inset

 to mean 
\begin_inset Quotes els
\end_inset

expands to
\begin_inset Quotes ers
\end_inset

,
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status collapsed

\begin_layout Plain Layout

\family roman
hg
\end_layout

\end_inset

 = hyperbolic geometry
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status collapsed

\begin_layout Plain Layout

\family roman
hg
\end_layout

\end_inset


\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout

\family roman
H
\end_layout

\end_inset

 = Hyperbolic geometry
\end_layout

\begin_layout LyX-Code

\family roman
so that the latter is appropriate for use at the start of a sentence.
\end_layout

\begin_layout LyX-Code

\family roman
\emph on
Example 3:
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
tp 2 
\family default

\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout
File Handling
\end_layout

\end_inset


\family roman

\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout
File Formats
\end_layout

\end_inset


\family sans

\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family sans
Tools \SpecialChar \menuseparator
 Preferences \SpecialChar \menuseparator
 
\backslash
1 \SpecialChar \menuseparator
 
\backslash
2
\end_layout

\end_inset


\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
defines the macro 
\series bold
tp
\series default
 with two

Re: The pLyX system

[Richard Heck]

On 01/01/2013 05:16 AM, Andrew Parsloe wrote:
Sometime in the first half of last year (2012) I discovered that LyX 
allowed one to export from a file with extension .lyx to a file with 
extension .lyx. What was needed to make the process work was a 
different file format name, something other than Lyx. The point of 
doing so was that during the export process one could manipulate the 
file in various ways with a script and then do a buffer-reload to 
overwrite the current document with the altered file. With the speed 
of modern computers, the whole process felt as if it were built-in to 
LyX -- there was no interruption to work flow. Rather like ERT, the 
process offered a means of plugging gaps in LyX's functionality (like 
sorting for instance).


I accumulated a variety of scripts to perform a variety of tasks, 
thinking I needed a new file format name for each script. That became 
unwieldy. Then it occurred to me that only one script was needed, a 
master script, which would launch a secondary script to do the actual 
export processing depending on a signal in the document. The signal is 
provided by a custom inset. This is 'the pLyX system' offered in the 
attached files to this posting and in two associated postings.


I would suggest that, for now, you create a page on the LyX wiki, and 
put all of this explanation, and these files, there. Better yet, for the 
files, create a git repo on github (or somewhere) and point at it.


Presumably, this could evolve to the point we'd include it in LyX, but 
obviously we need to see how it works first.


Richard

Re: The pLyX system

[Liviu Andronic]

On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:
 all of this explanation, and these files, there. Better yet, for the files,
 create a git repo on github (or somewhere) and point at it.

Could we have a 'wiki' branch on our GIT server? So that contributed
files (modules, scripts, etc.) remain in-house, and contributors can
commit their files there?

Liviu

The pLyX system

[Andrew Parsloe]

Sometime in the first half of last year (2012) I discovered that LyX 
allowed one to export from a file with extension .lyx to a file with 
extension .lyx. What was needed to make the process work was a different 
file format name, something other than Lyx. The point of doing so was 
that during the export process one could manipulate the file in various 
ways with a script and then do a buffer-reload to overwrite the current 
document with the altered file. With the speed of modern computers, the 
whole process felt as if it were built-in to LyX -- there was no 
interruption to work flow. Rather like ERT, the process offered a means 
of plugging gaps in LyX's functionality (like sorting for instance).


I accumulated a variety of scripts to perform a variety of tasks, 
thinking I needed a new file format name for each script. That became 
unwieldy. Then it occurred to me that only one script was needed, a 
master script, which would launch a secondary script to do the actual 
export processing depending on a signal in the document. The signal is 
provided by a custom inset. This is 'the pLyX system' offered in the 
attached files to this posting and in two associated postings.


With this posting there are 9 files:

pLyX.py, pLyX_help.py -- the 'master' script  its help file
qLyX.py -- an 'undo' script which uses the backup file to do the undoing
pLyX.module -- a LyX module defining various custom insets
pLyX(compressed).lyx -- an explanatory LyX document

The explanatory document is in compressed format and needs to be 
uncompressed for the examples in it to work. There are also two 'sub-' 
or 'child' scripts:


calcul8.py, calcul8_help.py -- a calculator  its help file
break.py, break_help.py -- a stop-processing script  its help file

I know LyX users have not been crying out for a calculator but it 
provides an easy illustration of how the system works and was 
ridiculously easy to write, doing little more than feed an arithmetic or 
mathematical expression into the gaping maw of python's eval function. 
(And it's rather nice to see an expression like e**pi - pi**e evaluated 
before one's eyes in LyX.)


To keep this posting and number of files to a reasonable level, there 
are two associated postings, one containing scripts for sorting tables 
(a reworking of a script from some months ago) and sorting lists, 
including sub-lists (to all 6 levels if needed); the other containing a 
script for a system of text macros (the 'jewel in the crown' of the pLyX 
system).


There are other scripts in the offing: find and replace in native LyX 
format; a script for counting various (e.g. LyX format) objects; and one 
for heuristically structuring text 'paste-special-ed' into LyX (e.g. 
from a pdf). I have basic working examples of each of these, but they 
all need polishing.


Andrew



#\DeclareLyXModule{pLyX}
#DescriptionBegin
# Provides custom insets for specifying python scripts
# to run. To be used with the converter pLyX.py which
# exports from LyX to pLyX format. 
#DescriptionEnd
#
#v.1.0 2013-01-01
#Author: Andrew Parsloe apars...@clear.net.nz
#
Preamble
\newcommand{\pLyXgobble}[1]{}
EndPreamble

# All inset names begin with a full stop
# to aid alphabetical grouping
 MultiPar   1   

#(upper-case initial letter for this inset only)
InsetLayout Flex:.Run script(s)
  LyXType   custom
  LatexType command
  LatexName pLyXgobble
  Decorationclassic
  ContentAsLabel0
  Font
Miscno_emph
Miscno_bar
Miscno_noun
Miscno_strikeout
Miscno_uuline
Miscno_uwave
Family  roman
Series  medium
Shape   up
Sizenormal
Color   none
  EndFont
  LabelFont
Color   blue
  EndFont
  LabelString   Run script(s)
  MultiPar  1
  ResetsFont0
  Spellcheck0
End

InsetLayout Flex:.[argument]
  CopyStyle Flex:.Run script(s)
  ContentAsLabel1
  LabelFont
Color   none
  EndFont
  LabelString   .
  FreeSpacing   0
End

InsetLayout Flex:.expand macro|txtmacs
  CopyStyle Flex:.Run script(s)
  ContentAsLabel1
  LabelString   Macro
  FreeSpacing   0
End

 MultiPar   0   

InsetLayout Flex:.stop|break
  CopyStyle Flex:.Run script(s)
  LabelString   Stop
  MultiPar  0
End

InsetLayout Flex:.calculate formula|calcul8
  CopyStyle Flex:.Run script(s)
  ContentAsLabel1
  LabelString   Calculate
  MultiPar  0
End

InsetLayout Flex:.sort table|sortable

The pLyX system: sorting tables and lists

[Andrew Parsloe]

There are four scripts attached with this email and one 
compressed-format LyX document:


sortable.py, sortable_help.py -- a script for sorting tables in LyX,  
its help file
sortlist.py, sortlist_help.py -- a script for sorting lists in LyX,  
its help file

pLyXSorting(compressed).lyx -- an explanatory document with examples

The LyX document is in compressed LyX format. For the examples to work 
it must be saved in uncompressed format. (The pLyX system depends on LyX 
files being *text* files.) It contains some example tables and a 
substantial multi-level list to play with.


The table sorting script reworks for the pLyX system a script aired on 
this list back in September. On the developer's list I've noticed recent 
work to swap columns or swap rows in tables. I imagine once that is 
done, the next step will be hard to resist: go the whole way and sort 
the table. This might be a short-lived script.


The list sorting script is new and was harder to write because of the 
recursive calls to the sorting routine required by the (possible) 
presence of sub-lists. My underlying interest in sorting lists arose 
from a wish to sort indexes. (With their headings, subheadings, 
sub-subheadings, ... the logic is the same.)


Andrew


def helpnote(hv):
if hv  1:
return header + version
else:
return header + tail

header = r'''\begin_layout LyX-Code
\family roman
\series bold
.sort table
\end_layout
'''
version = r'''\begin_layout LyX-Code
\family roman
Version 1.0 (15 December 2012) Columns can be sorted more than once for
 inter-filed mixed-case alphabetical sorting.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.4 (1 November 2012) First version for pLyX system.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.3 (17 September 2012) Use of custom insets; yellow notes option,
 hrules and vrules preserved.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (13 September 2012) Script now ignores ERT insets.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (12 September 2012 Table sorting script posted to user's list.
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Sort the
\emph on
 rows
\emph default
 by the values in specified columns.
\end_layout
\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Global options
\end_layout
\begin_layout LyX-Code
\family roman
-
\series bold
h  --help
\series default
  show this help note.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-v --version
\series default
  show version information.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-n  --notes
\series default
make LyX's (yellow) notes sortable; notes are
 sort-neutral by default.
\end_layout
\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Local options
\end_layout
\begin_layout LyX-Code
\family roman
A sort specification is a sequence like 
\series bold
2a3A1+
\series default
 (or 
\series bold
2a 3A 1+
\series default
 or 
\series bold
2a
\series default
,
\series bold
 3A
\series default
,
\series bold
 1+
\series default
, etc.) where the number indicates the column and the qualifying letter or
 sign indicates the kind of sort. A specification may involve from one to
 all columns in the table and a column may appear in the spec. more than once.
 The primary sort is by the first column specified, the secondary sort by
 the second column, etc. 
\end_layout
\begin_layout Itemize
\family roman
\series bold
a, A, +
\series default
 indicate ascending sorts; 
\end_layout
\begin_layout Itemize
\family roman
\series bold
z, Z, -
\series default
 indicate descending sorts; 
\end_layout
\begin_layout Itemize
\family roman
letters indicate alphabetical sorts, uppercase indicating case sensitivity;
\end_layout
\begin_layout Itemize
\family roman
\series bold
+, -
\series default
 indicate numerical sorts.
\end_layout
\begin_layout LyX-Code
\family roman
The 
\emph on
next
\emph default
 and subsequent rows of a table following a sort specification are sorted.
 For neat alphabetical sorts involving inter-filed mixed case, specify columns
 twice, e.g. 
\series bold
1a1A
\series default
 for an AaBbCc ... sort, or
\series bold
1a1Z
\series default
 for an aAbBcC ... sort.
\end_layout
'''




def helpnote(hv):
if hv  1:
return header + version
else:
return header + tail

header = r'''\begin_layout LyX-Code
\family roman
\series bold
.sort list
\end_layout
'''
version = r'''\begin_layout LyX-Code
\family roman
Version 1.0 (16 December 2012) Allow secondary, tertiary, etc. sorts.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (13 December 2012) Include -a and -n options.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (8 November 2012)
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Sort one or more lists and sub-lists.
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code

The pLyX system: text macros

[Andrew Parsloe]

 to the parent macro.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.5 (c.1 December 2012)
 built-in 'if0' and 'if1' macros.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.4 (10 November 2012)
 built-in 'toggle' macro.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.3 (21 October 2012)
 first version for the pLyX system.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (18 October 2012)
 first functioning script using insets instead of markers.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (13 October 2012)
 first script for expanding abbreviations.
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Define and expand text macros.
\end_layout
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Global options
\end_layout
\begin_layout LyX-Code

\family roman
\series bold
-h --help  
\series default
show this help note.
\end_layout

\begin_layout LyX-Code

\family roman
\series bold
-v --version  
\series default
show version information.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-g  
\series default
 set global default value for arguments; the default is the empty string.
 E.g. 
\series bold
-g *
\series default
 sets the global default to *.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-n   
\series default
make macros within (yellow) notes expandable; default 
\series bold
False
\series default
.
\end_layout
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Defining macros
\end_layout
\begin_layout LyX-Code
\family roman
\emph on
Example 1:
\end_layout
\begin_layout LyX-Code
\family roman
\begin_inset Flex .expand macro|txtmacs
status open
\begin_layout Plain Layout
\family roman
Lp
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout
\begin_inset Formula ${\displaystyle \left(\frac{\partial^{2}}{\partial x^{2}}+\frac{\partial^{2}}{\partial y^{2}}+\frac{\partial^{2}}{\partial z^{2}}\right)\phi=0}$
\end_inset
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout LyX-Code
\family roman
defines a 
\begin_inset Quotes els
\end_inset

pure abbreviation
\begin_inset Quotes ers
\end_inset

 macro 
\series bold
Lp
\series default
 (one with no parameters) which expands to Laplace's equation in mathematical
 display format: 
\family default

\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
Lp
\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
\emph on
Example 2: 
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
hg 1 
\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout

\family roman
h
\end_layout

\end_inset

 
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman

\backslash
1yperbolic geometry
\end_layout

\end_inset


\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
shows the definition of a macro 
\series bold
hg
\series default
 with one parameter.
 The default value of the parameter is 
\begin_inset Quotes els
\end_inset

h
\begin_inset Quotes ers
\end_inset

. Using 
\begin_inset Quotes els
\end_inset

=
\begin_inset Quotes ers
\end_inset

 to mean 
\begin_inset Quotes els
\end_inset

expands to
\begin_inset Quotes ers
\end_inset

,
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status collapsed

\begin_layout Plain Layout

\family roman
hg
\end_layout

\end_inset

 = hyperbolic geometry
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status collapsed

\begin_layout Plain Layout

\family roman
hg
\end_layout

\end_inset


\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout

\family roman
H
\end_layout

\end_inset

 = Hyperbolic geometry
\end_layout

\begin_layout LyX-Code

\family roman
so that the latter is appropriate for use at the start of a sentence.
\end_layout

\begin_layout LyX-Code

\family roman
\emph on
Example 3:
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
tp 2 
\family default

\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout
File Handling
\end_layout

\end_inset


\family roman

\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout
File Formats
\end_layout

\end_inset


\family sans

\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family sans
Tools \SpecialChar \menuseparator
 Preferences \SpecialChar \menuseparator
 
\backslash
1 \SpecialChar \menuseparator
 
\backslash
2
\end_layout

\end_inset


\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
defines the macro 
\series bold
tp
\series default
 with two

Re: The pLyX system

[Richard Heck]

On 01/01/2013 05:16 AM, Andrew Parsloe wrote:
Sometime in the first half of last year (2012) I discovered that LyX 
allowed one to export from a file with extension .lyx to a file with 
extension .lyx. What was needed to make the process work was a 
different file format name, something other than Lyx. The point of 
doing so was that during the export process one could manipulate the 
file in various ways with a script and then do a buffer-reload to 
overwrite the current document with the altered file. With the speed 
of modern computers, the whole process felt as if it were built-in to 
LyX -- there was no interruption to work flow. Rather like ERT, the 
process offered a means of plugging gaps in LyX's functionality (like 
sorting for instance).


I accumulated a variety of scripts to perform a variety of tasks, 
thinking I needed a new file format name for each script. That became 
unwieldy. Then it occurred to me that only one script was needed, a 
master script, which would launch a secondary script to do the actual 
export processing depending on a signal in the document. The signal is 
provided by a custom inset. This is 'the pLyX system' offered in the 
attached files to this posting and in two associated postings.


I would suggest that, for now, you create a page on the LyX wiki, and 
put all of this explanation, and these files, there. Better yet, for the 
files, create a git repo on github (or somewhere) and point at it.


Presumably, this could evolve to the point we'd include it in LyX, but 
obviously we need to see how it works first.


Richard

Re: The pLyX system

[Liviu Andronic]

On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck rgh...@lyx.org wrote:
 all of this explanation, and these files, there. Better yet, for the files,
 create a git repo on github (or somewhere) and point at it.

Could we have a 'wiki' branch on our GIT server? So that contributed
files (modules, scripts, etc.) remain in-house, and contributors can
commit their files there?

Liviu

The pLyX system

[Andrew Parsloe]

Sometime in the first half of last year (2012) I discovered that LyX 
allowed one to export from a file with extension .lyx to a file with 
extension .lyx. What was needed to make the process work was a different 
file format name, something other than Lyx. The point of doing so was 
that during the export process one could manipulate the file in various 
ways with a script and then do a buffer-reload to overwrite the current 
document with the altered file. With the speed of modern computers, the 
whole process felt as if it were built-in to LyX -- there was no 
interruption to work flow. Rather like ERT, the process offered a means 
of plugging gaps in LyX's functionality (like sorting for instance).


I accumulated a variety of scripts to perform a variety of tasks, 
thinking I needed a new file format name for each script. That became 
unwieldy. Then it occurred to me that only one script was needed, a 
master script, which would launch a secondary script to do the actual 
export processing depending on a signal in the document. The signal is 
provided by a custom inset. This is 'the pLyX system' offered in the 
attached files to this posting and in two associated postings.


With this posting there are 9 files:

pLyX.py, pLyX_help.py -- the 'master' script & its help file
qLyX.py -- an 'undo' script which uses the backup file to do the undoing
pLyX.module -- a LyX module defining various custom insets
pLyX(compressed).lyx -- an explanatory LyX document

The explanatory document is in compressed format and needs to be 
uncompressed for the examples in it to work. There are also two 'sub-' 
or 'child' scripts:


calcul8.py, calcul8_help.py -- a calculator & its help file
break.py, break_help.py -- a stop-processing script & its help file

I know LyX users have not been crying out for a calculator but it 
provides an easy illustration of how the system works and was 
ridiculously easy to write, doing little more than feed an arithmetic or 
mathematical expression into the gaping maw of python's eval function. 
(And it's rather nice to see an expression like e**pi - pi**e evaluated 
before one's eyes in LyX.)


To keep this posting and number of files to a reasonable level, there 
are two associated postings, one containing scripts for sorting tables 
(a reworking of a script from some months ago) and sorting lists, 
including sub-lists (to all 6 levels if needed); the other containing a 
script for a system of text macros (the 'jewel in the crown' of the pLyX 
system).


There are other scripts in the offing: find and replace in native LyX 
format; a script for counting various (e.g. LyX format) objects; and one 
for heuristically structuring text 'paste-special-ed' into LyX (e.g. 
from a pdf). I have basic working examples of each of these, but they 
all need polishing.


Andrew



#\DeclareLyXModule{pLyX}
#DescriptionBegin
# Provides custom insets for specifying python scripts
# to run. To be used with the converter pLyX.py which
# exports from LyX to pLyX format. 
#DescriptionEnd
#
#v.1.0 2013-01-01
#Author: Andrew Parsloe <apars...@clear.net.nz>
#
Preamble
\newcommand{\pLyXgobble}[1]{}
EndPreamble

# All inset names begin with a full stop
# to aid alphabetical grouping
 MultiPar   1   

#(upper-case initial letter for this inset only)
InsetLayout "Flex:.Run script(s)"
  LyXType   custom
  LatexType command
  LatexName pLyXgobble
  Decorationclassic
  ContentAsLabel0
  Font
Miscno_emph
Miscno_bar
Miscno_noun
Miscno_strikeout
Miscno_uuline
Miscno_uwave
Family  roman
Series  medium
Shape   up
Sizenormal
Color   none
  EndFont
  LabelFont
Color   blue
  EndFont
  LabelString   "Run script(s)"
  MultiPar  1
  ResetsFont0
  Spellcheck0
End

InsetLayout Flex:.[argument]
  CopyStyle "Flex:.Run script(s)"
  ContentAsLabel1
  LabelFont
Color   none
  EndFont
  LabelString   .
  FreeSpacing   0
End

InsetLayout "Flex:.expand macro|txtmacs"
  CopyStyle "Flex:.Run script(s)"
  ContentAsLabel1
  LabelString   Macro
  FreeSpacing   0
End

 MultiPar   0   

InsetLayout Flex:.stop|break
  CopyStyle "Flex:.Run script(s)"
  LabelString   Stop
  MultiPar  0
End

InsetLayout "Flex:.calculate formula|calcul8"
  CopyStyle "Flex:.Run script(s)"
  ContentAsLabel

The pLyX system: sorting tables and lists

[Andrew Parsloe]

There are four scripts attached with this email and one 
compressed-format LyX document:


sortable.py, sortable_help.py -- a script for sorting tables in LyX, & 
its help file
sortlist.py, sortlist_help.py -- a script for sorting lists in LyX, & 
its help file

pLyXSorting(compressed).lyx -- an explanatory document with examples

The LyX document is in compressed LyX format. For the examples to work 
it must be saved in uncompressed format. (The pLyX system depends on LyX 
files being *text* files.) It contains some example tables and a 
substantial multi-level list to play with.


The table sorting script reworks for the pLyX system a script aired on 
this list back in September. On the developer's list I've noticed recent 
work to swap columns or swap rows in tables. I imagine once that is 
done, the next step will be hard to resist: go the whole way and sort 
the table. This might be a short-lived script.


The list sorting script is new and was harder to write because of the 
recursive calls to the sorting routine required by the (possible) 
presence of sub-lists. My underlying interest in sorting lists arose 
from a wish to sort indexes. (With their headings, subheadings, 
sub-subheadings, ... the logic is the same.)


Andrew


def helpnote(hv):
if hv > 1:
return header + version
else:
return header + tail

header = r'''\begin_layout LyX-Code
\family roman
\series bold
.sort table
\end_layout
'''
version = r'''\begin_layout LyX-Code
\family roman
Version 1.0 (15 December 2012) Columns can be sorted more than once for
 inter-filed mixed-case alphabetical sorting.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.4 (1 November 2012) First version for pLyX system.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.3 (17 September 2012) Use of custom insets; yellow notes option,
 hrules and vrules preserved.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (13 September 2012) Script now ignores ERT insets.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (12 September 2012 Table sorting script posted to user's list.
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Sort the
\emph on
 rows
\emph default
 by the values in specified columns.
\end_layout
\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Global options
\end_layout
\begin_layout LyX-Code
\family roman
-
\series bold
h  --help
\series default
  show this help note.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-v --version
\series default
  show version information.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-n  --notes
\series default
make LyX's (yellow) notes sortable; notes are
 sort-neutral by default.
\end_layout
\begin_layout LyX-Code
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Local options
\end_layout
\begin_layout LyX-Code
\family roman
A sort specification is a sequence like 
\series bold
2a3A1+
\series default
 (or 
\series bold
2a 3A 1+
\series default
 or 
\series bold
2a
\series default
,
\series bold
 3A
\series default
,
\series bold
 1+
\series default
, etc.) where the number indicates the column and the qualifying letter or
 sign indicates the kind of sort. A specification may involve from one to
 all columns in the table and a column may appear in the spec. more than once.
 The primary sort is by the first column specified, the secondary sort by
 the second column, etc. 
\end_layout
\begin_layout Itemize
\family roman
\series bold
a, A, +
\series default
 indicate ascending sorts; 
\end_layout
\begin_layout Itemize
\family roman
\series bold
z, Z, -
\series default
 indicate descending sorts; 
\end_layout
\begin_layout Itemize
\family roman
letters indicate alphabetical sorts, uppercase indicating case sensitivity;
\end_layout
\begin_layout Itemize
\family roman
\series bold
+, -
\series default
 indicate numerical sorts.
\end_layout
\begin_layout LyX-Code
\family roman
The 
\emph on
next
\emph default
 and subsequent rows of a table following a sort specification are sorted.
 For neat alphabetical sorts involving inter-filed mixed case, specify columns
 twice, e.g. 
\series bold
1a1A
\series default
 for an AaBbCc ... sort, or
\series bold
1a1Z
\series default
 for an aAbBcC ... sort.
\end_layout
'''




def helpnote(hv):
if hv > 1:
return header + version
else:
return header + tail

header = r'''\begin_layout LyX-Code
\family roman
\series bold
.sort list
\end_layout
'''
version = r'''\begin_layout LyX-Code
\family roman
Version 1.0 (16 December 2012) Allow secondary, tertiary, etc. sorts.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (13 December 2012) Include -a and -n options.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (8 November 2012)
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Sort one or more lists and sub-lists.
\begin_layout LyX-Code

\end_layout
\be

The pLyX system: text macros

[Andrew Parsloe]

ents containing top-level macros before passing to the parent macro.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.5 (c.1 December 2012)
 built-in 'if0' and 'if1' macros.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.4 (10 November 2012)
 built-in 'toggle' macro.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.3 (21 October 2012)
 first version for the pLyX system.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.2 (18 October 2012)
 first functioning script using insets instead of markers.
\end_layout
\begin_layout LyX-Code
\family roman
Version 0.1 (13 October 2012)
 first script for expanding abbreviations.
\end_layout
'''
tail = r'''\begin_layout LyX-Code
\family roman
Define and expand text macros.
\end_layout
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Global options
\end_layout
\begin_layout LyX-Code

\family roman
\series bold
-h --help  
\series default
show this help note.
\end_layout

\begin_layout LyX-Code

\family roman
\series bold
-v --version  
\series default
show version information.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-g  
\series default
 set global default value for arguments; the default is the empty string.
 E.g. 
\series bold
-g *
\series default
 sets the global default to *.
\end_layout
\begin_layout LyX-Code
\family roman
\series bold
-n   
\series default
make macros within (yellow) notes expandable; default 
\series bold
False
\series default
.
\end_layout
\begin_layout LyX-Code

\end_layout
\begin_layout LyX-Code
\family roman
\series bold
Defining macros
\end_layout
\begin_layout LyX-Code
\family roman
\emph on
Example 1:
\end_layout
\begin_layout LyX-Code
\family roman
\begin_inset Flex .expand macro|txtmacs
status open
\begin_layout Plain Layout
\family roman
Lp
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout
\begin_inset Formula ${\displaystyle \left(\frac{\partial^{2}}{\partial x^{2}}+\frac{\partial^{2}}{\partial y^{2}}+\frac{\partial^{2}}{\partial z^{2}}\right)\phi=0}$
\end_inset
\end_layout
\end_inset
\end_layout
\end_inset
\end_layout
\begin_layout LyX-Code
\family roman
defines a 
\begin_inset Quotes els
\end_inset

pure abbreviation
\begin_inset Quotes ers
\end_inset

 macro 
\series bold
Lp
\series default
 (one with no parameters) which expands to Laplace's equation in mathematical
 display format: 
\family default

\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
Lp
\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
\emph on
Example 2: 
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
hg 1 
\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout

\family roman
h
\end_layout

\end_inset

 
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman

\backslash
1yperbolic geometry
\end_layout

\end_inset


\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family roman
shows the definition of a macro 
\series bold
hg
\series default
 with one parameter.
 The default value of the parameter is 
\begin_inset Quotes els
\end_inset

h
\begin_inset Quotes ers
\end_inset

. Using 
\begin_inset Quotes els
\end_inset

=>
\begin_inset Quotes ers
\end_inset

 to mean 
\begin_inset Quotes els
\end_inset

expands to
\begin_inset Quotes ers
\end_inset

,
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status collapsed

\begin_layout Plain Layout

\family roman
hg
\end_layout

\end_inset

 => hyperbolic geometry
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status collapsed

\begin_layout Plain Layout

\family roman
hg
\end_layout

\end_inset


\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout

\family roman
H
\end_layout

\end_inset

 => Hyperbolic geometry
\end_layout

\begin_layout LyX-Code

\family roman
so that the latter is appropriate for use at the start of a sentence.
\end_layout

\begin_layout LyX-Code

\family roman
\emph on
Example 3:
\end_layout

\begin_layout LyX-Code

\family roman
\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family roman
tp 2 
\family default

\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout
File Handling
\end_layout

\end_inset


\family roman

\begin_inset Flex .[argument]
status collapsed

\begin_layout Plain Layout
File Formats
\end_layout

\end_inset


\family sans

\begin_inset Flex .expand macro|txtmacs
status open

\begin_layout Plain Layout

\family sans
Tools \SpecialChar \menuseparator
 Preferences \SpecialChar \menuseparator
 
\backslash
1 \SpecialChar \menuseparator
 
\backslash
2
\end_layout

\end_inset


\end_layout

\end_inset


\end_layout

\begin_layout LyX-Code

\family 

Re: The pLyX system

[Richard Heck]

On 01/01/2013 05:16 AM, Andrew Parsloe wrote:
Sometime in the first half of last year (2012) I discovered that LyX 
allowed one to export from a file with extension .lyx to a file with 
extension .lyx. What was needed to make the process work was a 
different file format name, something other than Lyx. The point of 
doing so was that during the export process one could manipulate the 
file in various ways with a script and then do a buffer-reload to 
overwrite the current document with the altered file. With the speed 
of modern computers, the whole process felt as if it were built-in to 
LyX -- there was no interruption to work flow. Rather like ERT, the 
process offered a means of plugging gaps in LyX's functionality (like 
sorting for instance).


I accumulated a variety of scripts to perform a variety of tasks, 
thinking I needed a new file format name for each script. That became 
unwieldy. Then it occurred to me that only one script was needed, a 
master script, which would launch a secondary script to do the actual 
export processing depending on a signal in the document. The signal is 
provided by a custom inset. This is 'the pLyX system' offered in the 
attached files to this posting and in two associated postings.


I would suggest that, for now, you create a page on the LyX wiki, and 
put all of this explanation, and these files, there. Better yet, for the 
files, create a git repo on github (or somewhere) and point at it.


Presumably, this could evolve to the point we'd include it in LyX, but 
obviously we need to see how it works first.


Richard

Re: The pLyX system

[Liviu Andronic]

On Tue, Jan 1, 2013 at 4:32 PM, Richard Heck  wrote:
> all of this explanation, and these files, there. Better yet, for the files,
> create a git repo on github (or somewhere) and point at it.
>
Could we have a 'wiki' branch on our GIT server? So that contributed
files (modules, scripts, etc.) remain in-house, and contributors can
commit their files there?

Liviu