Norbert | 1 May 2011 20:10
Picon

Error tracing with Winedt

Hello,
I am using Winedt 6.0 with Latex for a several hundred pages document.
For this I have a short MASTER file which includes all chapters using 
the include statemet
\include{chapter1}
\include{chapter2} 
\include{chapter3} etc.

Winedt has the nice feature that - if errors are found by Latex - it jumps
to the line where the error is. Say, if there is an error in chapter2, line 110,
it jumps to this line and highlights it red.
It did work for me so far, but since some days
it jumps instead to the last line of the MASTER file. 

Is there a way to control this?
Many thanks for a hint.
Norbert

Hermann-Josef Röser | 2 May 2011 11:48
Picon
Favicon

AW: Error tracing with Winedt

Hello,

I had the same problem. Please check the forum for topic "Cursor position
following a LaTeX-error" and you will hopefully find the solution.

Best wishes

Hermann-Josef Röser

Norbert Wermes | 2 May 2011 13:09
Picon

Re: AW: Error tracing with Winedt

Hello,
thanks for the hint. I must admit that the thread about "Coursor position following a LaTex-error" is fairly long
with various changes in what worked and what not. I could not extract the exact fix which I have to do and which build I have to load.
Could you point me to the hint that worked for you?
Thanks in advance
Norbert

On 02.05.2011 11:48, Hermann-Josef Röser wrote:
Hello, I had the same problem. Please check the forum for topic "Cursor position following a LaTeX-error" and you will hopefully find the solution. Best wishes Hermann-Josef Röser

-- Norbert Wermes Professor of Physics phone +49 - 228 - 73 - 3533 (office) Bonn University +49 - 228 - 73 - 3225 (secretary) Physikalisches Institut fax +49 - 228 - 73 - 3220 Nussallee 12 email: wermes <at> uni-bonn.de 53115 Bonn http://hep1.physik.uni-bonn.de Germany
Bernhard Starck | 2 May 2011 19:31
Picon

pdf preview

Dear list members and  WinEdt experts,

my configuration deals with WinEdt 6  and the PDF Converter (Nuance) as pdf viewer. Therefore I have done the chances  in the Execution Modes dialog (PDF Viewer). The Autodetekt option is not selected, but this not seams to be the reason of the following problem.

 

 When I compile a tex file at the first time everything is fine, the pdf converter opened up automatically and displays the result.  During the second and all other compile runs I get the error code from pdflatex: “I cannot write on file …  Please type another file name for output: “  This is of course WinEdt is not able to close the pdf viewer automatically  I think.

 

A study of editing the PDFCloseDoc.edt and other macros doesn’t solve the problem.  What is to do?

 

Thank You for your help

 

Best regards

Bernhard Starck

 

 

WinEdt Team | 2 May 2011 23:10

Re: pdf preview

> my configuration deals with WinEdt 6 and the PDF Converter (Nuance)
> as pdf viewer. Therefore I have done the chances in the Execution
> Modes dialog (PDF Viewer). The Autodetekt option is not selected,
> but this not seams to be the reason of the following problem.
>
> When I compile a tex file at the first time everything is fine, the
> pdf converter opened up automatically and displays the result.
> During the second and all other compile runs I get the error code
> from pdflatex: "I cannot write on file . Please type another file
> name for output: " This is of course WinEdt is not able to close
> the pdf viewer automatically I think.
>
> A study of editing the PDFCloseDoc.edt and other macros doesn't
> solve the problem. What is to do?
 
In other words PDF Converter (Nuance) locks pdf file that it is
previewing (like most pdf viewers)...
 
You will either have to manually close the file in Nunace or else
read Nuance's documentation to find out is the viewer provides any
means to close a document from another application. Adobe Reader
allows DDE, PDFX-Change has command line switches, Sumatra does
not lock the file at all, etc... If the Nuance does not provide
any means to be told to release a pdf file then there is nothing
WinEdt can do. If it does, then perhaps something could be added
to PDFCloseDoc.edt to make it recognize Nuance and act
accordingly.
 
Best regards,
 
alex

 

WinEdt Team | 2 May 2011 23:13

Re: Error tracing with Winedt

> thanks for the hint. I must admit that the thread about "Coursor
> position following a LaTex-error" is fairly long with various
> changes in what worked and what not. I could not extract the exact
> fix which I have to do and which build I have to load. Could you
> point me to the hint that worked for you?

For start: what is your build of WinEdt (Help -> About Dialog)?

Improvements were made in the March Build of WinEdt 6 when it comes
to parsing log files for errors. Previous builds have problems
(especially when filenames and paths of included files are long).

If you have the latest build take a good look at log file. It is
possible that filenames in log file are wrapped in two lines and
that would spell trouble in most cases... The reason for such
change can be explained by close inspection of log file.

Best regards,

alex

Seva | 10 May 2011 12:08
Picon

Re: Problem with DDEOpen and Adobe X and WinEdt 6.0

