gmane.editors.winedt

Log examination

I'm using Winedt build 20071003 (v. 5.5). The minimal input is the file 
showing my problem is

--------------------------------------------
\documentclass[12pt]{article}
\begin{document}
Hello world!
\end{document}
-------------------------------------------

I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7). 
Next, I hit the log button in Winedt. That causes a pop up warning (and 
no log display at screen bottom). The warning says

  ")" Expected
  [FindError(1,1,0,1,0,0 ^^^,0,4);]

I have no idea what this means or what to do about it. BTW, all was 
working but I haven't done any tex-ing for a while and now this - no 
updates since installation. Any ideas what is going on and what to do 
about it. The log file is included below. Thanks for any help.

-- Jeff Barnett

------------------------------ LOG FILE 
------------------------------------------
This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (preloaded 
format=latex 2008.2.12)  13 APR 2008 22:25
entering extended mode
**test.tex

(Continue reading)

headers

Nicolas Vaughan | 14 Apr 08:02

Re: Log examination

Are you sure this is the log of the LaTeX code you posted? I rephrase the question: are you sure WinEdt is running pdfLaTeX on that file.

I wonder this, because your log states that pdfTeX is loading the babel package, and that isn't stated in your source file.

Check whether your main file in WinEdt is the one you want to compile (Project -> Set Main File).

Regards,

Nicolas Vaughan

On Mon, Apr 14, 2008 at 12:41 AM, Bernice Barnett <jbbrus <at> ca.rr.com> wrote:

I'm using Winedt build 20071003 (v. 5.5). The minimal input is the file showing my problem is

--------------------------------------------
\documentclass[12pt]{article}
\begin{document}
Hello world!
\end{document}
-------------------------------------------

I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7). Next, I hit the log button in Winedt. That causes a pop up warning (and no log display at screen bottom). The warning says

")" Expected
[FindError(1,1,0,1,0,0 ^^^,0,4);]

I have no idea what this means or what to do about it. BTW, all was working but I haven't done any tex-ing for a while and now this - no updates since installation. Any ideas what is going on and what to do about it. The log file is included below. Thanks for any help.

-- Jeff Barnett

