Pavel Sanda wrote:
> Juergen, can i apply it to branch too?
Yes.
Jürgen
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> >> It would be useful, but I think nevertheless that we should try to think
> >> about more understandable names. Each function likes to have its own
> >> variables, and we have no complete vision of this.
> >
> > so what is your proposal?
>
> N
Pavel Sanda writes:
>> It would be useful, but I think nevertheless that we should try to think
>> about more understandable names. Each function likes to have its own
>> variables, and we have no complete vision of this.
>
> so what is your proposal?
Now: apply your patch
Later: rewrite everyth
Jean-Marc Lasgouttes wrote:
> Pavel Sanda writes:
> > i think the intention was that $$p is path of the input file
> > not path of the original file.
> >
> > that said i'm not against adding new $$r variable. opinions?
>
> It would be useful, but I think nevertheless that we should try to think
>
Pavel Sanda writes:
> i think the intention was that $$p is path of the input file
> not path of the original file.
>
> that said i'm not against adding new $$r variable. opinions?
It would be useful, but I think nevertheless that we should try to think
about more understandable names. Each funct
Roland Clobus wrote:
> Reading the code:
> * infile2 and outfile2 are made relative paths by using the path part of
> from_file
> * from_base is from_file with no extension.
>
> > possibly we can use another $$ variable
>
> $$p for Path to the original file looks ok to me:
i think the intention
> Roland Clobus wrote:
> > > Pavel Sanda wrote:
> > > you are right, that there is a bug that $$p is not used. however
> this
> > > patch
> > > looks suspicious from the first sight, as $$i is stuffed from
> infile2
> > > while
> > > your $$p is stuffed from orig_from. according to the doc $$p
shou
Roland Clobus wrote:
> > Pavel Sanda wrote:
> > you are right, that there is a bug that $$p is not used. however this
> > patch
> > looks suspicious from the first sight, as $$i is stuffed from infile2
> > while
> > your $$p is stuffed from orig_from. according to the doc $$p should
> > originate
>
> > Roland Clobus wrote:
> > ...
> > In the
> > code (Converter.cpp) I found "$$p" which was declared but not in
use.
> > This patch places the path to the current LyX file in $$p, which can
> > be used by the converter to reach the images.
> Pavel Sanda wrote:
> you are right, that there is a bug
Roland Clobus wrote:
> Hello,
>
> I was looking for a method to modify my LyX file and let LyX parse the
> modified file (LyX file -> LyX file with modifications -> PDF). I
> noticed that the images would cause problems, because the directory
> structure of the images is not copied to the temporar
Hello,
I was looking for a method to modify my LyX file and let LyX parse the
modified file (LyX file -> LyX file with modifications -> PDF). I
noticed that the images would cause problems, because the directory
structure of the images is not copied to the temporary directory. In the
code (Convert
11 matches
Mail list logo
