Open GoogleCodeExporter opened 8 years ago
Are you sure there is no old ktexteditservice installed somewhere in the PATH
before
the most recent ktexteditservice (from lilypond-kde4)? Try:
$ which ktexteditservice
$ `which ktexteditservice` --version (should be 0.2)
Could you please try the following:
- run frescobaldi from command line and look to the messages that appear while
clicking on a note
- try running ktexteditservice <texteditURL> on the commandline,
a) in a Konsole, and
b) in the embedded Terminal inside Frescobaldi? (Use an exactly valid textedit
url to
check if ktexteditservice works well)
Thanks for your report, let's hope we can debug this. On my systems (Gentoo and
KUbuntu intrepid) everything works like it should.
Original comment by wbsoft
on 1 Jan 2009 at 3:05
> `which ktexteditservice` --version
Qt: 4.4.3
KDE: 4.1.3 (KDE 4.1.3)
KTextEditService: 0.2
Here's the output of frescobaldi, with my comments preceded by '%'
> frescobaldi
frescobaldi(15002)/kdecore (trader) KServiceTypeTrader::defaultOffers:
KServiceTypeTrader: serviceType "ThumbCreator" not found
frescobaldi(15002)/kdecore (trader) KServiceTypeTrader::defaultOffers:
KServiceTypeTrader: serviceType "ThumbCreator" not found
% CLICKING ON NOTE...
frescobaldi(15002)/kio (KRun): #### NO SUPPORT FOR READING!
From gnome-terminal and Frescobaldi's internal Konsole, this works:
> ktexteditservice
textedit:///home/mdboom/Dropbox/Lilypond/3SongsOfShattering.new.ly:51:2:2
> Found running instance: org.frescobaldi.main-15188
Another piece of info -- I'm running a Gnome desktop, and installed kdebase,
kdegraphics, PyKDE4, PyQt (and all dependencies) to get Frescobaldi going, but I
don't have a "full" KDE desktop, so I may be silently missing some piece. FWIW,
logging into a KDE session has identical behavior.
Original comment by mdb...@gmail.com
on 1 Jan 2009 at 4:40
That could be the case. The textedit.protocol file should contain a line
helper=true.
That makes sure apps don't try to read. In your case, apps seem to try reading
from
the service, which is not possible.
However, it would be good if Frescobaldi "just works" in Gnome! So I keep this
bug
open. Thanks again for feedback.
Original comment by wbsoft
on 1 Jan 2009 at 6:02
Just for clarification -- it doesn't work from KDE for me either. Logging in
to a
KDE session, and then running Frescobaldi also fails. My only theory (not
understanding all the working pieces), is that something that is normally part
of the
KDE desktop is not installed but needs to be.
Removing the "helper=true" line in textedit.protocol, (or setting it to
"helper=false") does not resolve the issue.
Thanks for your help.
Original comment by mdb...@gmail.com
on 1 Jan 2009 at 6:21
I researched a bit further, but the textedit.protocol file
(part of lilypond-kde4) has both lines:
helper=true
reading=false
in it. So it is strange that the PDF previewer tries to read from the protocol
(which
is apparently the case in your setup). This could be complicated... maybe some
obscure
component of KDE is out of date? Are there some old KDE3 libraries lying around?
Original comment by wbsoft
on 1 Jan 2009 at 7:19
Any updates on this?
Original comment by wbsoft
on 22 Mar 2009 at 10:52
To let you know, I just installed Frescobaldi from the PPA on a Ubuntu Jaunty
machine
and get the same result. Synaptic pulls in all the latest KDE base packages. I
will
do try to do some more detailed testing.
Original comment by jonarnoldsemail
on 22 Jun 2009 at 7:19
Sounds like this might help:
http://lilypond.org/doc/v2.12/Documentation/user/lilypond-program/Point-and-clic
k#Point-and-click
If you can get okular to launch lilypond-invoke-editor and have the LYEDITOR
environment variable be set to "frescobaldi --smart -l %(line)s -c %(column)s
%(file)s"
then that program will take care of it for you. Is there a way to configure how
okular launches links?
Original comment by jonarnoldsemail
on 22 Jun 2009 at 8:20
Yes, see the Frescobaldi (or Okular) documentation, on
http://frescobaldi.org/uguide/configuring.html under Configuring Point and
Click.
In Jaunty (or any other KDE 4.2 distribution) the lilypond-kde4 package is not
necessary anymore, as Okular does not pass textedit:// urls on to the KDE
protocol
handlers anymore.
Original comment by wbsoft
on 23 Jun 2009 at 9:18
Well, the program correctly configured frescobaldi as the custom editor in
Okular,
but still nothing happens when I click on the links. I also tried installing a
full
kubuntu-desktop yesterday and nothing happens in a KDE session either.
Original comment by jonarnoldsemail
on 23 Jun 2009 at 4:15
I tried the latest revision (1384) and I still have the same issue. I will try
in a
Kubuntu Live-CD when I can.
Original comment by jonarnoldsemail
on 23 Jun 2009 at 5:11
Got lilypond-invoke-editor to open Frescobaldi by setting LYEDITOR to
"frescobaldi
--smart --line %(line)s --column %(column)s %(file)s" but I can't get Okular to
launch lilypond-invoke-editor as a custom editor, which makes me think maybe
this
whole thing is an Okular bug. I set lilypond-invoke-editor %f:%l:%c:%c as the
custom
editor line.
Original comment by jonarnoldsemail
on 23 Jun 2009 at 5:40
Okular does not call the external editor when it determines the file does not
exist.
Maybe you have non-7bit characters in the .ly file path? LilyPond encodes them
as
UTF-8 in the PDF urls, but Okular does possibly not always correctly decode
them.
Original comment by wbsoft
on 23 Jun 2009 at 8:39
Ah ha! It's spaces. Thanks! That fixes it for me! Should've tested that
first.....
Original comment by jonarnoldsemail
on 23 Jun 2009 at 8:44
LilyPond encodes spaces as '%20' inside the URLs, but the bug is in Okular that
tries
to check if the file exists, but uses the literal '%20'. Will file a bug with
Okular...
Original comment by wbsoft
on 1 Jul 2009 at 8:55
Greetings,
This as been reported by a French user as well: accented chars and spaces in the
file's path break the PDF point-and-click feature.
How's it going on the Okular front?
Original comment by v.villenave
on 9 May 2010 at 8:44
Original issue reported on code.google.com by
mdb...@gmail.com
on 1 Jan 2009 at 2:18