------------------------------ LOG FILE ------------------------------------------
This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (preloaded format=latex 2008.2.12) 13 APR 2008 22:25
entering extended mode
**test.tex
(test.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, dumylang, nohyphenation, lo
aded.
("C:\Program Files\MiKTeX 2.7\tex\latex\base\article.cls"
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
("C:\Program Files\MiKTeX 2.7\tex\latex\base\size12.clo"
File: size12.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
)
\c <at> part=\count79
\c <at> section=\count80
\c <at> subsection=\count81
\c <at> subsubsection=\count82
\c <at> paragraph=\count83
\c <at> subparagraph=\count84
\c <at> figure=\count85
\c <at> table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (test.aux)
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
[1

]
(test.aux) )
Here is how much of TeX's memory you used:
203 strings out of 95353
1988 string characters out of 1184550
45983 words of memory out of 1500000
3479 multiletter control sequences out of 110000
3938 words of font info for 15 fonts, out of 1200000 for 2000
14 hyphenation exceptions out of 8191
22i,4n,19p,137b,107s stack positions out of 5000i,500n,10000p,200000b,5000s

Output written on test.dvi (1 page, 248 bytes).

headers

Bernice Barnett | 14 Apr 08:09

Re: Log examination

Yes - I think Miktex always runs pdfLaTeX and I'm sure the log file is 
the correct one. I also believe that the hyphen patterns are supplied by 
Miktex through configuration and that might be the origin of the 
reference to babel. Also I always run the default project with no main 
file set so latex applies to the file I'm editing.

-- Jeff Barnett

Nicolas Vaughan wrote:
> Are you sure this is the log of the LaTeX code you posted? I rephrase 
> the question: are you sure WinEdt is running pdfLaTeX on that file.
>
> I wonder this, because your log states that pdfTeX is loading the 
> babel package, and that isn't stated in your source file.
>
> Check whether your main file in WinEdt is the one you want to compile 
> (Project -> Set Main File).
>
> Regards,
>
> Nicolas Vaughan
>
>
>
>
> On Mon, Apr 14, 2008 at 12:41 AM, Bernice Barnett <jbbrus <at> ca.rr.com 
> <mailto:jbbrus <at> ca.rr.com>> wrote:
>
>     I'm using Winedt build 20071003 (v. 5.5). The minimal input is the
>     file showing my problem is
>
>     --------------------------------------------
>     \documentclass[12pt]{article}
>     \begin{document}
>     Hello world!
>     \end{document}
>     -------------------------------------------
>
>     I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX
>     2.7). Next, I hit the log button in Winedt. That causes a pop up
>     warning (and no log display at screen bottom). The warning says
>
>      ")" Expected
>      [FindError(1,1,0,1,0,0 ^^^,0,4);]
>
>     I have no idea what this means or what to do about it. BTW, all
>     was working but I haven't done any tex-ing for a while and now
>     this - no updates since installation. Any ideas what is going on
>     and what to do about it. The log file is included below. Thanks
>     for any help.
>
>     -- Jeff Barnett
>
>     ------------------------------ LOG FILE
>     ------------------------------------------
>     This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (preloaded
>     format=latex 2008.2.12)  13 APR 2008 22:25
>     entering extended mode
>     **test.tex
>     (test.tex
>     LaTeX2e <2005/12/01>
>     Babel <v3.8h> and hyphenation patterns for english, dumylang,
>     nohyphenation, lo
>     aded.
>     ("C:\Program Files\MiKTeX 2.7\tex\latex\base\article.cls"
>     Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
>     ("C:\Program Files\MiKTeX 2.7\tex\latex\base\size12.clo"
>     File: size12.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
>     )
>     \c <at> part=\count79
>     \c <at> section=\count80
>     \c <at> subsection=\count81
>     \c <at> subsubsection=\count82
>     \c <at> paragraph=\count83
>     \c <at> subparagraph=\count84
>     \c <at> figure=\count85
>     \c <at> table=\count86
>     \abovecaptionskip=\skip41
>     \belowcaptionskip=\skip42
>     \bibindent=\dimen102
>     ) (test.aux)
>     LaTeX Font Info:    Checking defaults for OML/cmm/m/it on input
>     line 2.
>     LaTeX Font Info:    ... okay on input line 2.
>     LaTeX Font Info:    Checking defaults for T1/cmr/m/n on input line 2.
>     LaTeX Font Info:    ... okay on input line 2.
>     LaTeX Font Info:    Checking defaults for OT1/cmr/m/n on input line 2.
>     LaTeX Font Info:    ... okay on input line 2.
>     LaTeX Font Info:    Checking defaults for OMS/cmsy/m/n on input
>     line 2.
>     LaTeX Font Info:    ... okay on input line 2.
>     LaTeX Font Info:    Checking defaults for OMX/cmex/m/n on input
>     line 2.
>     LaTeX Font Info:    ... okay on input line 2.
>     LaTeX Font Info:    Checking defaults for U/cmr/m/n on input line 2.
>     LaTeX Font Info:    ... okay on input line 2.
>     [1
>
>     ]
>     (test.aux) )
>     Here is how much of TeX's memory you used:
>     203 strings out of 95353
>     1988 string characters out of 1184550
>     45983 words of memory out of 1500000
>     3479 multiletter control sequences out of 110000
>     3938 words of font info for 15 fonts, out of 1200000 for 2000
>     14 hyphenation exceptions out of 8191
>     22i,4n,19p,137b,107s stack positions out of
>     5000i,500n,10000p,200000b,5000s
>
>     Output written on test.dvi (1 page, 248 bytes).
>
>

headers

Nicolas Vaughan | 14 Apr 08:48

Re: Log examination

Have you tried running pdfLaTeX through the command line (DOS prompt)?

