> I think that we should add makefile like rules to the external_templates file
> (instead of the UpdateCommand fields).
> For example,
>
> Template XFig
> ...
> Format LaTeX
> Product \\includegraphics{$$Basename.eps}\\input{$$Basename.tex}
> # targetsource command ($$S/$$T ar
On Fri, Jun 16, 2000 at 07:52:08PM +0300, Dekel Tsur wrote:
>
> Now, I have two complaints about the inset:
>
> 1. The UpdateCommand is always called, even if we already generated the
> product files.
I think that we should add makefile like rules to the external_templates file
(instead of the
> On 17-Jun-2000 Dekel Tsur wrote:
> > I've updated the patch, but I haven't added an option to disenable the
> > resize/rotate controls according to the template.
>
> I'll wait for Asgers comment to apply this.
I have a few questions to Dekel regarding the patch:
- Would it not be beneficial t
Hello!
I would like to second that.
Only the actual user must be permitted to specify which
programs to run.
Maximum which lyx can do is supply the parameters.
Quoting r. Asger K. Alstrup Nielsen ([EMAIL PROTECTED]) "Re: Insert xfig":
> > > PS (to Asger) The need for writ
> For some strange reason, I named the script fig2psfig.py, where it should be
> fig2pstex.py.
> Here is a fixed patch.
Applied and commited!
Jürgen
-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._-._
Dr. Jürgen Vigna E-Mail: [EMAIL PROTECTED]
Italien
On 17-Jun-2000 Dekel Tsur wrote:
>
> I've updated the patch, but I haven't added an option to disenable the
> resize/rotate controls according to the template.
>
I'll wait for Asgers comment to apply this.
> The patch also fixes a bug in LibFileSearch (support/filetools.C):
> The correct orde
Thank you for your explanation, Asger.
Andre'
--
It'll take a long time to eat 63.000 peanuts.
André Pönitz . [EMAIL PROTECTED]
> What's the problem with calling transfig with system(3)?
At some point, the call will be expanded using a pattern like this:
fig2dev $$Parameters $$Filename
where Parameters and Filename comes from the document.
Now, I could type in a filename such as "`rm -Rf /`" into my
XFig external ins
> Better yet is, perhaps, to create a python secure module, that could be used as
> a wrapper around safe system calls. What do you think? (Asger and others...)
I wonder why we need python at all. Ok, I haven't had time to look at
the new "external" inset so maybe I am missing something very o
On Fri, Jun 16, 2000 at 11:52:20PM +0200, Asger K. Alstrup Nielsen wrote:
> What do others think? Is it a good idea to have resizing and
> rotating available for all external insets, when maybe 90% will
> be able to use one or both options?
> Maybe it would be best to provide a bool in the templ
> > 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
> 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
> > 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.
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 impl
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 co
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
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 w
> > 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 patc
> 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 pa
> > 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 to be
> > "cmd1;cmd2;.." with the meanning to execute cmd1, then cmd2 etc. ?
> > And what is the difference between pic2png_eps.py and pic2png_eps.sh
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 UpdateCo
On Thu, Jun 15, 2000 at 05:38:56PM -0300, Garst R. Reese 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).
> Hmm, when I export fr
Dekel Tsur wrote:
>
> > > Changing Basename.pstex to Basename.pstex_t gave me one error box,
> > > \epsfig not defined
> > > What package am I missing?
> > > Garst
> > Duh, \usepackage{epsfig}
>
> I think that pstex_t file should be generated without a command to include
> the Postscript file (i
> > Changing Basename.pstex to Basename.pstex_t gave me one error box,
> > \epsfig not defined
> > What package am I missing?
> > Garst
> Duh, \usepackage{epsfig}
I think that pstex_t file should be generated without a command to include
the Postscript file (i.e., only with the labels), and the c
"Garst R. Reese" wrote:
>
> "Garst R. Reese" wrote:
> >
> > Andre Poenitz wrote:
> > >
> > > > When you find the best format, please let us know.
> > > > Dekel mentioned that ps_tex was the best. If so, please
> > > > provide a patch to update the XFig template to use that
> > > > format.
> > >
>
"Garst R. Reese" wrote:
>
> Andre Poenitz wrote:
> >
> > > When you find the best format, please let us know.
> > > Dekel mentioned that ps_tex was the best. If so, please
> > > provide a patch to update the XFig template to use that
> > > format.
> >
> > The best option IMNSHO is the combined Te
Andre Poenitz wrote:
>
> > When you find the best format, please let us know.
> > Dekel mentioned that ps_tex was the best. If so, please
> > provide a patch to update the XFig template to use that
> > format.
>
> The best option IMNSHO is the combined TeX/ps version.
>
> Andre'
>
OK, xfig has
"Asger K. Alstrup Nielsen" wrote:
>
> > Shucks. I've been converting them to .eps, but that means if I want to
> > send the document to someone I have to send the .eps files as well or
> > send the .fig files with a bunch of instructions. But its no big deal.
> > I'll experiment with xfigs export
> When you find the best format, please let us know.
> Dekel mentioned that ps_tex was the best. If so, please
> provide a patch to update the XFig template to use that
> format.
The best option IMNSHO is the combined TeX/ps version.
Andre'
--
It'll take a long time to eat 63.000 peanuts.
Andr
> Shucks. I've been converting them to .eps, but that means if I want to
> send the document to someone I have to send the .eps files as well or
> send the .fig files with a bunch of instructions. But its no big deal.
> I'll experiment with xfigs export options.
When you find the best format, ple
Dekel Tsur wrote:
>
> On Tue, Jun 13, 2000 at 05:47:18PM -0300, Garst R. Reese wrote:
> > All goes well until I try to ViewPostscript, then it complains
> > extensively about numbers being missing and illegal units of measure.
> > teTeX-1, ImageMagik-5.2.0
>
> The default behavior for a xfig fil
On Tue, Jun 13, 2000 at 05:47:18PM -0300, Garst R. Reese wrote:
> All goes well until I try to ViewPostscript, then it complains
> extensively about numbers being missing and illegal units of measure.
> teTeX-1, ImageMagik-5.2.0
The default behavior for a xfig file is to convert it to TeX picture
All goes well until I try to ViewPostscript, then it complains
extensively about numbers being missing and illegal units of measure.
teTeX-1, ImageMagik-5.2.0
But, it is sooo nice an idea.
Garst
33 matches
Mail list logo
