On Fri, Jun 16, 2000 at 12:09:48AM +0300, Dekel Tsur wrote:
Sorry, python scripts aren't on my radar screen :)
So I guess I'll have to write it ...
PS (to Asger) The need for writing scripts for the external inset is a little
annoying. Can't we just add an option to define UpdateCommand
How does one make a batch job for .lyx - .dvi "conversion" ?
lyx2dvi:
#!/bin/sh
lyx --export latex $1
latex $1
latex $1
latex $1
or something like that.
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
On 15-Jun-2000 Dekel Tsur wrote:
On Mon, Jun 12, 2000 at 02:54:33PM +0200, Asger K. Alstrup Nielsen wrote:
The highlights include:
- Mayor clean up in the LyXText and inset handling by Juergen and
Lgb. This leads in the direction of a lot of new posibilities
for nesting different
On 15-Jun-2000 Dekel Tsur wrote:
I also want to add that routines for building forms automatically, can also
be used for adding support for arbitrary latex packages: a text file will
define the arguments/config commands to the package, and a form for changing
these values will be created
On Thu, 15 Jun 2000, Dekel Tsur wrote:
To be more specific, lyxrc.C should contain a big array with entries for the
lyxrc variables, each entry contains information like token name, default
value, etc. Another field will be type (e.g. "printer", "screen fonts", etc.)
which will be used for
current CVS does not compile with KDE frontend due to the difference in
Dialogs class definition for KDE and Xforms frontends. Namely, Dialogs
class constructor expects LyXView* as its argument in Xforms frontend
(src/frontends/Dialogs.h src/frontends/xforms/Dialogs.C) and LyXFunc* as
an
"Andre" == Andre Poenitz [EMAIL PROTECTED] writes:
How does one make a batch job for .lyx - .dvi "conversion" ?
Andre lyx2dvi:
Andre #!/bin/sh lyx --export latex $1
BTW andre, did you document this flag somewhere? I found nothing in
the man page (hint!).
JMarc
Kayvan This is on RH 6.1, default compiler/linker/etc.:
Kayvan /bin/sh ./libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I. -I./.. -I./..
-O2 -m486 -fno-strength-reduce -ansi -W -Wall -Wno-return-type -c marshal.cc
Kayvan c++ -DHAVE_CONFIG_H -I. -I. -I. -I./.. -I./.. -O2 -m486
using configure --with-frontend=kde
configuration falls over if QT or KDE aren't installed in certain hardwired
locations. This is daft, since two shell variables are defined when running KDE
but not employed by the configure script.
Why not test
$KDEDIR (=/usr/local/kde on my system)
$QTDIR
Andre #!/bin/sh lyx --export latex $1
BTW andre, did you document this flag somewhere? I found nothing in
the man page (hint!).
Of course not ;-)
There had been some discussion on the naming of the flags and I
did not have the impression that the issue was settled. Until then
I did not
"Andre" == Andre Poenitz [EMAIL PROTECTED] writes:
Andre There had been some discussion on the naming of the flags and I
Andre did not have the impression that the issue was settled. Until
Andre then I did not want to "officially" document the flag in order
Andre to prevent people from
On Fri, Jun 16, 2000 at 09:12:08AM +0200, Andre Poenitz wrote:
How does one make a batch job for .lyx - .dvi "conversion" ?
lyx2dvi:
#!/bin/sh
lyx --export latex $1
latex $1
latex $1
latex $1
Why there is now lyx --export dvi option?
However, it is possible to use
lyx --execute
On 16-Jun-2000 Angus Leeming wrote:
using configure --with-frontend=kde
configuration falls over if QT or KDE aren't installed in certain hardwired
locations. This is daft, since two shell variables are defined when running KDE
but not employed by the configure script.
Why not test
Why there is now lyx --export dvi option?
Erm... now that you mention it... I think lyx --export dvi
is possible, too. Stupid me...
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
However, I think that resizing/rotation options should be added to the
external inset.
Yes, I think so to. If you read the ExternalTemplate.lyx file, you will
notice that this is mentioned as a feature to implement for a volunteer.
I think it should be designed such that there are optional
It is very sad that LyX still can't support X keyboard other than
ISO-8859-1. It is one of those broken program for which I still need a
broken xmodmap. And I also don't think using LyX own keymaps is a good
thing, as the Xserver is ment to handle the keyboard.
The problem is, that when I have
Marko current CVS does not compile with KDE frontend due to the difference in
Marko Dialogs class definition for KDE and Xforms frontends. Namely, Dialogs
Marko class constructor expects LyXView* as its argument in Xforms frontend
Marko (src/frontends/Dialogs.h src/frontends/xforms/Dialogs.C) and
On Fri, Jun 16, 2000 at 11:04:52AM +0300, Lior Silberman wrote:
On Thu, 15 Jun 2000, Dekel Tsur wrote:
To be more specific, lyxrc.C should contain a big array with entries for the
lyxrc variables, each entry contains information like token name, default
value, etc. Another field will be
all development has been done with the xforms code. The code in the kde
directory was written as proof of concept a long, long time ago. As such, it
has lagged behind...
You are correct to report that the code in kde/Dialogs.C is inconsistent with
that in xforms/Dialogs.C. It is wrong and
Hello,
I have imported a text document in lyx which contains « and » "french
quote"
How can i input them in my lyx document
compose + + does not works
is there a tips
There are a few things you need to know about this table. This manual is
set up --- by hand, mind you --- to print all of
Date: Fri, 16 Jun 2000 17:59:14 +0100
From: Yann MORERE [EMAIL PROTECTED]
To: LyX Users [EMAIL PROTECTED], LyX devel [EMAIL PROTECTED]
Subject: [Q] How to generate the character « and »?
Hello,
I have imported a text document in lyx which contains « and » "french
quote"
How can i input them
No. You should write a python script that generates both the pstex and the
pstex_t files automatically (in the example above, the suffix of the
Postscript file should be changed from pstex to eps).
By now, it would come as no surprise that I'd like to ask Dekel to submit
a patch that
On Fri, Jun 16, 2000 at 07:52:08PM +0300, Dekel Tsur wrote:
No. You should write a python script that generates both the pstex and the
pstex_t files automatically (in the example above, the suffix of the
Postscript file should be changed from pstex to eps).
By now, it would come as
On Fri, Jun 16, 2000 at 01:08:47PM +0200, Asger K. Alstrup Nielsen wrote:
If what you meant was to provide a small facility to allow the
"safe" script constructs, sure we could do that. We already showed
the way with the script for the external date inset which uses
a general Python script as
Is there any idea when we might get visual feedback to the
"size" attribute for table cells? Or even a horizontal scrollbar when
tables go off-screen? Currently editing tables is virtually impossible.
I use the size for when I have a longer piece of text for a table cell and
I believe there is
On Fri, Jun 16, 2000 at 08:07:18PM +0300, Dekel Tsur wrote:
Why not have support for ";" in the external figure code?
(i.e. define UpdateCommand as "cmd1 parameters;cmd2 parameters;..." )
This will save a call to python.
Better yet is, perhaps, to create a python secure module, that could
On Fri, Jun 16, 2000 at 01:18:49PM +0200, Asger K. Alstrup Nielsen wrote:
However, I think that resizing/rotation options should be added to the
external inset.
Yes, I think so to. If you read the ExternalTemplate.lyx file, you will
notice that this is mentioned as a feature to implement
Why not have support for ";" in the external figure code?
(i.e. define UpdateCommand as "cmd1 parameters;cmd2 parameters;..." )
This will save a call to python.
Better yet is, perhaps, to create a python secure module, that could be used as
a wrapper around safe system calls. What do
For some strange reason, I named the script fig2psfig.py, where it should be
fig2pstex.py.
Here is a fixed patch.
This patch set is good. Thanks Dekel ;-)
Could somebody please apply it to the cvs?
Thanks,
Asger
Yes, I think so to. If you read the ExternalTemplate.lyx file, you will
notice that this is mentioned as a feature to implement for a volunteer.
I've added more options to the external inset: the ability to resize/rotate
the result (the resize buttons doesn't work yet).
I also changed
An alternative approach would be to keep all the member variables, without
having the query_* methods.
The only disadvantage of this (comparing to your suggestion) is that adding
a new variable requires adding two lines (one in lyxrc.C and one in lyxrc.h)
instead of one (in lyxrc.C), and
On Fri, Jun 16, 2000 at 12:09:48AM +0300, Dekel Tsur wrote:
> > Sorry, python scripts aren't on my radar screen :)
>
> So I guess I'll have to write it ...
>
> PS (to Asger) The need for writing scripts for the external inset is a little
> annoying. Can't we just add an option to define
> How does one make a batch job for .lyx -> .dvi "conversion" ?
lyx2dvi:
#!/bin/sh
lyx --export latex $1
latex $1
latex $1
latex $1
or something like that.
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
On 15-Jun-2000 Dekel Tsur wrote:
> On Mon, Jun 12, 2000 at 02:54:33PM +0200, Asger K. Alstrup Nielsen wrote:
>>
>> The highlights include:
>>
>> - Mayor clean up in the LyXText and inset handling by Juergen and
>> Lgb. This leads in the direction of a lot of new posibilities
>> for nesting
On 15-Jun-2000 Dekel Tsur wrote:
> I also want to add that routines for building forms automatically, can also
> be used for adding support for arbitrary latex packages: a text file will
> define the arguments/config commands to the package, and a form for changing
> these values will be
On Thu, 15 Jun 2000, Dekel Tsur wrote:
> To be more specific, lyxrc.C should contain a big array with entries for the
> lyxrc variables, each entry contains information like token name, default
> value, etc. Another field will be type (e.g. "printer", "screen fonts", etc.)
> which will be used
current CVS does not compile with KDE frontend due to the difference in
Dialogs class definition for KDE and Xforms frontends. Namely, Dialogs
class constructor expects LyXView* as its argument in Xforms frontend
(src/frontends/Dialogs.h src/frontends/xforms/Dialogs.C) and LyXFunc* as
an
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
>> How does one make a batch job for .lyx -> .dvi "conversion" ?
Andre> lyx2dvi:
Andre> #!/bin/sh lyx --export latex $1
BTW andre, did you document this flag somewhere? I found nothing in
the man page (hint!).
JMarc
Kayvan> This is on RH 6.1, default compiler/linker/etc.:
Kayvan> /bin/sh ./libtool --mode=compile c++ -DHAVE_CONFIG_H -I. -I. -I. -I./.. -I./..
-O2 -m486 -fno-strength-reduce -ansi -W -Wall -Wno-return-type -c marshal.cc
Kayvan> c++ -DHAVE_CONFIG_H -I. -I. -I. -I./.. -I./.. -O2 -m486
using configure --with-frontend=kde
configuration falls over if QT or KDE aren't installed in certain hardwired
locations. This is daft, since two shell variables are defined when running KDE
but not employed by the configure script.
Why not test
$KDEDIR (=/usr/local/kde on my system)
$QTDIR
> Andre> #!/bin/sh lyx --export latex $1
>
> BTW andre, did you document this flag somewhere? I found nothing in
> the man page (hint!).
Of course not ;-)
There had been some discussion on the naming of the flags and I
did not have the impression that the issue was settled. Until then
I did
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> There had been some discussion on the naming of the flags and I
Andre> did not have the impression that the issue was settled. Until
Andre> then I did not want to "officially" document the flag in order
Andre> to prevent people
On Fri, Jun 16, 2000 at 09:12:08AM +0200, Andre Poenitz wrote:
> > How does one make a batch job for .lyx -> .dvi "conversion" ?
>
> lyx2dvi:
>
> #!/bin/sh
> lyx --export latex $1
> latex $1
> latex $1
> latex $1
>
Why there is now lyx --export dvi option?
However, it is possible to use
lyx
On 16-Jun-2000 Angus Leeming wrote:
> using configure --with-frontend=kde
> configuration falls over if QT or KDE aren't installed in certain hardwired
> locations. This is daft, since two shell variables are defined when running KDE
> but not employed by the configure script.
>
> Why not test
> Why there is now lyx --export dvi option?
Erm... now that you mention it... I think lyx --export dvi
is possible, too. Stupid me...
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
> However, I think that resizing/rotation options should be added to the
> external inset.
Yes, I think so to. If you read the ExternalTemplate.lyx file, you will
notice that this is mentioned as a feature to implement for a volunteer.
I think it should be designed such that there are optional
It is very sad that LyX still can't support X keyboard other than
ISO-8859-1. It is one of those broken program for which I still need a
broken xmodmap. And I also don't think using LyX own keymaps is a good
thing, as the Xserver is ment to handle the keyboard.
The problem is, that when I have
Marko> current CVS does not compile with KDE frontend due to the difference in
Marko> Dialogs class definition for KDE and Xforms frontends. Namely, Dialogs
Marko> class constructor expects LyXView* as its argument in Xforms frontend
Marko> (src/frontends/Dialogs.h src/frontends/xforms/Dialogs.C)
On Fri, Jun 16, 2000 at 11:04:52AM +0300, Lior Silberman wrote:
> On Thu, 15 Jun 2000, Dekel Tsur wrote:
>
> > To be more specific, lyxrc.C should contain a big array with entries for the
> > lyxrc variables, each entry contains information like token name, default
> > value, etc. Another field
> all development has been done with the xforms code. The code in the kde
> directory was written as proof of concept a long, long time ago. As such, it
> has lagged behind...
>
> You are correct to report that the code in kde/Dialogs.C is inconsistent with
> that in xforms/Dialogs.C. It is
Hello,
I have imported a text document in lyx which contains « and » "french
quote"
How can i input them in my lyx document
compose + <+< does not works
is there a tips
There are a few things you need to know about this table. This manual is
set up --- by hand, mind you --- to print all of
>>Date: Fri, 16 Jun 2000 17:59:14 +0100
>>From: Yann MORERE <[EMAIL PROTECTED]>
>>To: LyX Users <[EMAIL PROTECTED]>, LyX devel <[EMAIL PROTECTED]>
>>Subject: [Q] How to generate the character « and »?
>>
>>Hello,
>>
>>I have imported a text document in lyx which contains « and » "french
> > No. You should write a python script that generates both the pstex and the
> > pstex_t files automatically (in the example above, the suffix of the
> > Postscript file should be changed from pstex to eps).
>
> By now, it would come as no surprise that I'd like to ask Dekel to submit
> a
On Fri, Jun 16, 2000 at 07:52:08PM +0300, Dekel Tsur wrote:
> > > No. You should write a python script that generates both the pstex and the
> > > pstex_t files automatically (in the example above, the suffix of the
> > > Postscript file should be changed from pstex to eps).
> >
> > By now, it
On Fri, Jun 16, 2000 at 01:08:47PM +0200, Asger K. Alstrup Nielsen wrote:
> If what you meant was to provide a small facility to allow the
> "safe" script constructs, sure we could do that. We already showed
> the way with the script for the external date inset which uses
> a general Python
Is there any idea when we might get visual feedback to the
"size" attribute for table cells? Or even a horizontal scrollbar when
tables go off-screen? Currently editing tables is virtually impossible.
I use the size for when I have a longer piece of text for a table cell and
I believe there is
On Fri, Jun 16, 2000 at 08:07:18PM +0300, Dekel Tsur wrote:
>
> Why not have support for ";" in the external figure code?
> (i.e. define UpdateCommand as "cmd1 parameters;cmd2 parameters;..." )
> This will save a call to python.
Better yet is, perhaps, to create a python secure module, that
On Fri, Jun 16, 2000 at 01:18:49PM +0200, Asger K. Alstrup Nielsen wrote:
> > However, I think that resizing/rotation options should be added to the
> > external inset.
>
> Yes, I think so to. If you read the ExternalTemplate.lyx file, you will
> notice that this is mentioned as a feature to
> > Why not have support for ";" in the external figure code?
> > (i.e. define UpdateCommand as "cmd1 parameters;cmd2 parameters;..." )
> > This will save a call to python.
>
> Better yet is, perhaps, to create a python secure module, that could be used as
> a wrapper around safe system calls.
> For some strange reason, I named the script fig2psfig.py, where it should be
> fig2pstex.py.
> Here is a fixed patch.
This patch set is good. Thanks Dekel ;-)
Could somebody please apply it to the cvs?
Thanks,
Asger
> > Yes, I think so to. If you read the ExternalTemplate.lyx file, you will
> > notice that this is mentioned as a feature to implement for a volunteer.
>
> I've added more options to the external inset: the ability to resize/rotate
> the result (the resize buttons doesn't work yet).
>
> I also
> An alternative approach would be to keep all the member variables, without
> having the query_* methods.
> The only disadvantage of this (comparing to your suggestion) is that adding
> a new variable requires adding two lines (one in lyxrc.C and one in lyxrc.h)
> instead of one (in lyxrc.C),
62 matches
Mail list logo
