[tex-live] Problem with perl in Windows 7
Siep Kroonenberg
siepo at cybercomm.nl
Wed Jan 11 09:44:32 CET 2012
On Wed, Jan 11, 2012 at 12:39:51AM +0100, Reinhard Kotucha wrote:
> On 2012-01-11 at 04:05:58 +0700, Robert B. Gozzoli wrote:
>
> > Dear John and all list members,
> > I thank you for the email. When I run Biber through the command
> > line, it works fine. I attach the log file here at the bottom. Even
> > with emacs, pressing C-c C-c, does not give me any problem about
> > it. And I have to press it a few times, but I can get the final PDF
> > with Xelatex. It is with something like Texworks or WinEdt that the
> > problem come out. Even invoking biber in Texworks does not do
> > anything. The warnings about entries not found are my fault for not
> > putting them there yet. Utils.pm just complains about that. I use
> > the identical file in my netbook, so I am sure that the file is
> > fine.
> >
> > Thus, I believe the problem goes back to perl, that is somehow
> > corrupted. I can use emacs, and running cyclically for the
> > output. But the point is that if perl get corrupted, a way to
> > restore it would be nice.
>
> If you can run Biber successfully from the command line, then neither
> Biber nor Perl can be corrupted. Emacs actually doesn't do anything
> else than invoking programs on the command line.
>
> If things don't work with TeXworks or WinEdt, please look into their
> configuration files. Maybe they are not consistent.
Maybe TW path settings? Check Edit > Preferences > Typesetting tab.
There is an item `Paths for TeX and related programs' which prepends
some directories to the regular searchpath.
--
Siep Kroonenberg
More information about the tex-live
mailing list