On Mon, Apr 14, 2008 at 1:09 AM, Bernice Barnett <jbbrus <at> ca.rr.com> wrote:

Yes - I think Miktex always runs pdfLaTeX and I'm sure the log file is the correct one. I also believe that the hyphen patterns are supplied by Miktex through configuration and that might be the origin of the reference to babel. Also I always run the default project with no main file set so latex applies to the file I'm editing.

-- Jeff Barnett

Nicolas Vaughan wrote:

Are you sure this is the log of the LaTeX code you posted? I rephrase the question: are you sure WinEdt is running pdfLaTeX on that file.

I wonder this, because your log states that pdfTeX is loading the babel package, and that isn't stated in your source file.

Check whether your main file in WinEdt is the one you want to compile (Project -> Set Main File).

Regards,

Nicolas Vaughan

On Mon, Apr 14, 2008 at 12:41 AM, Bernice Barnett <jbbrus <at> ca.rr.com <mailto:jbbrus <at> ca.rr.com>> wrote:

I'm using Winedt build 20071003 (v. 5.5). The minimal input is the
file showing my problem is

--------------------------------------------
\documentclass[12pt]{article}
\begin{document}
Hello world!
\end{document}
-------------------------------------------

I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX
2.7). Next, I hit the log button in Winedt. That causes a pop up
warning (and no log display at screen bottom). The warning says

")" Expected
[FindError(1,1,0,1,0,0 ^^^,0,4);]

I have no idea what this means or what to do about it. BTW, all
was working but I haven't done any tex-ing for a while and now
this - no updates since installation. Any ideas what is going on
and what to do about it. The log file is included below. Thanks
for any help.

-- Jeff Barnett

------------------------------ LOG FILE
------------------------------------------
This is pdfTeX, Version 3.141592-1.40.4 (MiKTeX 2.7) (preloaded
format=latex 2008.2.12) 13 APR 2008 22:25
entering extended mode
**test.tex
(test.tex
LaTeX2e <2005/12/01>
Babel <v3.8h> and hyphenation patterns for english, dumylang,
nohyphenation, lo
aded.
("C:\Program Files\MiKTeX 2.7\tex\latex\base\article.cls"
Document Class: article 2005/09/16 v1.4f Standard LaTeX document class
("C:\Program Files\MiKTeX 2.7\tex\latex\base\size12.clo"
File: size12.clo 2005/09/16 v1.4f Standard LaTeX file (size option)
)
\c <at> part=\count79
\c <at> section=\count80
\c <at> subsection=\count81
\c <at> subsubsection=\count82
\c <at> paragraph=\count83
\c <at> subparagraph=\count84
\c <at> figure=\count85
\c <at> table=\count86
\abovecaptionskip=\skip41
\belowcaptionskip=\skip42
\bibindent=\dimen102
) (test.aux)
LaTeX Font Info: Checking defaults for OML/cmm/m/it on input
line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for T1/cmr/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for OT1/cmr/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for OMS/cmsy/m/n on input
line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for OMX/cmex/m/n on input
line 2.
LaTeX Font Info: ... okay on input line 2.
LaTeX Font Info: Checking defaults for U/cmr/m/n on input line 2.
LaTeX Font Info: ... okay on input line 2.
[1

]
(test.aux) )
Here is how much of TeX's memory you used:
203 strings out of 95353
1988 string characters out of 1184550
45983 words of memory out of 1500000
3479 multiletter control sequences out of 110000
3938 words of font info for 15 fonts, out of 1200000 for 2000
14 hyphenation exceptions out of 8191
22i,4n,19p,137b,107s stack positions out of
5000i,500n,10000p,200000b,5000s

Output written on test.dvi (1 page, 248 bytes).

headers

Pétiard François | 14 Apr 10:07

Re: Log examination

Le 14/04/2008 08:48, Nicolas Vaughan a écrit :
> Have you tried running pdfLaTeX through the command line (DOS prompt)?

But why ? That's not a MiKTeX problem, that's really a WinEdt problem.

