Re: [Kile-devel] Feature request and possible bug?

[Phil R. <pr...@it...>]

Hi, Thomas; many thanks for your response.  Even though I have the 
chronic delay problem on two separate machines, I've found a third which 
does not experience the problem at all, so I should be able to find my 
problem simply by comparing the configurations in detail.  If it doesn't 
seem to be my configuration after all, I'll post more information, 
following your advice and using your 'date' trick.

As for compiling via SSH, I misunderstood the error; it was indeed Kile 
which was generating the error, not pdflatex.  Digging through some 
code, it looks like Kile is very careful to check existence before 
attempting to compile, so my attempts have probably been ill-advised. 
One thing I found interesting in kiletool.cpp in Base::checkSource():

//FIXME deal with tools that do not need a source or target (yes they exist)

...so it looks like this sort of scenario may have been anticipated, and 
some day it may be possible to make Kile work with more exotic 
configurations, though for now it may be more hassle than it's worth.

I'll try to do some hacking over the next few weeks, perhaps disable a 
couple checks and see if I can get any modified build configs to work. 
In particular, I'm thinking of changing the "pdflatex" command to "ssh 
user@host pdflatex" or something similar; since your timing examples 
demonstrate that you can use normal command-line constructs in the 
"Command" and "Option" fields, I still think it could work.

If all it takes is simply disabling source checks for a build class, is 
it possible we might some day have a class in the default Kile 
distribution which is essentially "Base" with those checks disabled, for 
use with custom configurations (say, for example, an "Advanced" class)?

In any event, I'll post again if I find anything that looks useful. 
Thanks again!

Phil

Thomas Braun wrote:
> Quoting Phil Regier <pr...@it...>:
> 
>> Hello again; I've been looking closer at my Kile configuration, and
>> wanted to adjust my questions a bit since I think I'm starting to
>> understand a bit better:
> 
> Hello Phil,
> 
>> First, the delay when using the "LaTeX" class for PDFLaTeX is actually
>> longer than I originally recalled, perhaps closer to a minute.  However,
>> I've started to notice possible drawbacks to setting the class to
>> "Compile", such as an apparent inability to step through errors after a
>> failed compile.
> 
> I use kile quite often and I never realized a big longer compilatin as 
> on the shell.
> Yes if you use the Compile Class the Latex Error Jumping is not 
> available. This is by design so.
> 
>> So my adjusted question would be whether there's high-level
>> documentation anywhere (again, I'm a terrible coder and generally don't
>> make it very far digging through source when I don't know what I'm
>> looking for) regarding the "Advanced" features of build tool
>> configuration;
> Nope sorry no docu. I think the error lies somewhere different and 
> tuning config should not help much. I think we just try to quantify the 
> time delay.
> 
> So please try the following:
> - Turn off "Automatic call bibtex and rerun latex" in config 
> kile->tools->pdflatex
> - Change your pdflatex command and option as shown to
> comamnd: date && pdflatex
> options: -interaction=nonstopmode '%source' && date
> See http://bayimg.com/fAhMIAabA for a screenshot.
> - Now run the pdflatex tool a few times and calculate execution time 
> needed.
> - Do the same on the shell and report back
> 
>> I didn't see anything that looked promising in the
>> handbook or in SVN READMEs, but since I'm new here I may have just been
>> looking in the wrong places.
>>
>> Part of the reason I ask is that I've made limited progress toward
>> getting the compiler to work in an SSH environment, and suspect that if
>> I was making better use of the build tool configuration, I might be able
>> to get it working, either locally or perhaps by using ssh to invoke
>> latex on the remote host.
>>
>> Any tips?  Thanks in advance...
>>
>> Phil
> 
> Thanks for your patience :)
> 
> Thomas
> 
> PS: See below for some comments on your last mail
>>
>> Phil Regier wrote:
>>> Hi, all; there's very little about Kile that's within my normal sphere
>>> of familiarity, so my apologies if any of the following reflects
>>> ignorance on my part:
>>>
>>>
>>> First, I'm noticing that even though Kile's integrated editor works
>>> splendidly with files accessed via fish:// , only the local path portion
>>> seems to be passed to pdflatex, resulting in a "Sorry, the file ... does
>>> not exist" error at build time.
> 
> This has never been tried.
> Does this work in a shell?
> If yes I can have a look where the error lies inside kile.
> 
>>> It would seem that since pdflatex can read a pipe, all Kile would need
>>> to do to build from fish:// would be to cat the file or selection in
>>> question directly to pdflatex and direct output either to a local temp
>>> directory or to a pipe back to a fish:// URL, and I assume other build
>>> tools could take advantage of such a feature too.  Is building directly
>>> from fish:// possible now, and/or could it be a possibility for the 
>>> future?
>>>
>>>
>>> Second, it seems that by default Kile takes much longer than it should
>>> need (perhaps an extra 15 seconds at 100% CPU utilization for a trivial
>>> document) to invoke pdflatex.  I can get execution time to drop to near
>>> command-line speed by changing the PDFLaTeX class from "LaTeX" to
>>> "Compile" under Settings->Configure Kile->Tools->Build, but this still
>>> doesn't seem right; I assume if this was the correct configuration, it
>>> would have been the default.
> 
> The main difference between both classes are the latex error filter for 
> easy jumping to errors etc.
> Is kile also that slow if you work completely on local files?
> 
> 
> 
>