Version: 1.6b2 (using KDE 3.1.4) Installed from: compiled sources Compiler: gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-113) OS: Linux (i686) release 2.4.22 The call of the kdvi forward search is done with the filename including the entire path, while kdvi is expecting the filename only. So the search fails. I used a master document with includes which are located in the same folder like the master, so that the include command has the short form \include{MyChapter}.
> The call of the kdvi forward search is done with the filename including the >entire path, while kdvi is expecting the filename only. So the search fails. I don't agree on this, AFAIK you can pass an absolute path for the source file. The reason why Kile does this is a work-around, if you just pass the filename then the filename can't begin with a number. > I used a master document with includes which are located in the same folder >like the master, so that the include command has the short form > \include{MyChapter}. Hmm, it should work (and works for me) with \input. It doesn't work if you use \input though. Can you give the exact error message KDVI gives? Btw, do you use the internal viewer or the stand-alone KDVI? best, Jeroen
>Hmm, it should work (and works for me) with \input. It doesn't work if you > use \input though. change the first input to include :-/
.
Subject: dvi forward search fails > > The call of the kdvi forward search is done with the filename including > > the >entire path, while kdvi is expecting the filename only. So the > > search fails. > > I don't agree on this, AFAIK you can pass an absolute path for the source > file. The reason why Kile does this is a work-around, if you just pass the > filename then the filename can't begin with a number. > I did some tests and just now I agree to you. But my problem was the following: My latex_projekt_directory_path (kile_working_path) includes a symbolic link, while the external kdvi viewer started by kile automatically uses the real long path. So kdvi doesn't recognize the short path kile tells kdvi. (I shouldn't use symbolic links. :-( ) > Can you give the exact error message KDVI gives? Die Stelle in der DVI-Datei, die der Zeile 1 in der TeX-Datei /short/path/MyFile.tex entspricht, wurde nicht gefunden. KDVI was not able to locate the place in the DVI file which corresponds to line 1 in the TeX-file /short/path/MyFile.tex. > Btw, do you use the > internal viewer or the stand-alone KDVI? The stand-alone KDVI.
Subject: Re: dvi forward search fails On Monday 03 November 2003 09:39, you wrote: > > > The call of the kdvi forward search is done with the filename including > > > the >entire path, while kdvi is expecting the filename only. So the > > > search fails. > > > > I don't agree on this, AFAIK you can pass an absolute path for the source > > file. The reason why Kile does this is a work-around, if you just pass > > the filename then the filename can't begin with a number. > > I did some tests and just now I agree to you. But my problem was the > following: My latex_projekt_directory_path (kile_working_path) includes a > symbolic link, while the external kdvi viewer started by kile automatically > uses the real long path. So kdvi doesn't recognize the short path kile > tells kdvi. > (I shouldn't use symbolic links. :-( ) Hmm, I'm not sure I completely understand. It is that KDVI does not follow the symbolic link? If that is the case, the bug should be reassigned to KDVI. Perhaps Kile could translate the symbolic link to an absolute path and pass that to KDVI, would that solve the problem? best, Jeroen
Subject: dvi forward search fails > Hmm, I'm not sure I completely understand. It is that KDVI does not follow > the symbolic link? If that is the case, the bug should be reassigned to > KDVI. Perhaps Kile could translate the symbolic link to an absolute path > and pass that to KDVI, would that solve the problem? After some konsole trials I think it's a KDVI bug. My configuration: MyFile.tex as well as MyFile.dvi reside /home/me/tmp If I am in /home/me/tmp [tmp]$ kdvi file:/home/me/tmp/MyFile.dvi#src:19MyFile.tex as well as [tmp]$ kdvi file:/home/me/tmp/MyFile.dvi#src:19/home/me/tmp/MyFile.tex work fine. If I am in /home/me [me]$ kdvi file:tmp/MyFile.dvi#src:19MyFile.tex works fine, but [me]$ kdvi file:tmp/MyFile.dvi#src:19/home/me/tmp/MyFile.tex and [me]$ kdvi file:/home/me/tmp/MyFile.dvi#src:19/home/me/tmp/MyFile.tex fail. So I agree with you to reassign the bug to KDVI. KDVI should work independendly of the working directory if the source file exists. Thank you for your efforts Michael
reassigning to KDVI
Subject: More information required Dear m_ichael, dear Jeroen, sorry for the long silence. I will now try to fix the bug ('dvi forward search fails') that have discussed in November. However, reading the bug report, I do not quite understand the nature of the problem. Could you perhaps make a tar-file with the setup that you are using (including the symlinks, etc.), together with a detailed description how to reproduce the problem ---Thanks. Best, Stefan.
Created attachment 4668 [details] Test files for "Additional Comment #6 From Michael Arnold 2003-11-03 12:14" Dear Stefan, this is for the testcase described in the comment #6. There are no symlinks involved, all folders are real folders. In my opinion the forward search should work if the src-file exists, regardless of the folder kdvi is called from. Best, Michael
Hello, thank you for your help. As far as I can see, the issue is fixed in the latest CVS version of KDVI; the bugfix will be included in the upcoming KDE 3.2.1 release. I would ask you the test that release as soon as is appears. If you find that the problem persists, please contact me again at kebekus@kde.org Best, Stefan Kebekus.