. 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
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
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
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
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
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
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
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
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
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,
. 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
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
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
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
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
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
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
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
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
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,
ocation 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)
&g
oe 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
>
>>
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
>
>
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
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
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
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
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
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
> >>
> >>
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,
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
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
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
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
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
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
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
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
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
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
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)
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
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
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)
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
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
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
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
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
-- 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
(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
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
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,
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
-- 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
(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
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
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,
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
sed).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
ut
\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
Vers
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
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,
63 matches
Mail list logo