>>> On Mon, Apr 14, 2008 at 12:41 AM, Bernice Barnett <jbbrus <at> ca.rr.com<mailto:
>>> jbbrus <at> ca.rr.com>> wrote:
>>>
>>>    I'm using Winedt build 20071003 (v. 5.5). The minimal input is the
>>>    file showing my problem is
>>>
>>>    --------------------------------------------
>>>    \documentclass[12pt]{article}
>>>    \begin{document}
>>>    Hello world!
>>>    \end{document}
>>>    -------------------------------------------
>>>
>>>    I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX
>>>    2.7). Next, I hit the log button in Winedt. That causes a pop up
>>>    warning (and no log display at screen bottom). The warning says
>>>
>>>     ")" Expected
>>>     [FindError(1,1,0,1,0,0 ^^^,0,4);]

It seems there is a problem in the definition of Find Errors.

Have you mode any customizations in WinEdt ?

If not, go to menu Options|Maintenance|Restore and restore the
configuration.

François Pétiard

headers

WinEdt Team | 14 Apr 17:02

Re: Log examination

> Le 14/04/2008 08:48, Nicolas Vaughan a écrit :
>> Have you tried running pdfLaTeX through the command line (DOS prompt)?
>
> But why ? That's not a MiKTeX problem, that's really a WinEdt problem.

The real problem lies in upgrading without consulting the
documentation on changes made in the new release.

Help->What's New explains, as does the info at

    http://www.winedt.com/installing.html

especially under the category of Upgrading...

regards
 Adriana

>>>> On Mon, Apr 14, 2008 at 12:41 AM, Bernice Barnett 
>>>> <jbbrus <at> ca.rr.com<mailto:
>>>> jbbrus <at> ca.rr.com>> wrote:
>>>>
>>>>    I'm using Winedt build 20071003 (v. 5.5). The minimal input is the
>>>>    file showing my problem is
>>>>
>>>>    --------------------------------------------
>>>>    \documentclass[12pt]{article}
>>>>    \begin{document}
>>>>    Hello world!
>>>>    \end{document}
>>>>    -------------------------------------------
>>>>
>>>>    I run this file through pdfTeX, Version 3.141592-1.40.4 (MiKTeX
>>>>    2.7). Next, I hit the log button in Winedt. That causes a pop up
>>>>    warning (and no log display at screen bottom). The warning says
>>>>
>>>>     ")" Expected
>>>>     [FindError(1,1,0,1,0,0 ^^^,0,4);]
>
> It seems there is a problem in the definition of Find Errors.
>
> Have you mode any customizations in WinEdt ?
>
> If not, go to menu Options|Maintenance|Restore and restore the
> configuration.
>
> François Pétiard
>

headers

Bernice Barnett | 14 Apr 20:53

Re: Log examination

WinEdt Team wrote:
>> Le 14/04/2008 08:48, Nicolas Vaughan a écrit :
>>> Have you tried running pdfLaTeX through the command line (DOS prompt)?
>>
>> But why ? That's not a MiKTeX problem, that's really a WinEdt problem.
>
>
> The real problem lies in upgrading without consulting the
> documentation on changes made in the new release.
>
> Help->What's New explains, as does the info at
>
>    http://www.winedt.com/installing.html
>
> especially under the category of Upgrading...
>
> regards
> Adriana
Why do you think I didn't read the above? I did. When I upgraded, I did 
the following in order specified: (1) uninstall Winedt then Miktek 
taking the blow everything away options, (2) reinstall Miktex then 
Winedt choosing the individual users are individuals options, (3) 
configure Miktex paper size, etc., options, (4) start Winedt and use 
configuration wizard for wrapping etc. Steps 1 and 2 where done via an 
administrative account. Steps 3 and 4 where done in both an 
administrative and a power user account.

So why is log display not working???

-- Jeff Barnett

headers

WinEdt Team | 14 Apr 21:20

Re: Log examination


