Thread: [MiKTeX] inverse dvi and bibtex problems
MiKTeX source code moved to GitHub
Brought to you by:
csc
From: John B. <jba...@ui...> - 2010-11-05 15:19:15
|
peculiar and more peculiar 1) inverse dvi I replied to Steffan Pinnow's note saying the inverse dvi seemed to be working. More precisely, better than expected. It came to the error marked it in the log file and went to the offending spot before e was even pressed. So there was no change in the text screen when e was pressed. I now moved my data files from old computer Then I tested again. Now when I get to the error, the log file goes to the error and stops; the text file doesn't move. If I click e, the text file comes up in notepad and also a command screen labeled C:\Windows\system32\cmd.exe Note that I am running 64 bit win7. The inverse dvi screen now showed the correct line "C:\...\WinEdt 6\winedt.exe" "[Open(|%f|);SelPar(%l,8)]" Any idea on what is causing this 2) bibtex I have installed a bibfile at C:\jblocaltree\bibtex\ssgroups.bib I went to mixtex2.9/maintenance/options/roots and installed this jblocaltree as a new local root. I then clicked apply and ok and then refresh fndb When I run bibtex I get the error, I couldn't open database file ssgroup.bib What step have I missed? John T. Baldwin Professor Emeritus Department of Mathematics, Statistics, and Computer Science M/C 249 jba...@ui... 851 S. Morgan Chicago IL 60607 !DSPAM:4cd41c28327372147715007! |
From: Stefan P. <Mo...@gm...> - 2010-11-06 08:11:46
|
Hello John, > 1) inverse dvi > > [...] > > Then I tested again. Now when I get to the error, the log file goes to > the error and stops; the text file doesn't move. > > If I click e, the text file comes up in notepad and also a command screen > labeled C:\Windows\system32\cmd.exe > > Note that I am running 64 bit win7. > > The inverse dvi screen now showed the correct line > > "C:\...\WinEdt 6\winedt.exe" "[Open(|%f|);SelPar(%l,8)]" > > > Any idea on what is causing this I think you again mix 2 things here. One is the Inverse DVI search which brings you near the double clicked line showing in Yap to the source file in the editor chosen in the Inverse Search dialog. This issue seems to work fine when I understood you correct. The other thing is where you get after pressing a key when you are TeXing a file. Let's assume you have a file like % -- minimal example -- \documentclass{minimal} \begin{document} \test \end{document} % --------------------- and compile it in WinEdt 6 pressing F9 (which should execute pdftexify) you should find yourself at a prompt similar to ! Undefined control sequence. l.4 \test ? either in the console of WinEdt or a Windows command screen (cmd). When I now press "e [Enter]" it behaves like you described: Notepad is opened with the file, but no selection of the line possibly containing the error. But if I press "x [Enter]" at that point it is jumped to line 4 of the document in WinEdt and "\test" is marked in white with a red background, showing the error. Best regards, Stefan |
From: John B. <jba...@ui...> - 2010-11-06 13:08:39
|
I reply below. On Sat, 6 Nov 2010, Stefan Pinnow wrote: > Hello John, > >> 1) inverse dvi >> >> [...] >> >> Then I tested again. Now when I get to the error, the log file goes to >> the error and stops; the text file doesn't move. >> >> If I click e, the text file comes up in notepad and also a command screen >> labeled C:\Windows\system32\cmd.exe >> >> Note that I am running 64 bit win7. >> >> The inverse dvi screen now showed the correct line >> >> "C:\...\WinEdt 6\winedt.exe" "[Open(|%f|);SelPar(%l,8)]" >> >> >> Any idea on what is causing this > > I think you again mix 2 things here. One is the Inverse DVI search which > brings you near the double clicked line showing in Yap to the source file in > the editor chosen in the Inverse Search dialog. This issue seems to work > fine when I understood you correct. > > The other thing is where you get after pressing a key when you are TeXing a > file. > Let's assume you have a file like > > % -- minimal example -- > \documentclass{minimal} > \begin{document} > \test > \end{document} > % --------------------- > > and compile it in WinEdt 6 pressing F9 (which should execute pdftexify) you > should find yourself at a prompt similar to > > ! Undefined control sequence. > l.4 \test > > ? > > either in the console of WinEdt or a Windows command screen (cmd). > > When I now press "e [Enter]" it behaves like you described: Notepad is > opened with the file, but no selection of the line possibly containing the > error. But if I press "x [Enter]" at that point it is jumped to line 4 of > the document in WinEdt and "\test" is marked in white with a red background, > showing the error. > In using the name inverse-dvi, I was trying to refer to the way in which I was told earlier by Ulrike to fix this problem of being directed from the log file to the offending line in the text. If I have the wrong word for the problem, excuse me please. On my new installation, I have exactly the behavior you do. I had remembered the desired behavior as pressing e takes one to the error and then advances the log to next error. To check my memory, I tried a couple of tests on the existing installion: error \test on a line both x and e behave the same. terminate the latex run but take you to the error. error: comment out \end{enumerate} on line 901 Both e and x give the same response: do not move the text but terminate the latex run the log says that \begin{enumerate} of line 699 terminates on line 1001 So I indeed see two problems. 1)On the new installation, if e is supposed to do something that x doesn't, I have to attach winedt as the editor - how do I do that? 2) e doesn't seem to be working properly even on the desktop I had been using. I realize that short samples would be better. However, I am unable to copy from the log file as displayed. I guess I could open a new copy of the log. next time. Thanks again. > > > Best regards, > Stefan > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > MiKTeX-Users mailing list > MiK...@li... > https://lists.sourceforge.net/lists/listinfo/miktex-users > > !DSPAM:4cd50ecd129286168412565! > > |
From: Ulrike F. <li...@ni...> - 2010-11-06 13:48:56
|
Am Sat, 6 Nov 2010 08:08:04 -0500 (Central Daylight Time) schrieb John Baldwin: > 1)On the new installation, if e is supposed to do something that x > doesn't, > I have to attach winedt as the editor - how do I do that? To jump to winedt when you press "e" you must either set an registry key (search the winedt mailing) or set the environment variable MIKTEX_EDITOR. -- Ulrike Fischer |
From: John B. <jba...@ui...> - 2010-11-06 13:54:27
|
Where does one set the environment variable Mixtex-editor? I had thought that was the problem but couldn't tell where to fix. Am I suppose to be altering a winedt file, or a miktex file - accessed via yap or via the miktex maintence options? I list these alternatives just to illustrate my level of ignorance. Thanks again. John John T. Baldwin Professor Emeritus Department of Mathematics, Statistics, and Computer Science M/C 249 jba...@ui... 851 S. Morgan Chicago IL 60607 On Sat, 6 Nov 2010, Ulrike Fischer wrote: > Am Sat, 6 Nov 2010 08:08:04 -0500 (Central Daylight Time) schrieb > John Baldwin: > >> 1)On the new installation, if e is supposed to do something that x >> doesn't, >> I have to attach winedt as the editor - how do I do that? > > To jump to winedt when you press "e" you must either set an registry > key (search the winedt mailing) or set the environment variable > MIKTEX_EDITOR. > > > > -- > Ulrike Fischer > > > ------------------------------------------------------------------------------ > The Next 800 Companies to Lead America's Growth: New Video Whitepaper > David G. Thomson, author of the best-selling book "Blueprint to a > Billion" shares his insights and actions to help propel your > business during the next growth cycle. Listen Now! > http://p.sf.net/sfu/SAP-dev2dev > _______________________________________________ > MiKTeX-Users mailing list > MiK...@li... > https://lists.sourceforge.net/lists/listinfo/miktex-users > > !DSPAM:4cd55cfe169831822916521! > > |
From: Ulrike F. <li...@ni...> - 2010-11-07 16:56:17
|
Am Sat, 6 Nov 2010 08:54:22 -0500 (Central Daylight Time) schrieb John Baldwin: > Where does one set the environment variable Mixtex-editor? There where you set all environments variables for windows: In german: Systemsteuerung->System-> Click the Advanced tab. Click Environment variables. -- Ulrike Fischer |