> > I am using WinEdt 6 [Build: 20110119 (v. 6.0)] and Adobe Acrobat X Pro,
> > and I get the following error message if I run PDFTexify with the 
> > previously created document still open:
> >    Cannot Open DDE Link to:
> >    "C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe
> >    Service: Acroview
> >    Topic: Control
> >    DDEOpen("%$('PDF-View')","%$('Acro-DDE_Service');","%$('Acro-
DDE_Topic');");

> Try:
> 
>   DDEOpen("%$('PDF-View')","AcroviewA10","%$('Acro-DDE_Topic');");

I have the very same problem as described above, except that I use WinEdt 5.5, 
and the last line of the error message that I get is
         DDEOpen('%$("AcroRead")',"acroview","control");
This is line 36 of the file "Acrobat CloseDoc.edt", and I suppose that just 
modifying this line appropriately should solve the problem. Is this correct? 
Exactly how should I modify it? (An expert would probably have figured 
this out from the answer given above, but it doesn't tell much to a non-expert 
like me...)

Many thanks in advance!

Maheswaran, M | 10 May 2011 17:13
Favicon

RE: Re: Problem with DDEOpen and Adobe X and WinEdt 6.0

Hi!

Here are the replies that I sent to the list on February 19, 2011, to the same question:

Message 1:

I am using Winedt 5.5. 
When I upgraded to Acrobat 10, I had the same DDE problem.
After scouring the web I found the following solution:

I went to the file      .....\Winedt Team\Winedt\exe\Acrobat OpenDoc.edt   .... Line 106 
and I changed   DDEOpen('%$("AcroRead")',"acroview","control",0);     
to  DDEOpen('%$("AcroRead")',"acroviewR10","control",0);

Now, I don't have the DDE problem.  I hope it works for you.

Message 2:

Further to my previous message, the change to acroviewR10 is for those using the Reader.

If someone uses the full Acrobat I believe that the change should be to acroviewA10.

Mahes

-----Original Message-----
From: Seva [mailto:wpooh62 <at> mail.ru] 
Sent: Tuesday, May 10, 2011 5:08 AM
To: winedt+list <at> wsg.net
Subject: [WinEdt] Re: Problem with DDEOpen and Adobe X and WinEdt 6.0

> > I am using WinEdt 6 [Build: 20110119 (v. 6.0)] and Adobe Acrobat X Pro,
> > and I get the following error message if I run PDFTexify with the 
> > previously created document still open:
> >    Cannot Open DDE Link to:
> >    "C:\Program Files\Adobe\Acrobat 10.0\Acrobat\Acrobat.exe
> >    Service: Acroview
> >    Topic: Control
> >    DDEOpen("%$('PDF-View')","%$('Acro-DDE_Service');","%$('Acro-
DDE_Topic');");

> Try:
> 
>   DDEOpen("%$('PDF-View')","AcroviewA10","%$('Acro-DDE_Topic');");

I have the very same problem as described above, except that I use WinEdt 5.5, 
and the last line of the error message that I get is
         DDEOpen('%$("AcroRead")',"acroview","control");
This is line 36 of the file "Acrobat CloseDoc.edt", and I suppose that just 
modifying this line appropriately should solve the problem. Is this correct? 
Exactly how should I modify it? (An expert would probably have figured 
this out from the answer given above, but it doesn't tell much to a non-expert 
like me...)

Many thanks in advance!

Erie Morales | 10 May 2011 21:53
Picon
Favicon

auxiliary files

Hello Everyone,

Some time ago Karl posted a solution so that the auxiliary files used when 
compiling (PdfTexify) would be stored in a MikTex folder rather than the working 
folder.  Yes, I only want my tex and pdf file in my working folder, I am tired 
of manually deleting the bunch.  I went back to his email to try to implement 
this on my WinEdt6 but looking at Options> Execution Mode>Tex does not seem to 
give the option of storing auxiliary files in another (any) folder.  Any body 
would be kind to give me a hint on how to work it in WinEdt?

Thanks,

Erie  

 Dr Erie Morales
University of Pennsylvania
Material Science and Engineering

Karl Koeller | 10 May 2011 22:05

Re: auxiliary files

Il 10/05/2011 21.53, Erie Morales ha scritto:
> Hello Everyone,
>
> Some time ago Karl posted a solution so that the auxiliary files used when
> compiling (PdfTexify) would be stored in a MikTex folder rather than the working
> folder.  Yes, I only want my tex and pdf file in my working folder, I am tired
> of manually deleting the bunch.  I went back to his email to try to implement
> this on my WinEdt6 but looking at Options>  Execution Mode>Tex does not seem to
> give the option of storing auxiliary files in another (any) folder.  Any body
> would be kind to give me a hint on how to work it in WinEdt?
>
> Thanks,
>
> Erie
>
>   Dr Erie Morales
> University of Pennsylvania
> Material Science and Engineering
>
The only thing you have to do is to create a subfolder named 'TeXAux' 
where your source is.
I recommend you to download the latest winedt build where this option is 
well implemented.
If you want to change 'TeXAux' name you can do it from 
Options->Execution Modes->TeX Options->TeX Auxiliary Output Folder


Gmane