Bug 108054 - unable to "latex" files opened via media:/
Summary: unable to "latex" files opened via media:/
Status: CONFIRMED
Alias: None
Product: kile
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Michel Ludwig
URL:
Keywords:
: 151814 (view as bug list)
Depends on:
Blocks:
 
Reported: 2005-06-24 14:33 UTC by Andreas Leuner
Modified: 2021-03-09 06:59 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Leuner 2005-06-24 14:33:13 UTC
Version:            (using KDE Devel)
Installed from:    Compiled sources

Hi,

if I open a .tex file via the media:/ kioslave -- e.g. under media:/sda1 Kile won't properly invoke latex with it. latex will say: "file not found: /sda1/... "

Well, the easy way to workaround would be to restrict the file open dialog to local paths... (I guess I could do this myself)

Thanks for reading
Comment 1 Jeroen Wijnhout 2005-06-24 20:52:14 UTC
That's correct, LaTeX cannot deal with kioslaves, that KDE specific technology. I remember something about a project that enabled kioslaves for all linux apps, but I forgot the name of the project.

To use the files, mount the device and access it through the regular filesystem.

best,
Jeroen
Comment 2 Thiago Macieira 2005-06-25 21:12:30 UTC
Jeroen: kile must use mostLocalURL to retrieve the local file corresponding to media:/something.

The bug is in kile.
Comment 3 Jeroen Wijnhout 2005-06-26 10:15:07 UTC
How can I retrieve this URL? There is no mostLocalURL method in KURL.

best,
Jeroen
Comment 4 Andreas Leuner 2005-06-26 10:32:44 UTC
There is KFileItem::mostLocalURL(bool &local). I saw this in a backtrace :-)
Comment 5 Jeroen Wijnhout 2005-06-26 11:28:25 UTC
Hmm, this is only defined in KDE 3.4 and Kile still has to work for KDE 3.2. This means I can fix it for KDE 3.4 but not for 3.3 and 3.2.

best,
Jeroen
Comment 6 Thiago Macieira 2005-06-26 17:27:59 UTC
See http://bugs.kde.org/show_bug.cgi?id=102668#c9 for how amaroK solved this problem.

Kévin: do you have other suggestions? The commit amarok made hardcodes "media" (see link).
Comment 7 Kevin Ottens 2005-06-26 17:38:27 UTC
Hmmm, they could define KIO::UDS_LOCAL_PATH which is equal to "72 | UDS_STRING"
(defined in kdelibs/kio/kio/global.h). Stating a file and search for the atom
having this id number would be enough.

It's definitely a workaround but would be far better than using DCOP for this.
And it would work with other ioslaves using UDS_LOCAL_PATH.
Comment 8 Daniel Mader 2006-08-28 19:03:52 UTC
Hi, any news on this topic? It is quite annoying that the kioslave-accessed files cannot be compiled... Editing and saving works fine, though. I can deal with it, but I think the more novice user won't be pleased.

Thank you for your good work,

Daniel
Comment 9 Michel Ludwig 2006-10-15 11:15:50 UTC
I have prepared a fix, but it sometimes locks Kile completely up. Some investigation is still needed.
Comment 10 Thomas Braun 2008-02-24 13:35:05 UTC
*** Bug 151814 has been marked as a duplicate of this bug. ***
Comment 11 Thomas Braun 2009-05-26 23:17:11 UTC
Does this bug still apply to the kde4 version of kile?
Comment 12 Cédric Boutillier 2012-05-20 08:48:47 UTC
Hi!
I tested this with Kile 2.1 and KDE 4.8.3 (Debian), and I could not reproduce it. I thus think that this bug report can be closed. Thanks!
Comment 13 Justin Zobel 2021-03-09 06:59:11 UTC
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.