>> Help->What's New explains, as does the info at
>>
>>    http://www.winedt.com/installing.html
>>
>> especially under the category of Upgrading...
>>
> Why do you think I didn't read the above? I did. When I upgraded, I did 
> the following in order specified: (1) uninstall Winedt then Miktek 
> taking the blow everything away options, (2) reinstall Miktex then 
> Winedt choosing the individual users are individuals options, (3) 
> configure Miktex paper size, etc., options, (4) start Winedt and use 
> configuration wizard for wrapping etc. Steps 1 and 2 where done via an 
> administrative account. Steps 3 and 4 where done in both an 
> administrative and a power user account.
> 
> So why is log display not working???

Quoting from the Upgrading section of Installing WinEdt, on winedt.com:

... snipped...

 Default Settings and Compatibility with older Versions

 If preserving your old settings is very important and importing
 the modified default menus listed above is out of question you'll
 have to make a few manual changes through the Menu Setup Dialog.
 Here is what you should know:

 * The old Menu Item Tools -> Erase Output Files will not work! You
   should change its definition to:

      Exe('%b\Exec\Erase Working Files.edt');

 * The old Menu Item Search -> Errors... will not work! You should
   change its definition to:

     [FindError(1,1,0,4,1);]

 * The new categories of Errors are not compatible with WinEdt 5.4
   (or earlier). You should import the default Errors Settings (easy)
   or else read the documentation and make manual changes to your
   configurations through the Settings| Errors Dialog: otherwise some
   warnings in TeX documents will be treated as errors and vice
   versa...

 The What's New? document (Help Menu) describes all major the
 changes in functionality and the default settings from the
 previous version of WinEdt...

....

headers

Bernice Barnett | 15 Apr 00:33

Re: Log examination

WinEdt Team wrote:
>
>>> Help->What's New explains, as does the info at
>>>
>>>    http://www.winedt.com/installing.html
>>>
>>> especially under the category of Upgrading...
>>>
>> Why do you think I didn't read the above? I did. When I upgraded, I 
>> did the following in order specified: (1) uninstall Winedt then 
>> Miktek taking the blow everything away options, (2) reinstall Miktex 
>> then Winedt choosing the individual users are individuals options, 
>> (3) configure Miktex paper size, etc., options, (4) start Winedt and 
>> use configuration wizard for wrapping etc. Steps 1 and 2 where done 
>> via an administrative account. Steps 3 and 4 where done in both an 
>> administrative and a power user account.
>>
>> So why is log display not working???
>
> Quoting from the Upgrading section of Installing WinEdt, on winedt.com:
>
> ... snipped...
>
> Default Settings and Compatibility with older Versions
>
> If preserving your old settings is very important and importing
> the modified default menus listed above is out of question you'll
> have to make a few manual changes through the Menu Setup Dialog.
> Here is what you should know:
>
> * The old Menu Item Tools -> Erase Output Files will not work! You
>   should change its definition to:
>
>      Exe('%b\Exec\Erase Working Files.edt');
>
> * The old Menu Item Search -> Errors... will not work! You should
>   change its definition to:
>
>     [FindError(1,1,0,4,1);]
>
> * The new categories of Errors are not compatible with WinEdt 5.4
>   (or earlier). You should import the default Errors Settings (easy)
>   or else read the documentation and make manual changes to your
>   configurations through the Settings| Errors Dialog: otherwise some
>   warnings in TeX documents will be treated as errors and vice
>   versa...
>
> The What's New? document (Help Menu) describes all major the
> changes in functionality and the default settings from the
> previous version of WinEdt...
>
> ....
Thanks, the above changes fixed the problem. But as I said, I took the 
blow-everything-away options when (un)installing Winedt and Miktex. Is 
it possible that when one is set up in multiple user mode (each login 
has its own settings, etc.) that the uninstall, reinstall sequence only 
clears out settings for the account where the uninstall, reinstall 
occurs? I'm still quite mystified about where the old junk crept in. Was 
I supposed to MANUALLY remove WinEdtEx.ini (and maybe other files) for 
every user in the upgrade process?

-- Jeff Barnett