> > but compilation in lyx does (as can be seen in
> > Tools->Preferences...->Paths->TEXINPUTS prefix:)
> >
> > In fact, the entries in clsFiles.lst are missing now.
>
> This is because TeXFiles.py is called without setting TEXINPUTS.
> Moreover, there is also
creation is OK though.
> So the "configure.py" apparently does not honour the lyxrc.dist entry
> '\texinputs_prefix ".:/usr/local/share/lyx2.3/tex"'
> but compilation in lyx does (as can be seen in
> Tools->Preferences...->Paths->TEXINPUTS prefix:)
>
ist can be used to
> > augment the TEXINPUTS path.
>
> Good idea. But until now, there are only
> "development/(MacOSX|cygwin)/lyxrc.dist.in" present.
I implemented it now in cmake build. At first, everything seemed to work.
Reconfiguring lyx...
Load examples/chessgame.lyx
t; > But this dir is not part of the list 'kpsepath tex'.
> > If a new user starts lyx, he/she has either set the environment TEXINPUTS
> > or expand the path in preferences.
> >
> > Under cmake we add the data to "/usr/(local/)?share/texmf/tex/latex/lyx2
ts lyx, he/she has either set the environment TEXINPUTS
> or expand the path in preferences.
>
> Under cmake we add the data to "/usr/(local/)?share/texmf/tex/latex/lyx2.3",
> but that requires that this directory is used by kpsepath. Which is not the
> case
> if using
Hi,
I am struggling on the best install directory for our tex files.
ATM, automake installs them for unix at lyx-system-dir/tex.
But this dir is not part of the list 'kpsepath tex'.
If a new user starts lyx, he/she has either set the environment TEXINPUTS
or expand the path in preferenc
On Sun, Oct 16, 2011 at 11:55:51PM +0200, Uwe Stöhr wrote:
> Am 16.10.2011 19:29, schrieb Enrico Forestieri:
>
> >>When replaced by If.
> >
> >And, according to you, that's the grammar error?
>
> Our docs were during the last year kindly reviewed by Mr. Hudson - a
> lector in a publishing compan
Am 16.10.2011 19:29, schrieb Enrico Forestieri:
When replaced by If.
And, according to you, that's the grammar error?
Our docs were during the last year kindly reviewed by Mr. Hudson - a lector in a publishing company.
He corrected almost all my when to if for the case that when was to refe
On Sun, Oct 16, 2011 at 04:54:11PM +0200, Uwe Stöhr wrote:
> Am 16.10.2011 11:18, schrieb Enrico Forestieri:
>
> >>What is so difficult to have a look at my initial post of this thread.
> >
> >Yes, I saw it, but I still don't know what grammar errors you are
> >referring to.
>
> When replaced by
Am 16.10.2011 11:18, schrieb Enrico Forestieri:
What is so difficult to have a look at my initial post of this thread.
Yes, I saw it, but I still don't know what grammar errors you are
referring to.
When replaced by If.
On Sun, Oct 16, 2011 at 04:25:26AM +0200, Uwe Stöhr wrote:
> Am 15.10.2011 23:46, schrieb Enrico Forestieri:
>
> >I don't know what grammar errors you are referring to,
>
> What is so difficult to have a look at my initial post of this thread.
Yes, I saw it, but I still don't know what grammar
Am 15.10.2011 23:46, schrieb Enrico Forestieri:
I'm giving up, but you should try yourself to answer the following
question. What happens if TEXINPUTS is already set in the environment
when LyX is launched?
Then it would be a prefix. But this is not the case except I add this var
; in a batch file). But then it is no prefix to an
> existing variable, but the variable itself. That was my initial
> point.
I'm giving up, but you should try yourself to answer the following
question. What happens if TEXINPUTS is already set in the environment
when LyX is launched?
Am 15.10.2011 22:41, schrieb Enrico Forestieri:
http://en.wikipedia.org/wiki/Environment_variable#Local_to_process
So it is only available while LyX is executed (as if I use the command "set" in a batch file). But
then it is no prefix to an existing variable, but the variable itself. That was
On Sat, Oct 15, 2011 at 10:13:34PM +0200, Uwe Stöhr wrote:
> Am 15.10.2011 19:31, schrieb Enrico Forestieri:
>
> >>As I understand the explanation TEXINPUTS is an _environment
> >>variable_ consisting of a list of paths. So why is it then also a
> >>_prefix_?
>
Am 15.10.2011 19:31, schrieb Enrico Forestieri:
As I understand the explanation TEXINPUTS is an _environment
variable_ consisting of a list of paths. So why is it then also a
_prefix_?
Because TEXINPUTS may already be set in the environment,
I must admit that I then did not yet understand
On Sat, Oct 15, 2011 at 04:18:39AM +0200, Uwe Stöhr wrote:
> As I understand the explanation TEXINPUTS is an _environment
> variable_ consisting of a list of paths. So why is it then also a
> _prefix_?
Because TEXINPUTS may already be set in the environment, in which case
its content
Hi Enrico,
in your announcement text for the TEXINPUTS feature you write
"The support for using external files in ERT has been improved by the
introduction of a prefix for the TEXINPUTS environment variable.
This prefix can be set..."
As I understand the explanation TEXIN
Enrico Forestieri wrote:
> > that was the second check you forced me to do :)
>
> Sorry?
"doublecheck" in mails above. p
ess fucntions.
> looking again, there is always path.empty()?, so it should
> be ok...
Yes, that and also the fact that if you keep empty the TEXINPUTS prefix,
the environment is not touched, path.empty() or not.
> that was the second check you forced me to do :)
Sorry?
--
Enrico
Enrico Forestieri wrote:
> only an environment variable is
> added before launching converters.
yep thats what i meant; went only smoothly though those parts
and saw new code around startscript/process fucntions.
looking again, there is always path.empty()?, so it should
be ok... that was the sec
On Tue, May 10, 2011 at 11:39:21AM +0200, Pavel Sanda wrote:
> Enrico Forestieri wrote:
> > > i would be more careful about the
> > > systemcall part, it looks quite invasive and in very sensitive area of
> > > code.
> >
> > Uh? What do you mean?
>
> to double check anything which touches Syste
Enrico Forestieri wrote:
> > i would be more careful about the
> > systemcall part, it looks quite invasive and in very sensitive area of code.
>
> Uh? What do you mean?
to double check anything which touches SystemCallXXX::
pavel
On Tue, May 10, 2011 at 11:06:17AM +0200, Pavel Sanda wrote:
> Richard Heck wrote:
> >> To conclude, note that even if the patch may seem large, it is really
> >> simple and not invasive, such that it can be safely backported to branch.
> >>
> > What's the policy as regards preference changes? We
Richard Heck wrote:
>> To conclude, note that even if the patch may seem large, it is really
>> simple and not invasive, such that it can be safely backported to branch.
>>
> What's the policy as regards preference changes? We don't need to add this
> to prefs2prefs, or increase the preferences fo
other
ancillary programs (such as dvi previewers) only if the document dir is
placed in the TEXINPUTS environment variable.
The attached patch adds the document dir and all of its subdirs to
TEXINPUTS, such that the attached example in the tar archive works in LyX.
I would like to start a
illary programs (such as dvi previewers) only if the document dir is
> > placed in the TEXINPUTS environment variable.
> >
> > The attached patch adds the document dir and all of its subdirs to
> > TEXINPUTS, such that the attached example in the tar archive works in LyX.
&
On 05/08/2011 02:45 PM, Enrico Forestieri wrote:
> The \input@path mechanism (already used by LyX) is not always sufficient
> and there are cases where a file can be found by LaTeX and also by other
> ancillary programs (such as dvi previewers) only if the document dir is
> placed in t
The \input@path mechanism (already used by LyX) is not always sufficient
and there are cases where a file can be found by LaTeX and also by other
ancillary programs (such as dvi previewers) only if the document dir is
placed in the TEXINPUTS environment variable.
The attached patch adds the
29 matches
Mail list logo
